# Accounting API — Tracking Categories > Canonical URL: https://developers.apideck.com/apis/accounting/reference#tag/Tracking-Categories This document contains every operation on the `Tracking Categories` resource. --- # List Tracking Categories > **Accounting API** · `GET /accounting/tracking-categories` > Canonical URL: https://developers.apideck.com/apis/accounting/reference#tag/Tracking-Categories/operation/trackingCategoriesAll > MCP tool: `accounting-tracking-categories-all` ## Authentication - Send `Authorization: Bearer $API_KEY` using your Apideck secret API key. Keep the key server-side; never put it in a URL or client-side code. Use the application, consumer and connector headers listed in Parameters below for this operation. ## Learn more - [Tracking category explained](https://developers.apideck.com/glossary#tracking-category) - [How does cursor pagination work?](https://developers.apideck.com/glossary#cursor) - [Learn about field mapping](https://developers.apideck.com/guides/field-mapping) List Tracking Categories ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `raw` | query | `boolean` | No | Include raw response. Mostly used for debugging purposes | | `x-apideck-consumer-id` | header | `string` | Yes | ID of the consumer which you want to get or push data from | | `x-apideck-app-id` | header | `string` | Yes | The ID of your Unify application | | `x-apideck-service-id` | header | `string` | No | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | | `x-apideck-company-id` | header | `string` | No | The ID of the company to scope requests to. For connectors that support multi-company, this overrides the default company configured in connection settings. | | `cursor` | query | `string` | No | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | | `limit` | query | `integer` | No | Number of results to return. Minimum 1, Maximum 200, Default 20 | | `pass_through` | query | `object` | No | Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads | | `fields` | query | `string` | No | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation.

Example: `fields=name,email,addresses.city`

In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. | ### Responses #### 200 — Tracking categories - `status_code` `integer` **required** — HTTP Response Status Code — example: `200` - `status` `string` **required** — HTTP Response Status — example: `OK` - `service` `string` **required** — Apideck ID of service provider — example: `quickbooks` - `resource` `string` **required** — Unified API resource name — example: `tracking-categories` - `operation` `string` **required** — Operation performed — example: `all` - `data` `array of object` **required** - `id` `string` — A unique identifier for an object. — example: `12345` - `parent_id` `string` — A unique identifier for an object. — example: `12345` - `parent_name` `string` — The name of the parent tracking category. — example: `Area` - `name` `string` — The name of the tracking category. — example: `Department` - `code` `string` — The code of the tracking category. — example: `100` - `status` `string` — Based on the status some functionality is enabled or disabled. — enum: `active`, `inactive` — example: `active` - `custom_mappings` `object` — When custom mappings are configured on the resource, the result is included here. - `row_version` `string` — A binary value used to detect updates to a object and prevent data conflicts. It is incremented each time an update is made to the object. — example: `1-12345` - `updated_by` `string` — The user who last updated the object. — example: `12345` - `created_by` `string` — The user who created the object. — example: `12345` - `updated_at` `string` — The date and time when the object was last updated. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `created_at` `string` — The date and time when the object was created. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `pass_through` `array of object` — The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources. - `service_id` `string` **required** — Identifier for the service to which this pass_through should be applied. - `operation_id` `string` — Optional identifier for a workflow operation to which this pass_through should be applied. This is useful for Unify calls that are making more than one downstream request. - `extend_object` `object` — Simple object allowing any properties for direct extension. - `extend_paths` `array of object` — Array of objects for structured data modifications via paths. - `path` `string` **required** — JSONPath string specifying where to apply the value. — example: `$.nested.property` - `value` `any` **required** — The value to set at the specified path, can be any type. - `subsidiaries` `array of any` — The subsidiaries the account belongs to. - `id` `string` — The ID of the subsidiary. - `meta` `object` — Response metadata - `items_on_page` `integer` — Number of items returned in the data property of the response — example: `50` - `cursors` `object` — Cursors to navigate to previous or next pages through the API - `previous` `string` — Cursor to navigate to the previous page of results through the API — example: `em9oby1jcm06OnBhZ2U6OjE=` - `current` `string` — Cursor to navigate to the current page of results through the API — example: `em9oby1jcm06OnBhZ2U6OjI=` - `next` `string` — Cursor to navigate to the next page of results through the API — example: `em9oby1jcm06OnBhZ2U6OjM=` - `total_count` `integer` — Number of records available in total for this resource — example: `1` - `warnings` `array of object` — Non-fatal warnings emitted when optional workflow steps failed. Present only when at least one step degraded; the response status remains 200. - `type` `string` — Discriminator for the warning kind. — example: `downstream_request_failed` - `status_code` `integer` — HTTP status code returned by the failed downstream request, when available. — example: `429` - `error` `string` — Short error description from the downstream provider, when available. - `operation` `string` — Identifier of the workflow step that failed. — example: `getManager` - `message` `string` — Detailed message from the downstream provider, when available. - `links` `object` — Links to navigate to previous or next pages through the API - `previous` `string` — Link to navigate to the previous page through the API — example: `https://unify.apideck.com/crm/companies?cursor=em9oby1jcm06OnBhZ2U6OjE%3D` - `current` `string` — Link to navigate to the current page through the API — example: `https://unify.apideck.com/crm/companies` - `next` `string` — Link to navigate to the previous page through the API — example: `https://unify.apideck.com/crm/companies?cursor=em9oby1jcm06OnBhZ2U6OjM` - `_raw` `object` — Raw response from the integration when raw=true query param is provided #### 400 — Bad Request > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 401 — Unauthorized > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 402 — Payment Required > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 404 — The specified resource was not found > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 422 — Unprocessable > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### default — Unexpected error > Standard error response — see [Error Responses](https://developers.apideck.com/errors) --- # Create Tracking Category > **Accounting API** · `POST /accounting/tracking-categories` > Canonical URL: https://developers.apideck.com/apis/accounting/reference#tag/Tracking-Categories/operation/trackingCategoriesAdd > MCP tool: `accounting-tracking-categories-add` ## Authentication - Send `Authorization: Bearer $API_KEY` using your Apideck secret API key. Keep the key server-side; never put it in a URL or client-side code. Use the application, consumer and connector headers listed in Parameters below for this operation. ## Learn more - [Tracking category explained](https://developers.apideck.com/glossary#tracking-category) - [Field mapping explained](https://developers.apideck.com/glossary#field-mapping) - [Learn about field mapping](https://developers.apideck.com/guides/field-mapping) Create Tracking Category ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `raw` | query | `boolean` | No | Include raw response. Mostly used for debugging purposes | | `x-apideck-consumer-id` | header | `string` | Yes | ID of the consumer which you want to get or push data from | | `x-apideck-app-id` | header | `string` | Yes | The ID of your Unify application | | `x-apideck-service-id` | header | `string` | No | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | | `x-apideck-company-id` | header | `string` | No | The ID of the company to scope requests to. For connectors that support multi-company, this overrides the default company configured in connection settings. | ### Request Body _Required._ - `id` `string` — A unique identifier for an object. — example: `12345` - `parent_id` `string` — A unique identifier for an object. — example: `12345` - `parent_name` `string` — The name of the parent tracking category. — example: `Area` - `name` `string` — The name of the tracking category. — example: `Department` - `code` `string` — The code of the tracking category. — example: `100` - `status` `string` — Based on the status some functionality is enabled or disabled. — enum: `active`, `inactive` — example: `active` - `custom_mappings` `object` — When custom mappings are configured on the resource, the result is included here. - `row_version` `string` — A binary value used to detect updates to a object and prevent data conflicts. It is incremented each time an update is made to the object. — example: `1-12345` - `updated_by` `string` — The user who last updated the object. — example: `12345` - `created_by` `string` — The user who created the object. — example: `12345` - `updated_at` `string` — The date and time when the object was last updated. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `created_at` `string` — The date and time when the object was created. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `pass_through` `array of object` — The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources. - `service_id` `string` **required** — Identifier for the service to which this pass_through should be applied. - `operation_id` `string` — Optional identifier for a workflow operation to which this pass_through should be applied. This is useful for Unify calls that are making more than one downstream request. - `extend_object` `object` — Simple object allowing any properties for direct extension. - `extend_paths` `array of object` — Array of objects for structured data modifications via paths. - `path` `string` **required** — JSONPath string specifying where to apply the value. — example: `$.nested.property` - `value` `any` **required** — The value to set at the specified path, can be any type. - `subsidiaries` `array of any` — The subsidiaries the account belongs to. - `id` `string` — The ID of the subsidiary. ### Responses #### 201 — Tracking category created - `status_code` `integer` **required** — HTTP Response Status Code — example: `201` - `status` `string` **required** — HTTP Response Status — example: `Created` - `service` `string` **required** — Apideck ID of service provider — example: `quickbooks` - `resource` `string` **required** — Unified API resource name — example: `tracking-categories` - `operation` `string` **required** — Operation performed — example: `add` - `data` `object` **required** — A object containing a unique identifier for the resource that was created, updated, or deleted. - `id` `string` **required** — The unique identifier of the resource — example: `12345` - `_raw` `object` — Raw response from the integration when raw=true query param is provided #### 400 — Bad Request > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 401 — Unauthorized > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 402 — Payment Required > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 404 — The specified resource was not found > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 422 — Unprocessable > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### default — Unexpected error > Standard error response — see [Error Responses](https://developers.apideck.com/errors) --- # Get Tracking Category > **Accounting API** · `GET /accounting/tracking-categories/{id}` > Canonical URL: https://developers.apideck.com/apis/accounting/reference#tag/Tracking-Categories/operation/trackingCategoriesOne > MCP tool: `accounting-tracking-categories-one` ## Authentication - Send `Authorization: Bearer $API_KEY` using your Apideck secret API key. Keep the key server-side; never put it in a URL or client-side code. Use the application, consumer and connector headers listed in Parameters below for this operation. ## Learn more - [Tracking category explained](https://developers.apideck.com/glossary#tracking-category) - [Field mapping explained](https://developers.apideck.com/glossary#field-mapping) - [Learn about field mapping](https://developers.apideck.com/guides/field-mapping) Get Tracking Category ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `id` | path | `string` | Yes | ID of the record you are acting upon. | | `x-apideck-consumer-id` | header | `string` | Yes | ID of the consumer which you want to get or push data from | | `x-apideck-app-id` | header | `string` | Yes | The ID of your Unify application | | `x-apideck-service-id` | header | `string` | No | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | | `x-apideck-company-id` | header | `string` | No | The ID of the company to scope requests to. For connectors that support multi-company, this overrides the default company configured in connection settings. | | `raw` | query | `boolean` | No | Include raw response. Mostly used for debugging purposes | | `fields` | query | `string` | No | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation.

Example: `fields=name,email,addresses.city`

In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. | ### Responses #### 200 — Tracking category - `status_code` `integer` **required** — HTTP Response Status Code — example: `200` - `status` `string` **required** — HTTP Response Status — example: `OK` - `service` `string` **required** — Apideck ID of service provider — example: `xero` - `resource` `string` **required** — Unified API resource name — example: `tracking-categories` - `operation` `string` **required** — Operation performed — example: `one` - `data` `object` **required** - `id` `string` — A unique identifier for an object. — example: `12345` - `parent_id` `string` — A unique identifier for an object. — example: `12345` - `parent_name` `string` — The name of the parent tracking category. — example: `Area` - `name` `string` — The name of the tracking category. — example: `Department` - `code` `string` — The code of the tracking category. — example: `100` - `status` `string` — Based on the status some functionality is enabled or disabled. — enum: `active`, `inactive` — example: `active` - `custom_mappings` `object` — When custom mappings are configured on the resource, the result is included here. - `row_version` `string` — A binary value used to detect updates to a object and prevent data conflicts. It is incremented each time an update is made to the object. — example: `1-12345` - `updated_by` `string` — The user who last updated the object. — example: `12345` - `created_by` `string` — The user who created the object. — example: `12345` - `updated_at` `string` — The date and time when the object was last updated. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `created_at` `string` — The date and time when the object was created. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `pass_through` `array of object` — The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources. - `service_id` `string` **required** — Identifier for the service to which this pass_through should be applied. - `operation_id` `string` — Optional identifier for a workflow operation to which this pass_through should be applied. This is useful for Unify calls that are making more than one downstream request. - `extend_object` `object` — Simple object allowing any properties for direct extension. - `extend_paths` `array of object` — Array of objects for structured data modifications via paths. - `path` `string` **required** — JSONPath string specifying where to apply the value. — example: `$.nested.property` - `value` `any` **required** — The value to set at the specified path, can be any type. - `subsidiaries` `array of any` — The subsidiaries the account belongs to. - `id` `string` — The ID of the subsidiary. - `meta` `object` — Response metadata - `items_on_page` `integer` — Number of items returned in the data property of the response — example: `50` - `cursors` `object` — Cursors to navigate to previous or next pages through the API - `previous` `string` — Cursor to navigate to the previous page of results through the API — example: `em9oby1jcm06OnBhZ2U6OjE=` - `current` `string` — Cursor to navigate to the current page of results through the API — example: `em9oby1jcm06OnBhZ2U6OjI=` - `next` `string` — Cursor to navigate to the next page of results through the API — example: `em9oby1jcm06OnBhZ2U6OjM=` - `total_count` `integer` — Number of records available in total for this resource — example: `1` - `warnings` `array of object` — Non-fatal warnings emitted when optional workflow steps failed. Present only when at least one step degraded; the response status remains 200. - `type` `string` — Discriminator for the warning kind. — example: `downstream_request_failed` - `status_code` `integer` — HTTP status code returned by the failed downstream request, when available. — example: `429` - `error` `string` — Short error description from the downstream provider, when available. - `operation` `string` — Identifier of the workflow step that failed. — example: `getManager` - `message` `string` — Detailed message from the downstream provider, when available. - `_raw` `object` — Raw response from the integration when raw=true query param is provided #### 400 — Bad Request > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 401 — Unauthorized > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 402 — Payment Required > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 404 — The specified resource was not found > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 422 — Unprocessable > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### default — Unexpected error > Standard error response — see [Error Responses](https://developers.apideck.com/errors) --- # Delete Tracking Category > **Accounting API** · `DELETE /accounting/tracking-categories/{id}` > Canonical URL: https://developers.apideck.com/apis/accounting/reference#tag/Tracking-Categories/operation/trackingCategoriesDelete > MCP tool: `accounting-tracking-categories-delete` ## Authentication - Send `Authorization: Bearer $API_KEY` using your Apideck secret API key. Keep the key server-side; never put it in a URL or client-side code. Use the application, consumer and connector headers listed in Parameters below for this operation. ## Learn more - [Tracking category explained](https://developers.apideck.com/glossary#tracking-category) - [Field mapping explained](https://developers.apideck.com/glossary#field-mapping) - [Learn about field mapping](https://developers.apideck.com/guides/field-mapping) Delete Tracking Category ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `id` | path | `string` | Yes | ID of the record you are acting upon. | | `x-apideck-consumer-id` | header | `string` | Yes | ID of the consumer which you want to get or push data from | | `x-apideck-app-id` | header | `string` | Yes | The ID of your Unify application | | `x-apideck-service-id` | header | `string` | No | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | | `x-apideck-company-id` | header | `string` | No | The ID of the company to scope requests to. For connectors that support multi-company, this overrides the default company configured in connection settings. | | `raw` | query | `boolean` | No | Include raw response. Mostly used for debugging purposes | ### Responses #### 200 — Tracking category deleted - `status_code` `integer` **required** — HTTP Response Status Code — example: `200` - `status` `string` **required** — HTTP Response Status — example: `OK` - `service` `string` **required** — Apideck ID of service provider — example: `quickbooks` - `resource` `string` **required** — Unified API resource name — example: `tracking-categories` - `operation` `string` **required** — Operation performed — example: `delete` - `data` `object` **required** — A object containing a unique identifier for the resource that was created, updated, or deleted. - `id` `string` **required** — The unique identifier of the resource — example: `12345` - `_raw` `object` — Raw response from the integration when raw=true query param is provided #### 400 — Bad Request > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 401 — Unauthorized > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 402 — Payment Required > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 404 — The specified resource was not found > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 422 — Unprocessable > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### default — Unexpected error > Standard error response — see [Error Responses](https://developers.apideck.com/errors) --- # Update Tracking Category > **Accounting API** · `PATCH /accounting/tracking-categories/{id}` > Canonical URL: https://developers.apideck.com/apis/accounting/reference#tag/Tracking-Categories/operation/trackingCategoriesUpdate > MCP tool: `accounting-tracking-categories-update` ## Authentication - Send `Authorization: Bearer $API_KEY` using your Apideck secret API key. Keep the key server-side; never put it in a URL or client-side code. Use the application, consumer and connector headers listed in Parameters below for this operation. ## Learn more - [Tracking category explained](https://developers.apideck.com/glossary#tracking-category) - [Field mapping explained](https://developers.apideck.com/glossary#field-mapping) - [Learn about field mapping](https://developers.apideck.com/guides/field-mapping) Update Tracking Category ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `id` | path | `string` | Yes | ID of the record you are acting upon. | | `x-apideck-consumer-id` | header | `string` | Yes | ID of the consumer which you want to get or push data from | | `x-apideck-app-id` | header | `string` | Yes | The ID of your Unify application | | `x-apideck-service-id` | header | `string` | No | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | | `x-apideck-company-id` | header | `string` | No | The ID of the company to scope requests to. For connectors that support multi-company, this overrides the default company configured in connection settings. | | `raw` | query | `boolean` | No | Include raw response. Mostly used for debugging purposes | ### Request Body _Required._ - `id` `string` — A unique identifier for an object. — example: `12345` - `parent_id` `string` — A unique identifier for an object. — example: `12345` - `parent_name` `string` — The name of the parent tracking category. — example: `Area` - `name` `string` — The name of the tracking category. — example: `Department` - `code` `string` — The code of the tracking category. — example: `100` - `status` `string` — Based on the status some functionality is enabled or disabled. — enum: `active`, `inactive` — example: `active` - `custom_mappings` `object` — When custom mappings are configured on the resource, the result is included here. - `row_version` `string` — A binary value used to detect updates to a object and prevent data conflicts. It is incremented each time an update is made to the object. — example: `1-12345` - `updated_by` `string` — The user who last updated the object. — example: `12345` - `created_by` `string` — The user who created the object. — example: `12345` - `updated_at` `string` — The date and time when the object was last updated. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `created_at` `string` — The date and time when the object was created. — format: `date-time` — example: `2020-09-30T07:43:32.000Z` - `pass_through` `array of object` — The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources. - `service_id` `string` **required** — Identifier for the service to which this pass_through should be applied. - `operation_id` `string` — Optional identifier for a workflow operation to which this pass_through should be applied. This is useful for Unify calls that are making more than one downstream request. - `extend_object` `object` — Simple object allowing any properties for direct extension. - `extend_paths` `array of object` — Array of objects for structured data modifications via paths. - `path` `string` **required** — JSONPath string specifying where to apply the value. — example: `$.nested.property` - `value` `any` **required** — The value to set at the specified path, can be any type. - `subsidiaries` `array of any` — The subsidiaries the account belongs to. - `id` `string` — The ID of the subsidiary. ### Responses #### 200 — Tracking category updated - `status_code` `integer` **required** — HTTP Response Status Code — example: `200` - `status` `string` **required** — HTTP Response Status — example: `OK` - `service` `string` **required** — Apideck ID of service provider — example: `quickbooks` - `resource` `string` **required** — Unified API resource name — example: `tracking-categories` - `operation` `string` **required** — Operation performed — example: `update` - `data` `object` **required** — A object containing a unique identifier for the resource that was created, updated, or deleted. - `id` `string` **required** — The unique identifier of the resource — example: `12345` - `_raw` `object` — Raw response from the integration when raw=true query param is provided #### 400 — Bad Request > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 401 — Unauthorized > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 402 — Payment Required > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 404 — The specified resource was not found > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 422 — Unprocessable > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### default — Unexpected error > Standard error response — see [Error Responses](https://developers.apideck.com/errors) --- # Create Tracking Categories in batch > **Accounting API** · `POST /accounting/tracking-categories/batch` > Canonical URL: https://developers.apideck.com/apis/accounting/reference#tag/Tracking-Categories/operation/trackingCategoriesBatchAdd > MCP tool: `accounting-tracking-categories-batch-add` ## Authentication - Send `Authorization: Bearer $API_KEY` using your Apideck secret API key. Keep the key server-side; never put it in a URL or client-side code. Use the application, consumer and connector headers listed in Parameters below for this operation. ## Learn more - [Tracking category explained](https://developers.apideck.com/glossary#tracking-category) - [Field mapping explained](https://developers.apideck.com/glossary#field-mapping) - [Learn about field mapping](https://developers.apideck.com/guides/field-mapping) Create multiple tracking categories in a single request. Each item is processed independently, so some may be created while others fail; the response returns `200` with one result per item, in the order the items were sent. The maximum number of items accepted per request depends on the connector. ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `raw` | query | `boolean` | No | Include raw response. Mostly used for debugging purposes | | `x-apideck-consumer-id` | header | `string` | Yes | ID of the consumer which you want to get or push data from | | `x-apideck-app-id` | header | `string` | Yes | The ID of your Unify application | | `x-apideck-service-id` | header | `string` | No | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | | `x-apideck-company-id` | header | `string` | No | The ID of the company to scope requests to. For connectors that support multi-company, this overrides the default company configured in connection settings. | ### Request Body _Required._ A batch of tracking categories to write in a single request. Each item is processed independently: some may succeed while others fail, and the response carries one result per item in the order they were sent. - `items` `array of object` **required** — The records to write. The per-connector limit is the real cap and is usually lower than the ceiling here: read `batch_support.resources[].max_items` on the Connector API for the connector you are calling, or the resource gotchas. This ceiling exists so an oversized array is rejected by request validation before any per-item work runs, rather than after it. - `_ref` `string` — A caller-supplied reference for this item, echoed back on the matching result so each outcome can be tied to the record it came from. Must be unique within the request. Never sent to the connector. — example: `item-1` - `data` `object` **required** — The writable shape of TrackingCategory for a batch create. Identical to [TrackingCategory](the model returned on reads) with the read-only properties removed — the same properties the single-record create endpoint rejects, so a batched record and a single-record create accept exactly the same body. - `parent_id` `string` — A unique identifier for an object. — example: `12345` - `parent_name` `string` — The name of the parent tracking category. — example: `Area` - `name` `string` — The name of the tracking category. — example: `Department` - `code` `string` — The code of the tracking category. — example: `100` - `status` `string` — Based on the status some functionality is enabled or disabled. — enum: `active`, `inactive` — example: `active` - `row_version` `string` — A binary value used to detect updates to a object and prevent data conflicts. It is incremented each time an update is made to the object. — example: `1-12345` - `pass_through` `array of object` — The pass_through property allows passing service-specific, custom data or structured modifications in request body when creating or updating resources. - `service_id` `string` **required** — Identifier for the service to which this pass_through should be applied. - `operation_id` `string` — Optional identifier for a workflow operation to which this pass_through should be applied. This is useful for Unify calls that are making more than one downstream request. - `extend_object` `object` — Simple object allowing any properties for direct extension. - `extend_paths` `array of object` — Array of objects for structured data modifications via paths. - `path` `string` **required** — JSONPath string specifying where to apply the value. — example: `$.nested.property` - `value` `any` **required** — The value to set at the specified path, can be any type. - `subsidiaries` `array of any` — The subsidiaries the account belongs to. - `id` `string` — The ID of the subsidiary. ### Responses #### 200 — Tracking Categories batch processed - `status_code` `integer` **required** — HTTP Response Status Code — example: `200` - `status` `string` **required** — HTTP Response Status — example: `OK` - `service` `string` **required** — Apideck ID of service provider — example: `quickbooks` - `resource` `string` **required** — Unified API resource name — example: `tracking-categories` - `operation` `string` **required** — Operation performed — example: `add` - `data` `array of object` **required** — One result per item in the request, in the order the items were sent. - `_ref` `string` — A caller-supplied reference for this item, echoed back on the matching result so each outcome can be tied to the record it came from. Must be unique within the request. Never sent to the connector. — example: `item-1` - `id` `string` — A unique identifier for an object. — example: `12345` - `downstream_id` `string` — The third-party API ID of original entity — example: `12345` - `status` `string` **required** — The outcome for this item. - `created` / `updated` — the record was written. - `failed` — it was not written, and `error` says why. - `uncertain` — the request to the connector did not complete (typically a timeout), so whether this record was written is genuinely unknown. Do not blindly retry: list the resource to find what exists first, or a retry may duplicate it. A `created` or `updated` result can also carry an `error`: the record was written, but work that runs after the write did not complete. Read this rather than `id` to decide what happened. `id` is present when the identifier could also be read back, which is not the same question — a written record whose id could not be parsed still reports `created`. — enum: `created`, `updated`, `failed`, `uncertain` — example: `created` - `error` `object` — Why this item did not complete. Present when `status` is `failed`, meaning the record was not written, and when `status` is `uncertain`, meaning it is unknown whether it was. Also present, more rarely, alongside `created`/`updated`: the record WAS written and post-write processing failed, so the item reports the error beside its success status. Per-item failures are independent — one item's rejection says nothing about the others. The exception is a failure of the request itself, such as a timeout: where a connector writes the whole batch in one call, every item shares that outcome and carries the same error. - `status_code` `number` — HTTP status code — example: `502` - `error` `string` — Contains an explanation of the status_code as defined in HTTP/1.1 standard (RFC 7231) — example: `Bad Gateway` - `type_name` `string` — The type of error returned — example: `PostWriteProcessingError` - `message` `string` — A human-readable message providing more details about the error. — example: `The record was written, but processing its response failed.` - `detail` `string | object` — Contains parameter or domain specific information related to the error and why it occurred. — example: `The record was written, but processing its response failed.` - One of: - Option 1: string - Option 2: object - `ref` `string` — Link to documentation of error type — example: `https://developers.apideck.com/errors#postwriteprocessingerror` - `warnings` `array of object` — Non-fatal problems with THIS item — a currency the connector could not match, for example, which is sent without it. Present per item rather than per request, because a caller with twenty records needs to know which one was affected. A warning does not imply the record was written: some are raised while preparing the item, before the write is attempted, so they can appear on a `failed` item too. Read `status` for what happened. - `type` `string` — example: `currency_not_configured` - `operation` `string` — example: `invoicesAdd` - `message` `string` — example: `Currency "CAD" is not configured for this organization -- the request was sent without currency_id.` - `status_code` `number` — example: `200` - `error` `string` - `_raw` `object` — Raw response from the integration when raw=true query param is provided #### 400 — Bad Request > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 401 — Unauthorized > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 402 — Payment Required > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 404 — The specified resource was not found > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### 422 — Unprocessable > Standard error response — see [Error Responses](https://developers.apideck.com/errors) #### default — Unexpected error > Standard error response — see [Error Responses](https://developers.apideck.com/errors) ---