Query and manage ARC-issued debit, credit, and recall commission memos programmatically using ARC's Memo Manager API
domain: apidocs.dev.arccorp.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Email ARC to request API access, supplying your Agency/HOL, Airline Number, or GDS Identification, the environment you need (UAT or PROD), and your outbound source IP ranges in CIDR notation.
Once granted access, obtain a client ID and client secret from My Applications and exchange them for an OAuth2.0 bearer token via a client_credentials grant with scope=memos_api.
Send the bearer token in the Authorization header, then call the Search Memos endpoint (/memos) to retrieve memo numbers and high-level info matching your criteria.
Call Get Memo Details (/memos/details) for full detail on specific memo numbers, and Get Attachments (/memos/attachments/{attachmentId}) to download supporting documents.
To act on an open memo, call Pay Memo (/memos/pay) or Dispute Memo (/memos/dispute) as appropriate; disputes can subsequently be accepted or rejected by the carrier through the corresponding endpoints.
Known gotchas
API access is not self-serve — you must request credentials by email and allow-list your source IPs in CIDR notation before any sandbox or production call will authenticate.
Pay, dispute, and correspondence actions are restricted by memo status — only non-closed (Open or Inactive) memos accept these actions; attempting them on a closed memo will fail.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?