API Reference
Atlas API endpoint reference for request schemas, response fields, and samples organized by workflow and capability.
Last updated
Was this helpful?
Atlas API endpoint reference for request schemas, response fields, and samples organized by workflow and capability.
💬 Need help? If you're stuck, ask Eva in the Help Center for instant diagnostics.
All API Reference endpoint examples on this site show sandbox base URLs.
For production traffic, use the production API base URLs shown in ATRIP under My Profile → Company Information.
Production uses two API base URLs:
one for search traffic
one for all other transaction APIs
Do not send live traffic to sandbox endpoints.
Use this section for exact endpoint schemas, fields, and samples.
Start here when you need to:
confirm exact request and response fields
find the endpoint reference for a workflow
validate field-level implementation details after reading the guides
Use API Reference when you need exact endpoint-level details such as request fields, response fields, schemas, and samples.
Use Product Guides first when you need flow choice, sequence guidance, or business decisions.
Use Integration Guides when you need onboarding, sandbox, UAT, or go-live steps.
Start with the workflow group that matches the task.
Then open the exact endpoint page for the API you are implementing.
Start with Product Guides for workflow choice.
Use Integration Guides for sandbox, UAT, and production rollout.
Use this section for request and response details.
Use Support & Reference for troubleshooting, shared reference data, and updates.
Use MCP-Assisted Development when you need help finding the right workflow, comparing related APIs, or narrowing down the next integration step.
Use this section as the field-level source of truth after the workflow is clear.
After you confirm the endpoint schema, return to the matching workflow or integration page to continue implementation.
Last updated
Was this helpful?
Was this helpful?