First-request guide for Update Activity Type.
Update Activity Type
Update Activity Type
Overview
Update an existing activity type on your Demandbase tenant. Use the activity type ID in the URI (via `PUT /activity_type/{activityTypeId}`).
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/import/v1/activity_type/1 \
--header "Authorization: Bearer $DB_API_KEY" \
--header "Content-Type: application/json" \
--data '{"activityType":{"label":"example","name":"example","description":"example"},"fields":[{"fieldName":"example","fieldDataType":"example","defaultField":true,"isRequiredForCsvImport":true}]}'Request anatomy
Build the request from the method, path, parameters, and payload described below.
Parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
activityTypeId | path | integer (int64) | Required |
Request body
No fields are defined for this payload.
Response anatomy
The endpoint returns 200 for the documented success case. Inspect the response fields below.
The response schema does not enumerate fields; inspect the example response and status code.
Rules
- Use
PUTwith the path/activity_type/{activityTypeId}. - Required inputs: activityTypeId.
- Authenticate every request with a valid Demandbase access token.
- Send the request body as
application/json.
Filters
The published schema exposes the following endpoint inputs. Use the location column to place each value correctly.
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
activityTypeId | path | integer (int64) | Required |
Errors
Handle non-success responses explicitly so your integration can report actionable failures.
| Status | Meaning |
|---|---|
400 | Request failed. |
404 | Request failed. |
500 | Request failed. |