Safeguard Docs
Compliance ConnectorsSetup by categoryVendor Procurement

SAP Ariba

Connect SAP Ariba to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Record your SAP Ariba connection as vendor procurement evidence. Automated collection is not available for this provider yet.

CategoryVendor Procurement
Connect withAPI token
What a connection producesConnection record

Connect with an API token

  1. In SAP Ariba:

    1. At https://developer.ariba.com/api, choose your region from the Portals dropdown and sign in to the SAP Ariba Developer Portal.
    2. Create the application: click Create application on the home page (or, as an Organization admin, go to Manage › Applications and click the + symbol near the search bar).
    3. Fill out the Create a new application form with an application name and description, then click Submit. This generates the application's Application key.
    4. As a user with the Organization admin role, go to Manage › Applications, select the application and choose Actions › Request API access.
    5. In the Application Details dialog, choose the API from Select an API, tick the solution (Procurement, Sourcing, SAP Business Network (formerly Ariba Network) or Customer ID) and pick the realm(s), then click Submit.
    6. Wait for SAP Ariba to approve the request; the Organization admin receives an email with the OAuth client ID for the application.
    7. As an Organization Admin, click Manage in the left-hand navigation menu, select the application and choose Actions › Generate OAuth Secret, then click Submit.
    8. Copy the OAuth Secret and Base64 Encoded Client and Secret right away and store them securely; they are displayed only temporarily.
    9. Access is granted per API and realm in the Request API access step; request only the read-oriented API you need (for example a reporting or approval API) and only the realms you want covered.

    Where to find the other values:

    • API token / Personal access token: Manage › select the application: the Application key field holds the apiKey and the OAuth client ID field holds the client ID; the OAuth Secret / Base64 Encoded Client and Secret come from Actions › Generate OAuth Secret.
    • Base URL (optional): The OAuth server URL prefix and API host for your regional data center are shown on the SAP Ariba Developer Portal (US example API host: https://openapi.ariba.com).
    • Account / Org / Workspace (optional): Your realm names appear as the realm choices in the Application Details dialog of Actions › Request API access (or the AN-ID for SAP Business Network).

    SAP Ariba shows the secret only once, so copy it before you leave the page.

    Source is SAP's 'Help for the SAP Ariba Developer Portal' PDF (document version 2608). SAP Ariba does not issue a single token: API calls need the Application key (apiKey) plus an OAuth access token obtained with the OAuth client ID and secret (or mutual TLS). Production access requires SAP Ariba approval of the API access request, and only one application per realm/API combination is allowed. Generating a new OAuth secret invalidates the previous one. Developer portal instances are regional; SAP Business Network APIs use the US data center.

    Source: help.sap.com, help.sap.com, checked 2026-10-07.

  2. On Compliance › Connectors, open SAP Ariba, click Connect, choose API token and fill in:

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. Click Connect with token.

Frameworks

SAP Ariba publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

FrameworkEvidenceControlsTests
SOC2AttestationCC6.2, CC6.31
ISO/IEC 27001AttestationA.5.181
HIPAA Security RuleAttestation164.308(a)(3)1
PCI DSSAttestation7.2.41
NIST CSF 2.0AttestationPR.AA-051

These tests are switched on per workspace by the Safeguard team.

On this page