Can AI agents automate Coupa?

Coupa Core is automatable today through its documented REST APIs. This record is the Coupa Core platform REST surface, including purchase orders, invoices, and requisitions. It is not SAP Concur, SAP Ariba, or Basware. Treasury, CSO, and Supply Chain Optimization stay out of this identity. Callers use HTTPS against a tenant host of the form https://{instance}.coupahost.com/api/{resource}. Authentication is OAuth 2.0 / OIDC. API keys are deprecated for Core integrations. Tenant admins create OAuth clients under Setup > Oauth2/OpenID Connect Clients. Client Purpose is mandatory. Client-credentials tokens are minted at POST /oauth2/token and last about 24 hours (expires_in 86399 seconds). Optional IP allowlists and account-group or business-group restrictions apply. REST supports GET, POST, and PUT in XML or JSON; deleting data is not supported for any resource except where a resource documents a destroy action, such as requisitions. Purchase Orders API can query, create external POs, update, issue, cancel, close, and reopen. Invoices API can create, query, submit, abandon, and dispute. Requisitions API can create, submit, and update carts. A GraphQL endpoint at /api/graphql is OIDC-authenticated, client-credentials and read-scopes only; mutations are not supported. No official Core SDK or CLI was established from the opened pages. Vendor docs do not declare a first-party MCP server. The official MCP registry search for coupa returned zero servers; that is discovery silence, not proof of absence. iPaaS catalogs were not opened. Computer-use viability is unassessed.

Best path today: api · Overall automatability: 7/10