First-request guide for Get available reference objects.
Export API guide
List reference objects
Discover the lookup objects available to enrich or interpret Export data.
On this page: QuickstartRequest anatomyResponse anatomyRules and constraintsEmpty resultsErrors and recoveryNext steps
Before you start
Authenticate
Send Authorization: Bearer <token> on every request and keep tokens out of logs and source control.
Common workflows
Quickstart
Step 1 — Send the request
curl --request GET \
--url https://uapi.demandbase.com/data/export/v1/references \
--header "Authorization: Bearer $DB_API_KEY" \
--header "Accept: application/json"
Step 2 — Read the response
{
"refObjectsAvailable": [
{
"name": "IdealBuyingGroup",
"description": "Ideal Buying Group",
"href": "https://uapi.demandbase.com/data/export/v1/reference/IdealBuyingGroup"
},
{
"name": "IdealBuyingGroupPersonaRole",
"description": "Persona and Buyer roles associated with an ideal buying group.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/IdealBuyingGroupPersonaRole"
},
{
"name": "BuyerRole",
"description": "Buyer roles reference data.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/BuyerRole"
},
{
"name": "Persona",
"description": "Personas reference data.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/Persona"
},
{
"name": "KeywordSet",
"description": "Keyword sets reference data.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/KeywordSet"
},
{
"name": "KeywordSetMember",
"description": "Members (keywords) within a keyword set.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/KeywordSetMember"
},
{
"name": "JobLevel",
"description": "Job levels reference data.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/JobLevel"
},
{
"name": "JobFunction",
"description": "Job functions reference data.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/JobFunction"
},
{
"name": "TopLevelIndustry",
"description": "Top Level Industry reference data.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/TopLevelIndustry"
},
{
"name": "SubIndustry",
"description": "Sub Industry reference data.",
"href": "https://uapi.demandbase.com/data/export/v1/reference/SubIndustry"
}
]
}
Request anatomy
| Part | Required | What to send |
|---|---|---|
| Authorization | header | Bearer token with permission to read Export reference data. |
| body | none | This discovery request has no request body or query parameters. |
Response anatomy
| Field | Type / state | How to use it |
|---|---|---|
| refObjectsAvailable | array | Reference objects available to this API version. |
| objectType | string | Name accepted by the lookup endpoint. |
| href | URL | Endpoint for retrieving the object values. |
Rules and constraints
- Use the exact objectType and href returned by the API.
- Cache discovery only for a period appropriate to your integration because availability can vary by version or tenant.
- Do not treat the discovery list as the values themselves.
Empty results
If no reference objects are returned, continue without enrichment and verify tenant entitlements before treating it as an API failure.
Errors and recovery
Handle these responses explicitly so your integration can report an actionable cause and next step.
| Status | Meaning | Recovery |
|---|---|---|
| 401 | The bearer token is missing, expired, or invalid. | Refresh the token and retry discovery. |
| 403 | The caller cannot read reference data. | Verify Export reference permissions for the tenant. |