Interests a contact

PUT/api/v1/contacts/{contact}/interests
Requires anorganization API keywith the scopecontacts:write

Parameters

NameInTypeDescription
contactrequiredpathstringThe contact identifier.

Request

PUT/api/v1/contacts/{contact}/interests
curl -X PUT 'https://app.mailyte.com/api/v1/contacts/01JBT8XQ2M9WYC3K4F6R7S8T9V/interests' \
  -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>
    • objectstringinterest
    • idstring
    • namestring

      The answer, as a contact reads it.

    • categoryobject

      The question this answers. Included because an answer alone is ambiguous — "Events" means nothing until you know which question it belongs to.

      • idstring

        NULL MEANS UNKNOWN — the category relation was not loaded.

      • titlestring

        NULL MEANS UNKNOWN — the category relation was not loaded.

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.