Service documentation
This page is the human-readable companion to the API catalog advertised from the homepage via HTTP Link headers. It highlights the main web-facing routes agents and integrations are most likely to need.
Quickstart
Read-only catalog search, API metadata, and the public MCP server are available without authentication. Rate limits apply. Enquiry tools may be used only after the traveler explicitly consents to sharing their supplied contact details.
OpenAPI
GET https://www.amigotreks.com.np/openapi.jsonMCP Streamable HTTP URL
https://www.amigotreks.com.np/api/mcp/publicProduction behavior
Unknown API routes return HTTP 404 with an application/problem+json body containing stable status, code, and instance fields.
Rate-limited proxy responses preserve Retry-After, RateLimit-*, and X-RateLimit-* headers supplied by the API service.
Agents may retry GET and HEAD requests with exponential backoff and jitter. Write operations should be retried only when their documented idempotency mechanism is used.
Authentication
Protected customer operations use the OAuth 2.0 authorization-code flow with PKCE S256. The customer signs in and approves access; integrations must be pre-registered with an exact redirect URI. Public discovery and the public MCP server remain unauthenticated.
customer.readRead the customer's account, leads, activity, recommendations, companions, and referral dashboard.
customer.profileUpdate the customer's profile and profile image.
customer.documentsRead, upload, update, or delete the customer's travel documents.
customer.reviewsRead and submit the customer's reviews and review images.
customer.paymentsStart and finalize customer payment flows.
customer.offersRead customer-specific pricing and offers.
Discovery
These routes help agents and integrations understand the public site structure and trip inventory without requiring authentication.
/api/searchSearch trips, destinations, categories, and guide content.
/api/nav-catalogRead structured navigation and site discovery data.
/api/trip-suggestionsReturn curated trip suggestions for recommendations and cards.
/api/site-settingsRead selected public-facing site settings.
Leads and payments
These public routes support the website booking funnel, planner flows, and payment initiation. Validation and rate limiting still apply.
/api/leadsCreate contact, custom-trip, inquiry, and booking-request submissions.
/api/paymentsInitiate payment-related flows used by the website checkout experience.
Customer account
Customer routes support sign-in, account retrieval, documents, payments, and personalized recommendations. Protected routes require a customer bearer token.
/api/customer/loginStart a customer sign-in flow.
/api/customer/registerRegister a new customer account.
/api/customer/meReturn the authenticated customer profile used by the account dashboard.
Status
The API catalog also advertises a lightweight status endpoint so agents and integrations can confirm the web API is reachable before relying on other routes.
/api/statusReturn a lightweight API health payload.