Build your integration
Your agency workspace
Use the workspace assigned to your verified agency. Creator profiles, findings, and events stay inside that access boundary.
On this page
One agency, one assigned workspace
Create an agency account and complete onboarding and KYC. Once the agency is approved, opening /agency/api provisions API access automatically, with one workspace bound to the agency and its current owner.
Your integration enrolls profiles into that workspace. It does not create separate agencies or workspaces through the API. Software companies integrating CRD follow the same agency onboarding path.
Find your workspace ID
Use GET /v1/me with workspaces:read to discover the assigned workspace. Save its id as workspace_id for enrollment. GET /v1/workspaces/{id} reads an accessible workspace.
Receiving a workspace ID or enrolling an inactive creator does not start the usage meter.
Existing contract identifiers
Some fields and resource prefixes retain the internal name partner for compatibility, including the partner object in GET /v1/me. They identify your agency’s API account, not a separate account type.
Use /agency/api for keys, webhook endpoints, usage, and available billing tools. After ownership changes, the current verified owner opens /agency/api and replaces keys and webhook endpoints. Resources tied to an earlier binding may require reconciliation before they can be used again.
Request & response example
/v1/workspaces/{id}curl --request GET 'https://api.crd.systems/v1/workspaces/wsp_example' \
--header "Authorization: Bearer $CRD_API_KEY"{
"id": "wsp_example",
"external_id": "agency_001",
"name": "Example Agency",
"created_at": 1790035200000
}Illustrative response. Replace example resource IDs with the IDs returned by your API requests. View endpoint details.