Can AI agents automate SAP Ariba?

SAP Ariba is automatable today through REST APIs on the SAP Ariba Developer Portal. This record is the SAP Ariba source-to-pay and spend-management cloud as exposed through those portal APIs. It is not SAP Concur, SAP S/4HANA, Coupa, or Basware. Callers send HTTPS requests to regional runtime prefixes such as https://openapi.ariba.com/api/{api}/{version}/prod. Every request needs both an application key in the apiKey header and an OAuth 2.0 Bearer token. Tokens come from POST {oauth_server_url_prefix}/v2/oauth/token with grant_type=client_credentials and HTTP Basic credentials made from the OAuth client ID and secret. Access tokens default to 1440 seconds. Organization admins create applications, request per-API access for a realm, and wait for SAP to approve that access and issue an OAuth client ID. SAP Ariba limits customers to one application per realm and API. The Operational Reporting API for Procurement extracts JSON, or asynchronous ZIP files, for requisitions, purchase orders, receipts, invoices, invoice reconciliations, and contracts, with a 10,000-record cap. The Document Approval API can GET pending requisitions and invoices and PATCH their approval state to approve or deny. Use requires a current SAP Ariba or SAP Business Network license, a regional developer-portal account, and Intelligent Configuration Manager enablement for external approval. Vendor docs do not declare a first-party MCP server. The official MCP registry search for "SAP Ariba" 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: 6/10