Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.crustdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Use this page to send your first request and understand the shared conventions across the Company, Person, and Web 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 codeMeaningDescription
200SuccessRequest completed successfully.
400Bad RequestInvalid request parameters or malformed input.
401UnauthorizedMissing or invalid API key.
403ForbiddenAPI key does not have access to this endpoint.
404Not FoundRequested resource not found.
500Internal Server ErrorUnexpected server-side failure. Try again later.

​
Error response examples

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

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

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

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

{
  "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 12 endpoints across three product areas.
Company and Person live endpoints are plan-specific. Use the Company, Person, and Web guide pages for workflow examples and endpoint-specific behavior.

​
Company API

MethodPathDescription
POST/company/searchSearch companies with filters
POST/company/identifyResolve a domain, URL, or name to a company
POST/company/enrichGet a full company profile
POST/company/search/autocompleteAutocomplete company search fields
POST/company/professional_network/search/liveSearch companies in real time

​
Person API

MethodPathDescription
POST/person/searchSearch people using filters and sorting
POST/person/enrichEnrich person profiles from the cached dataset
POST/person/professional_network/enrich/liveFetch fresh profile data from the web
POST/person/professional_network/search/liveSearch people in real time
POST/person/search/autocompleteGet field value suggestions for building search filters

​
Web API

MethodPathDescription
POST/web/search/livePerform web search
POST/web/enrich/liveFetch web content

Company API

Search, identify, enrich, and autocomplete company data.

Person API

Search, enrich, and autocomplete people data.

Web API

Search the web and fetch page content.