# Marketo Engage (Adobe) > Marketo Engage is Adobe's B2B marketing automation platform. Its REST API gives > programmatic access to person records ("leads"), activities, programs, > campaigns, static lists, custom objects, marketing assets, bulk import/export, > and user administration. Adobe publishes five machine-readable specifications > covering 367 operations. This file was GENERATED by API Evangelist from those > specifications and from Adobe's own developer documentation; Marketo publishes > no llms.txt of its own. ## Read this first — three things that will break a naive integration - **HTTP 200 is not success.** Marketo returns HTTP 200 for authentication failures, rate-limit exhaustion, quota exhaustion and per-record write failures. Read the boolean `success` member of the JSON body, and on batch writes read each record's `status` and `reasons` array. Adobe instructs callers not to evaluate the HTTP reason phrase at all. - **There is no shared host.** The base URL is `https://{munchkinId}.mktorest.com/rest`, unique to every subscription and read from Admin > Integration > Web Services. The specs Adobe publishes carry `host: localhost:8080` for this reason. - **No rate-limit headers exist.** 100 calls per 20 seconds, 50,000 calls per day and 10 concurrent calls are enforced, but exhaustion arrives as in-body codes 606 / 607 / 615 with HTTP 200 and no Retry-After. Poll `getDailyUsageUsingGET` to see the budget. ## Live breaking changes - 2026-08-31 — the `access_token` query/form parameter is removed. Use `Authorization: Bearer`. - 2026-09-30 — Get Lead Activities / Get Lead Changes with a `listId` fail (error 1003) when the static list holds 10,000+ leads. - 2026-07-31 — the SOAP API was removed. Merge Leads now rejects more than 25 `leadIds` (error 1080). ## APIs - [Lead Database API](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api): People, activities, companies, opportunities, custom objects, static lists, campaigns, program members, bulk import/export. 147 operations under /rest/v1 and /bulk/v1. - [Asset API](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api): Emails, landing pages, forms, templates, snippets, segments, folders, files, tokens. 199 operations under /rest/asset/v1. - [User Management API](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api): Users, roles, workspaces, invitations. 12 operations under /userservice/management/v1. - [Identity](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication): OAuth 2.0 client-credentials token issuance at /identity/oauth/token. - [Data Ingestion API](https://mkto-ingestion-api.adobe.io): Asynchronous high-volume sync of persons, companies, custom objects, program members and list membership. 7 operations. The only Marketo surface with correct HTTP status semantics (202/400/401). ## Specs - [Lead Database (Swagger 2.0)](https://raw.githubusercontent.com/AdobeDocs/marketo-apis/main/static/swagger-mapi.json) - [Asset (Swagger 2.0)](https://raw.githubusercontent.com/AdobeDocs/marketo-apis/main/static/swagger-asset.json) - [User Management (Swagger 2.0)](https://raw.githubusercontent.com/AdobeDocs/marketo-apis/main/static/swagger-user.json) - [Identity (Swagger 2.0)](https://raw.githubusercontent.com/AdobeDocs/marketo-apis/main/static/swagger-identity.json) - [Data Ingestion (OpenAPI 3.0.1)](https://raw.githubusercontent.com/AdobeDocs/marketo-apis/main/static/swagger-data-ingestion.json) ## Docs - [Marketo Developer Guide home](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/home) - [REST API overview and quotas](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/rest-api) - [Authentication](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication) - [Base URL](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/base-url) - [Custom Services and the Access API permission list](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/custom-services) - [Error Codes](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/error-codes) - [Endpoint Reference](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/endpoint-reference) - [Webhooks](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/webhooks/webhooks) - [Javascript API — Munchkin, Forms 2.0, Web Personalization, Predictive Content](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/javascriptapi/javascript-api) - [Forms 2.0 API Reference](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/javascriptapi/forms-api-reference) - [Release notes (where API breaking changes are announced)](https://experienceleague.adobe.com/en/docs/marketo/using/release-notes/current) - [API Documentation site](https://developer.adobe.com/marketo-apis/) - [Adobe Experience League llms.txt](https://experienceleague.adobe.com/llms.txt): Adobe-wide, product-documentation oriented, with a Marketo Engage section. Not developer-API specific. ## Authorization - OAuth 2.0, two-legged client credentials. `GET|POST {identityUrl}/oauth/token?grant_type=client_credentials&client_id=…&client_secret=…` - Access tokens live 3,600 seconds and belong to exactly one LaunchPoint Custom Service. - There are **no OAuth scopes.** The `scope` field in the token response is the API-Only user's email address. Authorization is 24 role permissions under the "Access API" tree — see the Custom Services page. - Error 603 means authenticated but not permitted, or blocked by IP allowlist. ## Artifacts published by API Evangelist - Authentication profile: https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/authentication/marketo-authentication.yml - Permission vocabulary: https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/scopes/marketo-scopes.yml - Error registry (66 codes): https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/errors/marketo-error-codes.yml - API conventions: https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/conventions/marketo-conventions.yml - Rate limits: https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/rate-limits/marketo-rate-limits.yml - Lifecycle and deprecations: https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/lifecycle/marketo-lifecycle.yml - Data model: https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/data-model/marketo-data-model.yml - Event surface (AsyncAPI 2.6): https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/asyncapi/marketo-events-asyncapi.yml - Agent skills: https://raw.githubusercontent.com/api-evangelist/marketo/refs/heads/main/skills/_index.yml ## What Marketo does not publish - No MCP server. Adobe's own llms.txt lists only AEM MCP servers. - No A2A agent card on any Adobe or Marketo host. - No GraphQL endpoint. - No AsyncAPI document. - No sandbox, test mode, or test credentials — every call is against live data. - No first-party REST client library in any package registry. - No Sunset or Deprecation response headers, despite three dated breaking changes in flight.