Recipes (automation)

GET/api/v1/automations/recipes
Requires anorganization API keywith the scopeautomations:read

Request

GET/api/v1/automations/recipes
curl -X GET 'https://app.mailyte.com/api/v1/automations/recipes' \
  -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>
    • keystring
    • namestring
    • descriptionstring
    • categorystringwelcome | recovery | loyalty | reengagement | milestones | nurture | other
    • phaseinteger
    • entry_rulestringonce | every_time | cooldown
    • cooldown_hoursinteger
    • placeholdersarray<string>

      Node ids the customer must complete before publishing.

    • graphobject

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.