List contact lists

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

Request

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

Response

Success.

  • dataobject
    • dataarray<object>
      • objectstringcontact_list
      • idstring

        Unique identifier for the list.

      • namestring
      • descriptionstring

        Optional free text describing what the list is for. `null` means NONE — none was written — never "we did not include it": it is a column on the row already read and it is present in a list response as well as on a single list. Nothing in the send path reads it — it is stored and handed back for your own operators.

      • contact_countinteger

        EVERY member of the list, whatever their state. An unsubscribed contact is still a member — membership and deliverability are separate facts here, and removing somebody from a list is not how an unsubscribe is recorded. So a list of 500 with 40 unsubscribes still reports 500; the mailable subset is `GET /contacts?list_id=…` filtered on `state`. Never null: the count is either already on the model or taken live.

      • created_atstring
      • updated_atstring
    • pagination_metaany

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.