Skip to main content
If the carrier is not on All Carriers, open sidebar Carrier Requests and ask Zippendo to build it. You submit test credentials and docs URLs; the pipeline uses those to generate the integration. Catalog carriers you can connect yourself: Carrier credentials. Journey: Carriers.

​
List

URL: /{org}/dashboard/carrier-requests.
Carrier Integration Requests empty state with Request Integration in the headerCarrier Integration Requests empty state with Request Integration in the header

Carrier Integration Requests — empty list with Request Integration

Empty: title No carrier integration requests, description Request a new carrier integration and we’ll build it for you, button Request Integration. Columns: Carrier, Status, Auth Type, Submitted, Last Updated. Click a row to open the detail modal. This list has no search or filter popover.

​
Statuses

​
Request carrier integration

Header Request Integration opens modal request-carrier-modal. Success toast: Carrier integration request submitted. Failure: Failed to submit request or Failed to submit request. Please try again., plus any API code from errors.json.
Request carrier integration modal with API Key authentication fieldsRequest carrier integration modal with API Key authentication fields

Request form — Carrier Name, website, docs URLs, Authentication Type API Key

​
Shared fields

Authentication Type options: The credential block below the dashed rule changes with this select. Unused credential fields are not sent.

​
API Key

​
OAuth 2.0

Request carrier integration with Authentication Type OAuth 2.0 and Token URLRequest carrier integration with Authentication Type OAuth 2.0 and Token URL

OAuth 2.0 — Client ID, Client Secret, Token URL

​
Basic Auth

Empty either field: This field is required.

​
Custom

Label Custom Credentials *. Each row is Key / Value. Add field appends a row. Remove field is disabled when only one row remains. At least one non-empty key is required: Add at least one key/value pair. Empty keys are dropped on submit.

​
Test against live / production API

Request form scrolled to Test against live / production API switch and NotesRequest form scrolled to Test against live / production API switch and Notes

Test against live / production API — off by default, long helper under the label

This is not the Sandbox Mode checkbox on a connected carrier — Sandbox mode.

​
Request details

Click a row. Modal carrier-request-detail-modal. Loading: skeleton status pill and pipeline. Then:
  • Status badge (same labels as the list)
  • Carrier website (external link)
  • Notes (only if you submitted notes)
  • Pipeline — event graph when events exist. Stages include Request Submitted, Researching Carrier, Generating Booking, Generating Tracking, Generating Service Points, Generating Products, Running Tests, Pull Request Created, Released, Failed, and recovery Force Unlocked / Reconciled. Parallel groups can show Runs in parallel and {{built}} / {{total}} built. Node statuses: Pending, Building, Built, Failed, Skipped.
You cannot edit or resubmit from this modal.

​
API errors

Codes the form can surface: