The API Report CardAPI Index
G Adventures

G Adventures API

gadventures.com

G Adventures runs a public REST API at rest.gadventures.com with instant self-serve sandbox and production keys. Read and content integrations need no approval; booking writes require a Sherpa Agency contract via sales. The only official SDK is Python, and there is no OpenAPI spec.

Last verified: July 2026Hospitality & Travel
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic REST API at rest.gadventures.com with JSON and XML, spanning tours, departures, bookings, and reference data.
AccessGOODSandbox and production keys are issued instantly on signup; only booking writes need a Sherpa Agency contract.
CoverageGOODTours, departures, accommodations, bookings, customers, promotions, and agency data across four brands.
AuthGOODX-Application-Key secret keys server-side, restricted publishable keys for browser use, all self-issued.
Docs & DXGOODDocs portal, weekly-reset sandbox, webhooks with an open-source receiver, and a maintained Python SDK; no OpenAPI spec.
StabilityGOOD
Supergood: G Adventures shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

G Adventures scores A on the API Report Card. G Adventures runs a public REST API at rest.gadventures.com with instant self-serve sandbox and production keys. Read and content integrations need no approval; booking writes require a Sherpa Agency contract via sales. The only official SDK is Python, and there is no OpenAPI spec.

Tried to integrate with G Adventures?
SOURCES
No public OpenAPI/Swagger specification, partners must hand-code request/response shapes from prose docs or rely on the Python SDK as the de-facto schema reference developers.gadventures.com β†—
Specific rate-limit quotas are not published, partners learn ceilings only by hitting HTTP 429 in production, with no documented backoff guidance or quota-increase process developers.gadventures.com β†—
No public status page, no published SLA, no incident history, partners cannot subscribe to maintenance windows or post-mortems and rely on email support for outage signal developers.gadventures.com β†—
Booking-write capability is gated behind a Sherpa Agency code and a sales-led commercial contract, read-only and content integrations are self-serve, but transactional flows require a manual onboarding step developers.gadventures.com β†—
Sandbox data refreshes weekly on Sundays and overwrites test modifications, making it impractical for long-running staged integration tests or for QA scenarios that need persistent fixtures developers.gadventures.com β†—
Only one official client library (Python via gapipy), Ruby, PHP, Node/TypeScript, Java, .NET, and Go integrators must roll their own or rely on community libraries with no vendor maintenance commitment developers.gadventures.com β†—
PUT is silently treated as PATCH (partial update, not full replacement), a documented gotcha that surprises integrators expecting standard REST semantics and can cause silent data drift developers.gadventures.com β†—
Webhook documentation exists but the open-source receiver helper (django-gapi-hooked) is Django-specific and has seen limited updates (last meaningful activity Mar 2025), pushing non-Django integrators to build their own signature verification, retry handling, and idempotency from scratch github.com β†—
Webhook event-type catalog, retry policy, signing/verification scheme, and replay tooling are not exhaustively documented on the public docs site, partners learn operational specifics during onboarding developers.gadventures.com β†—
No published per-call pricing or revenue-share schedule for transactional bookings, commercials are negotiated bilaterally via sales, making it hard for prospective partners to model unit economics before commitment developers.gadventures.com β†—
Refund and cancellation disputes, customers report being denied cash refunds and offered future-trip credits instead, particularly for cancellations inside the 60-day window or for trips cancelled by G Adventures during disruption events bbb.org β†—
Pandemic-era refund backlog with reports of 9-month processing timelines and disputed cancellation fees g-adventures.pissedconsumer.com β†—
Escalation friction, phone agents have no authority to issue refunds and customers report difficulty reaching supervisors or decision-makers g-adventures.pissedconsumer.com β†—
Trustpilot reviews surface mixed experiences across 14,000+ reviews: tour quality praised but refund/cancellation policy and post-booking customer service flagged repeatedly trustpilot.com β†—
BBB complaints (low volume, ~2 over 3 years) center on denied refunds tied to airline disruptions (CrowdStrike outage) and charges applied despite pre-confirmation cancellation requests; G Adventures is not BBB accredited and one complaint went unanswered bbb.org β†—
TripAdvisor and travel-forum threads recount accommodation quality variance, with budget-tier trips delivering lower lodging standards than marketing suggests tripadvisor.com β†—
Brand consolidation friction, the GTC restructure (2023) and centralized administrative consolidation across G Adventures, TruTravels, G Touring drew internal and trade-press attention to leadership churn and operational integration risk skift.com β†—