Sign in

v1

latestOpenAPI 3.0.32026-07-26362271803.3 KB
Company Objects

List Custom Dimensions

    Retrieve a list of transaction tags (custom dimensions) with optional filtering and sorting.

    Supports including soft-deleted records for audit and recovery purposes.
    When include_deleted=true, returns ONLY deleted records instead of active records.
    Deleted records contain minimal data: 'id', 'is_deleted=true', 'deleted_at' timestamp,
    and 'last_modified_at'. When 'false' or omitted, returns ONLY active records.
    This provides clean separation between active and deleted data.
get/coa/api/tag

Query parameters

exclude_tagsstring

Comma-separated list of tag IDs to exclude

groupinteger

Filter by tag group ID

include_deletedboolean

When set to 'true', returns ONLY deleted records instead of active records. Deleted records contain minimal data: 'id', 'is_deleted=true', 'deleted_at' timestamp, and 'last_modified_at'. When 'false' or omitted, returns ONLY active records. This provides clean separation between active and deleted data.

include_inactiveboolean

If true, include inactive tags

last_modified_at__gtestring

Filter for records modified on or after this timestamp. Format: ISO 8601 (e.g., '2024-01-01T00:00:00Z' or '2024-01-01'). Works with both active records and deleted records (filters by deletion time for deleted records).

last_modified_at__ltestring

Filter for records modified on or before this timestamp. Format: ISO 8601 (e.g., '2024-12-31T23:59:59Z' or '2024-12-31'). Works with both active records and deleted records (filters by deletion time for deleted records).

limitinteger

Number of results to return per page.

no_groupboolean

If true, only return tags without a group

offsetinteger

The initial index from which to return the results.

parentinteger

Filter by parent tag ID

qstring

Search query - searches by tag name or group name

sortstring

Sort order. Use field name for ascending, -field for descending. Special field: group_name. Default: name

Response

countinteger required
nextstring uri nullable
previousstring uri nullable

Example response

{
  "count": 123,
  "next": "http://api.example.org/accounts/?offset=400&limit=100",
  "previous": "http://api.example.org/accounts/?offset=200&limit=100"
}