---
title: "Add assets to an attack surface"
method: POST
path: "/v1/attacksurfaces/{attack_surface_id}/assets"
tags: ["Exposure Management"]
---

# Add assets to an attack surface

`POST /v1/attacksurfaces/{attack_surface_id}/assets`

## Request

- Base URL: `https://api.platform.censys.io`
- URL: `https://api.platform.censys.io/v1/attacksurfaces/{attack_surface_id}/assets`
- Auth: HTTP bearer

Add assets as seeds, the starting points from which Censys discovers the rest of your attack surface. Name each asset as an IP address, CIDR block, ASN (for example AS15169), domain, or certificate SHA-256 fingerprint. <br><br>You may submit up to 50 assets per request. Inputting an asset that you have previously added will not return an error.<br><br>This endpoint does not cost credits to execute.

## Path parameters

- `attack_surface_id` string, required: The ID of the attack surface, or the literal 'default' for your organization's attack surface. Obtain the attack surface ID using the list attack surfaces endpoint.

## Query parameters

- `organization_id` string, uuid, required: The ID of a Censys organization to associate the request with. See the [Getting Started docs](https://docs.censys.com/reference/get-started#step-3-find-and-use-your-organization-id-optional) for more information.

## Headers

- `X-Organization-ID` string, uuid: The ID of a Censys organization to associate the request with. See the [Getting Started docs](https://docs.censys.com/reference/get-started#step-3-find-and-use-your-organization-id-optional) for more information. Note: The header parameter is supported for atypical use cases; we recommend always providing this field via the query parameter.

## Request body

- AttackSurfaceAssetsRequest
  - `assets` string[], required: The assets, each an IP address, CIDR block, ASN, domain, or certificate SHA-256 fingerprint.

## Response `201`

Assets applied successfully

- ResponseEnvelopeAttackSurfaceAssets
  - `result` AttackSurfaceAssets
    - `assets` AttackSurfaceAsset[], nullable, required: The assets that were applied, in the form Censys resolved them to.
      - `asset` string, required: The asset, as an IP address, CIDR block, ASN, domain, or certificate SHA-256 fingerprint, in the form you would send to add it. Assets of the types web_property, registrant_organization, registrant_email, crunchbase_organization, and organization are shown by their name or identifier and cannot be named in a request.
      - `type` 'organization' | 'host' | 'domain' | 'certificate' | 'web_property' | 'netblock' | 'autonomous_system' | 'registrant_organization' | 'registrant_email' | 'crunchbase_organization': The kind of entity the asset names. Only host, domain, certificate, netblock, and autonomous_system assets can be named in a request. Omitted when it cannot be determined.

## Other responses

- `401`: Request does not contain a valid Authorization token
- `403`: User does not have permission to access this data
- `404`: Attack surface not found
- `409`: The Exposure Management API is not enabled, or the operation conflicts with the attack surface's current state.
- `422`: Invalid inputs, such as an asset that is not an IP address, CIDR block, ASN, domain, or certificate SHA-256 fingerprint
- `500`: Internal server error

## Changes

- **2026-11-03** `ec1686b0a36a`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/censys/apis/censys-platform-api/changes/v1/attacksurfaces/:attack_surface_id/assets/post.md)

---

[API](https://skmtc.dev/censys/apis/censys-platform-api.md) - [All operations](https://skmtc.dev/censys/apis/censys-platform-api/llms.txt) - [OpenAPI document](https://skmtc.dev/censys/apis/censys-platform-api/revisions/ec1686b0a36a?raw)