First-request guide for Upsert field mappings.
Upsert field mappings
Upsert field mappings
Overview
Creates or replaces the field mappings for the given source and object type. The full set of mappings provided in the request body replaces any existing mappings.
Quickstart
Follow these two steps to make a request and recognize a successful response.
Make a request
curl --request PUT \
--url https://uapi.demandbase.com/integration/v1/custom-sources/1/field-mappings/account \
--header "Authorization: Bearer $DB_API_KEY" \
--header "Content-Type: application/json" \
--data '{"fieldMappings":[{"sourceFieldLabel":"annual_revenue","demandbaseFieldName":"annualRevenue","dataType":"number"},{"sourceFieldLabel":"hq_country","demandbaseFieldName":"country","dataType":"string"}]}'Request anatomy
Build the request from the method, path, parameters, and payload described below.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| value | Optional | ||
| value | Optional |
Request body
No fields are defined for this payload.
Response anatomy
The endpoint returns 201 for the documented success case. Field mappings upserted successfully. No content returned.
The response schema does not enumerate fields; inspect the example response and status code.
Rules
- Use
PUTwith the path/integration/v1/custom-sources/{source_id}/field-mappings/{object_type}. - Required inputs: No parameters are marked required in the published schema..
- Authenticate every request with a valid Demandbase access token.
- Send the request body as
application/json.
Filters
This endpoint has no additional filters or parameters beyond its authentication requirements.
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| value | Optional | ||
| value | Optional |
Errors
Handle non-success responses explicitly so your integration can report actionable failures.
| Status | Meaning |
|---|---|
400 | Request failed. |
401 | Request failed. |
404 | Request failed. |
500 | Request failed. |