Overview
Client-mode REST API connector for the Coupa Core API: OAuth token plus purchase orders and requisitions and invoices and suppliers and receipts.BASE_ADDRESS defaults to https://YOUR_INSTANCE.coupahost.com. Topics use erp/coupa/<object>/<verb>.
Authentication
OAuth 2.0 / OIDC client credentials. OAuthToken posts the form grant_type=client_credentials&client_id=…&client_secret=…&scope=core.purchase_order.read … to /oauth2/token; the access token (about 24 h) goes in Authorization: Bearer {value.json.access_token}. Scopes per resource (core.purchase_order.read, core.invoice.read, core.supplier.read, core.requisition.write …). Legacy X-COUPA-API-KEY is deprecated.Notes
- The OIDC client is created by a Coupa admin in the customer instance (Setup > Integrations > OAuth2/OpenID Connect Clients); no partner program is needed.
- OAuthToken is the only event whose body carries a credential (the token form), the same pattern as the Box OAuthToken event. Never retain erp/coupa/oauth/#.
- Use query filters such as updated-at[gt]=2026-10-01&limit=50 and return_object=shallow to keep responses small.
Basic Syntax
Sources
- https://docs.coupa.com/en/developer-documentation/the-coupa-core-api/oauth-2.0-and-oidc
- https://docs.coupa.com/en/developer-documentation/the-coupa-core-api/oauth-2.0-and-oidc/set-up-an-openid-connect-client
- https://docs.coupa.com/en/developer-documentation/the-coupa-core-api/resources/transactional-resources/purchase-orders-api-purchase_orders

