---
updatedAt: 2026-07-29T13:49:08.000Z
agentTools:
  projectIndex: https://docs.axonius.com/llms.txt
---

# Coupa

 

Coupa is a spend-management platform that offers procurement, sourcing, invoice, expense and payment automation to centralize and control direct and indirect spend across the source-to-pay lifecycle.

## Before You Begin

### Required Ports

* TCP port 443 (HTTPS)

### Authentication Methods

OAuth 2.0 Client Credentials Grant Type Authentication

### APIs

Axonius uses the Coupa Core API. The following endpoints are called:

* `POST /oauth2/token` - Obtains an OAuth 2.0 access token using client credentials
* `GET /api/contracts` - Retrieves contracts (paginated)

### Required Permissions

The following permissions are required:

#### OAuth 2.0 Scope

The OAuth2/OpenID Connect client must be granted the following scope:

* `core.contract.read` — Provides read access to Contract objects via the Coupa API

### Supported From Version

Supported from Axonius version 8.0.12.0

### Setting Up Coupa to Work with Axonius

To allow Axonius to connect to Coupa, create an OAuth2/OpenID Connect client in your Coupa instance with the Client Credentials grant type and the required scope.

1. Log in to your Coupa instance as an administrator with integration privileges.
2. Go to **Setup** > **OAuth2/OpenID Connect Clients**. You can type `oauth` in the Search box to find it quickly.
3. Click **Create**.
4. For **Grant Type**, select **Client credentials**.
5. Specify a **Name**, **Login**, **Contact info**, and **Contact Email** for the client.
6. Under **Scopes**, select `core.contract.read`.
7. Click **Save**.
8. Copy the **Client Identifier** (Client ID) and click **Show/Hide** to reveal and copy the **Client Secret**. Store these values securely — the secret will not be displayed again.

> **Note:** Coupa instance addresses take the form of `https://{organization_name}.coupahost.com` (for customer instances) or `https://{organization_name}.coupacloud.com` (for partner and demo instances). Use the full base URL (without trailing slash) as the **Host Name or IP Address** when connecting in Axonius.

For more information, see [OAuth 2.0 Getting Started with Coupa API](https://compass.coupa.com/en-us/products/total-spend-management-platform/integration-playbooks-and-resources/integration-knowledge-articles/oauth-2.0-getting-started-with-coupa-api) and the [Contracts API](https://compass.coupa.com/en-us/products/product-documentation/integration-technical-documentation/the-coupa-core-api/resources/transactional-resources/contracts-api-\(contracts\)).

<br />

## Connecting the Adapter in Axonius

Navigate to the Adapters page, search for Coupa, and click on the adapter tile.

Click **Add Connection**.

To connect the adapter in Axonius, provide the following parameters:

### Required Parameters

1. **Host Name or IP Address** - The base URL of your Coupa instance. Example: `https://mycompany.coupahost.com`
2. **Client ID** - The Client Identifier generated when creating the OAuth2/OpenID Connect client in Coupa.
3. **Client Secret** - The Client Secret generated when creating the OAuth2/OpenID Connect client in Coupa.
4. **Verify SSL** - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see [SSL Trust & CA Settings](/docs/certificate-settings#ssl-trust-ca-settings).

<br />

<br />

### Optional Parameters

1. **HTTPS Proxy** - Connect the adapter to a proxy instead of directly connecting it to the domain.
2. **HTTPS Proxy User Name** - The user name to use when connecting to the value supplied in **Host Name or IP Address** via the value supplied in **HTTPS Proxy**.
3. **HTTPS Proxy Password** - The password to use when connecting to the server using the **HTTPS Proxy**.

<br />

To learn more about common adapter connection parameters and buttons, see [Adding a New Adapter Connection](/docs/adding-a-new-adapter-connection).

<br />

<br />

<br />

***

Co-authored by [Augment Code](https://www.augmentcode.com/?utm_source=atlassian\&utm_medium=jira_issue\&utm_campaign=jira)