Skip to main content
GET
Get all tags

Overview

Retrieve all tags configured for your organization. This endpoint returns tag IDs, names, types, and visual properties that you can use for contact tagging, filtering, and organization. This is an essential endpoint for building tag selection interfaces and getting the tag IDs needed for the tag update endpoints.

Use Cases

  • Tag Selection UI: Populate dropdowns or multi-select components with available tags
  • Get Tag IDs: Find tag IDs for use with update/assignment endpoints
  • Tag Management: Display all tags in admin interfaces
  • Filtering Options: Build dynamic filters for contacts based on available tags
  • Integration Sync: Sync tag definitions with external systems
  • Tag Validation: Verify tag IDs before attempting to assign them

Authentication

This endpoint requires authentication using an API key. Include your API key in the request header:

Response Structure

Returns an array of tag objects:

Example Request

Example Response

Common Use Cases

1. Build Tag Selection Dropdown

2. Get Tag ID by Name

3. Group Tags by Type

4. Get Tags by Color Variant

5. Build Tag Filter Interface

6. Sync Tags to External System

7. Cache Tags for Performance

Tag Entity Types

Important: TICKET tags can only be assigned to contacts that have an active ticket.

Color Variants

Tags have color variants for visual organization in your UI:

Integration Tags

Tags can be synced from external CRM systems. These have:
  • integration_token_id: The CRM integration token
  • integration_provider: CRM name (e.g., “salesforce”, “hubspot”, “pipedrive”)
  • integration_external_id: The tag ID in the external system
These allow bi-directional sync between Vambe and your CRM.

Error Responses

Important Notes

  • Tag IDs are Numeric: Unlike most other IDs in the API (UUIDs), tag IDs are integers
  • Organization Scoped: Returns only tags from your organization
  • Includes Integration Tags: Shows both manually created and CRM-synced tags
  • No Pagination: Returns all tags (typically not a large dataset)
  • Cache-Friendly: Tags don’t change frequently, safe to cache

Response Characteristics

  • All Tags: Returns all tags regardless of type
  • No Filtering: Currently no query parameters to filter tags
  • Alphabetical: Not sorted - consider sorting client-side if needed
  • Complete List: Includes both active and CRM-integrated tags

Using Tag IDs

After getting tag IDs from this endpoint, use them with: Update Contact Tags (Replace all):
Create Tags by Channel (Additive):

Complete Workflow Example

Tag Display Component Example

Best Practices

1. Cache Tag List

2. Create Tag Lookup Map

3. Filter Tags by Type for UI

Performance Tips

  • Cache the Response: Tags change infrequently - cache for 5-10 minutes
  • Client-side Operations: Sort, filter, and search tags on the client side
  • Load Once: Fetch tags once when your app loads, reuse throughout session
  • Update on Change: Refresh cache when users create/edit tags in your UI

Notes

  • No Pagination: All tags are returned in a single response
  • Small Dataset: Most organizations have < 100 tags
  • Unique Names: Tag values must be unique per organization and entity type
  • Case Sensitive: Tag names are case-sensitive
  • ID Format: Tag IDs are integers (not UUIDs like other resources)

Headers

x-api-key
string
required

API key needed to authorize the request

Response

Tags retrieved successfully.

id
number
Example:

1

value
string
Example:

"vip-customer"

variant
string

Color variant for UI display

Example:

"amber"

entity_type
string

CONTACT or TICKET

Example:

"CONTACT"

created_at
string
Example:

"2024-01-15T10:00:00.000Z"

client_id
string
Example:

"550e8400-e29b-41d4-a716-446655440000"