Transaction API
Number of APIs: 3
Home
Transaction API is ARC’s first step towards real-time transaction processing. The transaction providers (NDC Carriers, System Providers, Travel Technology Partners) should have the capability to send their transaction data to ARC via the API instead of the current SPRF flat files.
Getting Started
Requesting Access
- Please contact NDC@ARCcorp.com for more details
Authentication Requirements
Authentication is required to access ARC’s APIs in sandbox and production environments. ARC uses OAuth2.0, an industry-standard protocol, to authenticate users. Once ARC has granted you access to an API, you must obtain an OAuth2.0 bearer token.
To receive your bearer token:
Acquire your client ID and client secret from ARC
Post: https://eum-okta-cic-prod.arctravel.auth0app.com/oauth/token
Provide the following in your request to receive your bearer token. Then use your bearer token in the “Authorization” header to submit requests to the API.
client_id = {{clientId}}
client_secret = {{clientSecret}}
audience = {{audience}}
granttype = clientcredentials
Release Notes
2024-03-21
The initial release of Transaction API.
-
transactions - Post transactions POST {{baseUrlTransactionAPI}}/transactions
-
summaries-{requestId} - Get summaries GET {{baseUrlTransactionAPI}}/summaries/:requestId
-
clients-{clientId}-rotate-secret - Rotate Secret POST {{baseUrlTransactionAPI}}/clients/:clientId/rotate-secret