Developer documentation
Two integration surfaces, one live accommodation network.
Use MCP when an AI agent needs structured tools and traveler-aware workflows. Use the public REST API for anonymous catalog discovery in a conventional HTTP client. Both surfaces return structured JSON and point back to ATA’s direct booking experience.
Public REST discovery
Inspect the catalog without credentials.
The published OpenAPI document intentionally covers only anonymous, read-only endpoints. It excludes internal administration, authenticated traveler data, holds, and booking writes.
Example
curl "https://api.atatravel.cloud/public/stays/properties?city=Puerto%20Vallarta"MCP for agents
Initialize a Streamable HTTP session, inspect tools, and let tool schemas guide each call. Live tool results remain the source of truth for dates, occupancy, price, and policy fit.
Approval for writes
Catalog reads are public and rate-limited. Inventory holds, reservation requests, booking actions, and payment steps require traveler approval through ATA’s verification or handoff flow.
Predictable failures
REST failures use JSON responses. Clients should branch on the HTTP status and error code, respect rate limits, and avoid treating descriptive content as proof of live availability.
Need integration help?
Send a technical question or report a security or abuse concern.