Build with the
Amigo Treks API.

Request an API key

Submit your application name, contact email and intended use. Save the key returned below securely; it is shown only once and remains inactive until an administrator approves your request. Approval is not automatic.

Approved keys expire after one year. Request a replacement if a key is lost or expires. Contact Amigo immediately if a key is exposed so an administrator can revoke it.

Make your first request

Search for Everest trips from your terminal. Send your approved key in the Authorization header. Each key allows up to 60 requests per minute.

curl --get 'https://www.amigotrekking.com/api/agent/v1/search' \
  --data-urlencode 'q=everest' \
  --data-urlencode 'limit=3' \
  --header 'Authorization: Bearer YOUR_AGENT_API_KEY' \
  --header 'Accept: application/json'

Read search results in data.suggestions. For a trip result, use the slug from its href: /everest-base-camp-trek.html becomes everest-base-camp-trek. You can also get slugs from the trip catalog. Check the HTTP status before reading the response data.

Keep the key on your server, outside browser bundles, URLs and logs. A pending, invalid, expired or revoked key returns HTTP 401. Customer or administrator tokens cannot be used as agent keys.

Endpoint reference

The OpenAPI specification lists the public content operations and parameters.

Access and privacy

Agents can read published travel content, itineraries, departures and pricing. Customer accounts, login, private bookings, documents and payment records are not part of the integration API.

Do not collect customer passwords or request account tokens. Travelers manage their accounts and checkout on the Amigo website.

Connect an MCP client

Add the following URL to a client that supports Streamable HTTP. Configure the Authorization header as Bearer YOUR_AGENT_API_KEY using your approved key. Use the server card to inspect the connection metadata.

https://www.amigotrekking.com/api/mcp/public

Before invoking an enquiry tool, ask the traveler to confirm that you may send their contact details and trip request to Amigo. Submitting a request does not confirm a booking.

Errors and retries

Handle each endpoint’s response body alongside its HTTP status. Error formats vary by route.

Unknown route · 404

Check the path and slug against the specification. Agent endpoints return a JSON error when a route or published resource is unavailable.

Rate limit · 429

The agent API and MCP share a limit of 60 requests per minute per key. Honor Retry-After before retrying. Additional transport limits apply.

Read request failed

Retry transient GET or HEAD failures with bounded exponential backoff and jitter. Set a timeout and stop after a limited number of attempts.

Write result is uncertain

Check whether the enquiry was created before retrying. Use an idempotency mechanism only where the endpoint documents one; do not assume all writes support it.

Service reachability

GET /api/status confirms the web service responds. Check the operation you depend on before treating the catalog service as available.

Specifications and support