Developers

The first public API surface exposes route pages as structured content records.

The contract is intentionally small while the travel schema is still being specialized. The frontend already consumes the list endpoint to build the passport finder and uses a by-path fetch for each route page.

Core endpoints

GET https://api.visapony.com/healthz
GET https://api.visapony.com/openapi.json
GET https://api.visapony.com/api/v1/pages
GET https://api.visapony.com/api/v1/pages/by-path?path=/from/united-states/to/japan
POST https://api.visapony.com/mcp

Route shape

Published guides currently use the path pattern /from/:origin/to/:destination. Each record includes title, description, summary, coverage status, freshness, and an optional source URL.

Read llms.txt

Example requests

curl https://api.visapony.com/api/v1/pages

curl "https://api.visapony.com/api/v1/pages/by-path?path=/from/united-states/to/japan"

curl https://api.visapony.com/openapi.json