Postman Collection for Coupa APIs

Revised: 26 July 2022

To help partners and customers with the API implementation, Coupa has come up with a POSTMAN collection covering some of the common API use cases that we come across during our implementations. We believe this will help the customers and partners not only to reduce the implementation time but also to explore various integration options using Coupa APIs.

OAuth2/OIDC - Postman Collection

Note

Make sure that the POSTMAN in your system is upgraded to the latest version

Postman Collection for Coupa APIs using OAuth Access Tokens

Setup

You will need the POSTMAN tool installed in your local before you start the collection steps given below. 

  1. Download the collection file attached below as per the desired Accept header. Coupa supports application/xml or application/json accept headers
    Accept Header - application/xml - Coupa Postman Collection - XML
    Accept Header - application/json - Coupa Postman Collection - JSON
  2. Click on the "Import" option within the POSTMAN tool

    clipboard_e039ec9284b39b9a2c4d8b5d533f21f9b.png
     
  3. Upload the file you downloaded in step#1 and click Import

    clipboard_e049ae643742092bba79f6a73ca1e122a.png
  4. Add a new Environment by clicking "New" and selecting "Environment" as shown below

    clipboard_ef686a30fdd3ba910f6f0119f79e26704.png
  5. Enter the following variables and their values and the same environment with a meaningful name
Variable Value
URL https://customer-name.coupahost.com/api
token_url https://customer-name.coupahost.com/oauth2/token
client_id Available in the OAuth Client created at https://customer-name.coupahost.com/oauth2/clients
client_secret Available in the OAuth Client created at https://customer-name.coupahost.com/oauth2/clients
scope Available in the OAuth Client created at https://customer-name.coupahost.com/oauth2/clients
treasury_url

Enter the Coupa Treasury Host
Example: https://coupa.treasury.host.com/api

API Keys - Postman Collection

Note

API Keys Deprecation
          R32 - OAuth2.0 is the only available option for new customers
          R34 - new API keys can no longer be issued to existing customers
          R35 - API keys will no longer be supported
          More Details