API Introduction - Crustdata Docs

Use this page to send your first request and understand the shared conventions across the Company, Person, Job, Web, and Social Post APIs.

Base URL

All API requests are made to:

https://api.crustdata.com

Authentication

Every request must include a Bearer token in the authorization header.

--header 'authorization: Bearer YOUR_API_KEY'

You can get your API key from the Crustdata dashboard.

Keep your API key secret. Do not expose it in client-side code or public repositories.

Endpoint availability can vary by plan. Some live Company and Person endpoints are enterprise-only. Review Pricing before you build a production workflow.

API versioning

Include the x-api-version header in every request. The current version is 2025-11-01.

--header 'x-api-version: 2025-11-01'

Requests without a version header can default to the latest version, which may introduce breaking changes. Always pin to a specific version.

Request format

All endpoints accept JSON request bodies with content-type: application/json.

curl --request POST \
  --url https://api.crustdata.com/company/identify \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{"domains": ["retool.com"]}'

Response format

All responses return JSON. Successful requests typically return 200 with the endpoint-specific payload in the response body.

Error responses

Error responses return JSON with an error field and a details field explaining the issue.

Most APIs use description for the details field. The Person API uses reason instead.

{
    "error": "Invalid Request",
    "description": "Exactly one identifier must be provided."
}

Person API

{
    "error": "Invalid Request",
    "reason": "Input should be a valid dictionary"
}

HTTP status codes

Status code	Meaning	Description
`200`	Success	Request completed successfully.
`400`	Bad Request	Invalid request parameters or malformed input.
`401`	Unauthorized	Missing or invalid API key.
`403`	Forbidden	API key does not have access to this endpoint.
`404`	Not Found	Requested resource not found.
`500`	Internal Server Error	Unexpected server-side failure. Try again later.

Error response examples

400 — Bad Request

{
  "error": "bad_request",
  "description": "Invalid request body."
}

401 — Unauthorized

{
  "error": "Unauthorized",
  "description": "Missing or invalid API key."
}

403 — Forbidden

{
  "error": "forbidden",
  "description": "API key does not have access to this endpoint."
}

404 — Not Found

{
  "error": "Not Found",
  "description": "Company not found."
}

500 — Internal Server Error

{
  "error": "Internal Server Error",
  "description": "An unexpected error occurred. Please try again later."
}

Rate limits

API requests are rate-limited per API key. See Rate limits for details on limits and best practices.

Endpoints

This reference currently documents 18 endpoints across five product areas.

Endpoint availability varies by plan. Certain live and specialized endpoints are enterprise-only. Check exactly what your API key can currently access with the free /account/endpoints endpoint, and contact sales to enable more.

Company API

Method	Path	Description
POST	`/company/search`	Search companies with filters
POST	`/company/identify`	Resolve a domain, URL, or name to a company
POST	`/company/enrich`	Get a full company profile
POST	`/company/professional_network/search/live`	Search companies in real time
POST	`/company/search/autocomplete`	Autocomplete company search fields

Person API

Method	Path	Description
POST	`/person/search`	Search people using filters and sorting
POST	`/person/enrich`	Enrich person profiles from the cached dataset
POST	`/person/contact/enrich`	Enrich contact data (emails and phone numbers) for a person
POST	`/person/professional_network/enrich/live`	Fetch fresh profile data from the web
POST	`/person/professional_network/search/live`	Search people in real time
POST	`/person/search/autocomplete`	Get field value suggestions for building search filters

Job API

Method	Path	Description
POST	`/job/search`	Search the indexed job dataset with filters, sorting, and aggregations
POST	`/job/search/autocomplete`	Autocomplete values for a job search field
POST	`/job/professional_network/search/live`	Fetch job listings in real time for a company

Web API

Method	Path	Description
POST	`/web/search/live`	Perform web search
POST	`/web/enrich/live`	Fetch web content

Method	Path	Description
POST	`/social_post/professional_network/enrich/live`	Fetch recent social posts for a person or company
POST	`/social_post/professional_network/search/live`	Search social posts by keyword and filters

Company API

Search, identify, enrich, and autocomplete company data.

Person API

Search, enrich, and autocomplete people data.

Job API

Search indexed job listings and fetch real-time openings for a company.

Web API

Search the web and fetch page content.

Social Post API guides are available to plans with live access — the endpoints above are documented in this reference. To enable access, contact us.

​Base URL

​Authentication

​API versioning

​Request format

​Response format

​Error responses

​HTTP status codes

​Error response examples

​Rate limits

​Endpoints

​Company API

​Person API

​Job API

​Web API

​Social Post API

Company API

Person API

Job API

Web API

Base URL

Authentication

API versioning

Request format

Response format

Error responses

HTTP status codes

Error response examples

Rate limits

Endpoints

Company API

Person API

Job API

Web API

Social Post API