List contact tags

GET/api/v1/contact-tags
Requires anorganization API keywith the scopecontacts:read

Request

GET/api/v1/contact-tags
curl -X GET 'https://app.mailyte.com/api/v1/contact-tags' \
  -H 'Authorization: Bearer mk_live_YOUR_API_KEY'
The key names its own organization, so no X-Organization-ID header is needed.

Response

Success.

  • dataarray<object>
    • objectstringcontact_tag
    • idstring

      Unique identifier for the tag.

    • namestring

      The label as it was first written. Tags are matched case-insensitively — "VIP" and "vip" are one tag — and the spelling kept is whichever was used first, so a contact never shows two chips for the same label.

    • contact_countinteger

      How many contacts carry this tag. NULL MEANS NOT INCLUDED — this response did not count them — never that the tag is unused. It is present when listing tags and absent when a tag is returned as part of a contact, where counting every tag would cost a query per chip.

    • created_atstring

Returned inside the standard envelope.

Errors

StatusWhen
401The API key is missing, unknown, revoked or expired. All four answer identically, on purpose: distinguishing them would confirm which keys exist.
403The key is valid but may not do this: it lacks the required scope, its IP allowlist does not include you, or this endpoint does not accept API keys.
404No such resource in this organization.
422The request was understood but the values were not acceptable.
429Too many requests, or the organization has spent its sending allowance. `Retry-After` says how long to wait.

Every status, with what causes it and what to do, is on the error reference.