# Create company assets

The endpoint is used to create company assets.

Endpoint: POST /v2/assets
Version: 2
Security: 

## Request fields (application/json):

  - `assets` (array, required)
    assets by name, e.g., "127.0.0.1", "panorays.com"
    Example: ["127.0.0.10","panorays.com"]

## Response 200 fields (application/json):

  - `type` (string, required)
    Enum: "DOMAIN", "SUBDOMAIN", "IP", "IP_RANGE"

  - `is_up` (boolean, required)
    Is the asset active or not

  - `location` (string, required)
    The asset location, two letter country code

  - `domains` (array,null)
    List of domains corresponding with the asset. Only for assets of type IP

  - `ips` (array,null)
    List of ips corresponding with the asset. Only for assets of type DOMAIN or SUBDOMAIN

  - `asset_lifecycle` (string, required)
    Assets Lifecycle

  - `dispute_status` (string, required)
    Dispute status

  - `discovery_origin` (string, required)
    Asset discovery origin

  - `name` (string, required)

  - `insert_ts` (string, required)

## Response 201 fields (application/json):

  - `type` (string, required)
    Enum: "DOMAIN", "SUBDOMAIN", "IP", "IP_RANGE"

  - `is_up` (boolean, required)
    Is the asset active or not

  - `location` (string, required)
    The asset location, two letter country code

  - `domains` (array,null)
    List of domains corresponding with the asset. Only for assets of type IP

  - `ips` (array,null)
    List of ips corresponding with the asset. Only for assets of type DOMAIN or SUBDOMAIN

  - `asset_lifecycle` (string, required)
    Assets Lifecycle

  - `dispute_status` (string, required)
    Dispute status

  - `discovery_origin` (string, required)
    Asset discovery origin

  - `name` (string, required)

  - `insert_ts` (string, required)


## Response 401 fields

## Response 403 fields

## Response 429 fields