# Adobe Workfront > Adobe's enterprise work-management platform for marketing and creative operations. Its developer > surface is four distinct APIs plus a hosted MCP server: the versioned core REST API at /attask/api > (v22.0, no OpenAPI but an anonymous object-metadata contract covering 174 objects), the Workfront > Planning API published as first-party OpenAPI 3.0.1 and 3.1.0 documents, the Event Subscription API > for outbound webhooks, and the Document Webhooks API that third-party document stores implement. This file is generated by API Evangelist from the Adobe Workfront profile at https://github.com/api-evangelist/workfront. Adobe publishes its own llms.txt for the documentation host at https://experienceleague.adobe.com/llms.txt (harvested verbatim to llms/workfront-experienceleague-llms.txt); this one is scoped to the Workfront API surface. ## APIs - [Adobe Workfront API](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/api-general-information/api-basics): The core REST API. `https://{customer-domain}.my.workfront.adobe.com/attask/api/v22.0/{objCode}/{id}`. GET reads and searches, POST inserts, PUT edits, DELETE removes. Auth: `SessionID` header, or OAuth2. - [Workfront Planning API v2](https://developer.adobe.com/wf-planning/api/v2): OpenAPI 3.1.0, 21 paths, 49 operations, 74 schemas. Workspaces, record types, records, fields, views, permissions. OAuth 2.0 only. - [Workfront Planning API v1](https://developer.adobe.com/wf-planning/api/v1): OpenAPI 3.0.1, 7 paths, 10 operations. Still targeted by the Workfront Fusion connector. - [Event Subscription API](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/event-subscriptions/event-subs-api): Outbound webhooks. Subscribe to CREATE/UPDATE/DELETE on 30 object types; payloads carry oldState, newState and eventTime. - [Document Webhooks API](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/document-webhooks-api/document-webhooks-api): The interface a third-party document store implements so Workfront can browse and manage documents in it. - [Adobe Workfront MCP Server](https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/workfront-mcp-server-overview): `https://mcp.workfront.adobe.com/mcp/v1/workfront`. 87 documented tools across Approvals, Planning and Workflow/Insights. OAuth 2.1 with PKCE and dynamic client registration. ## Specs - [Workfront Planning v2 OpenAPI](https://developer.adobe.com/wf-planning/v2.json): OpenAPI 3.1.0, published by Adobe. - [Workfront Planning v1 OpenAPI](https://developer.adobe.com/wf-planning/v1.json): OpenAPI 3.0.1, published by Adobe. - [Workfront API object metadata](https://api-cl01.my.workfront.com/attask/api/v22.0/metadata): The core API's machine-readable contract. Anonymous. Returns all 174 objects; each object's own `/metadata` endpoint returns its fields, references, collections, searchable fields, named queries, actions and supported operations. - [OAuth authorization-server metadata](https://mcp.workfront.adobe.com/.well-known/oauth-authorization-server): RFC 8414. - [OAuth protected-resource metadata](https://mcp.workfront.adobe.com/.well-known/oauth-protected-resource): RFC 9728. ## Docs - [Workfront API documentation hub](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/workfront-api) - [API basics](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/api-general-information/api-basics): operations, authentication, query limits, pagination, bulk. - [API Explorer](https://developersupport.workfront.com/page-api-explorer.html): browse every object's fields, references, collections and actions, per API version. - [API versioning and support schedule](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-api/api-notes/api-version-support-schedule): dated release and retirement table for versions 6 through 22. - [Planning API basics](https://experienceleague.adobe.com/en/docs/workfront/using/adobe-workfront-planning/adobe-workfront-planning-general-information/planning-api-basics) - [Create OAuth2 applications](https://experienceleague.adobe.com/en/docs/workfront/using/administration-and-setup/configure-integrations/create-oauth-application) - [Product releases](https://experienceleague.adobe.com/en/docs/workfront/using/product-announcements/product-releases/product-releases) - [Adobe status](https://status.adobe.com/) - [Adobe Trust Center](https://www.adobe.com/trust.html) ## Agent surface - [Workfront MCP tools](https://experienceleague.adobe.com/en/docs/workfront/using/basics/workfront-mcp-server/workfront-mcp-server-tools): the 87-tool catalogue, with read/write action class per tool. - [Adobe Workfront agent Skills](https://github.com/adobe/skills/tree/main/plugins/workfront): first-party Agent Skills, Apache-2.0. - No A2A agent card is served on any Workfront or Adobe host. ## Things an agent has to know - Authentication differs per surface. The core API takes a `SessionID` header; the Planning API takes an OAuth 2.0 bearer and explicitly rejects `sessionID` and `apiKey`; the MCP server takes an OAuth 2.1 bearer. API keys and the `/login` endpoint are deprecated. - Neither published Planning OpenAPI declares `securitySchemes`, so a generated client will not send an `Authorization` header. - There is no idempotency contract on any Workfront surface. A retried write is a second write. - No rate-limit response headers are published anywhere. The Planning API returns 429; the core API caps result sets ($$LIMIT max 2000, 50,000 objects, depth 4, batch 100, 8,892-byte URI) rather than request rate. - Planning v2 errors are RFC 7807 problem details — branch on `errorCode`, not on the HTTP status; 403 is frequently a capacity limit rather than a permission failure. Planning v1 uses a numeric `type` code instead. - Bulk operations return 207 Multi-Status on partial success. Walk the per-item results. - Workfront IDs are 32-character hex strings with no type prefix, so `objCode` must always travel with an ID. - The base URL is per-customer: `.my.workfront.adobe.com`, found in Workfront under Setup > System > Customer Info.