Skip to main content
Use this pageChatGPTClaudeCursor · OpenAPI · MCP

Connectivity

Connectivity is where buyers configure partner credentials, submit connections for activation, and follow validation progress until the connection is ready for live traffic.

This guide covers Hotels pull connections. Other verticals may activate without the validation gate until their design is migrated.

Connection states​

StatusMeaning
DraftSaved but not submitted. Environment and credentials can still change.
In progressSubmitted for activation. Validations are running or blocked on an action.
ActiveLive. Available for search, quote, and booking through Connect Hotels.
InactiveTemporarily disabled. Markups and rappels are suspended and restored on reactivate.

needs-action is a flag on In progress (and always implied for Draft). It means the buyer or Bundleport must act before activation can finish.

Environment (PRODUCTION / TEST / STAGING) is independent of status. Production credentials are never mixed with test traffic.

Activation flow (Hotels pull)​

  1. Create a connection (or save a draft) with partner, credentials, optional notify emails, and agencies.
  2. Accept the connectivity agreement and Submit for validation.
  3. The connection moves to In progress. Bundleport runs nine checks:
    • Booking flows (3): search + quote for 2 adults, 2 adults + 1 child, and 2 rooms × 2 adults. Book is never called.
    • Content (6): hotels, rooms, destinations, boards, categories, and metadata coverage for the partner catalog.
  4. When all checks pass, the connection becomes Active.
  5. If a check fails, the connection stays In progress with needs-action and a clear reason in the Activation tab.

Check connection in the wizard only validates credential format against the partner schema. Partner authentication is verified during the booking flows after submit.

Support tickets​

Activation failures open a conversation in the support inbox:

  • Technical failures (booking/content infrastructure, timeouts): Bundleport reviews the failure. The ticket is escalated to development automatically.
  • Credential failures (partner rejected the credentials): update credentials in Connectivity. Validations re-run on save; the conversation closes when they pass.

Ticket references look like BP-{id}. Private agent notes never appear in the Support tab.

Credentials updates​

On an Active connection you can:

  • Verify then apply (recommended): candidate credentials are validated with booking flows first. Live credentials stay unchanged until the run passes.
  • Apply now: replaces live credentials immediately.

On In progress or Draft, credential edits apply directly and restart validation when needed.

Deactivate and reactivate​

  • Deactivate (from Active): suspends markups/rappels and stops live traffic. Reversible.
  • Reactivate: restores Active when credentials match the last successful validation; otherwise returns to In progress and re-runs checks.
  • Delete: archives the connection. An in-flight validation run is cancelled.