Skip to main content
Use a completed audience run as the source for Orbit contacts. Choose paginated results for backend processing, direct CSV for a download, or a stored export when you need a reusable export record and a fresh signed URL.

​
Destination access

The hosted Orbit spec currently declares API-key access for integration, destination, and delivery operations, while their descriptions require a non-viewer organization member using Bearer authentication. Confirm the supported authentication with Leadpipe before implementing these operations. Do not assume the generated API-key control means a request will be accepted.
The reference describes webhook and EmailOctopus destinations, activation, synchronization, testing, secret rotation, and delivery history. These are separate from Identification webhooks configured in Webhooks. Do not transfer authentication, trigger, or retry assumptions between them. Until the access discrepancy is resolved, the documented API-key workflows for obtaining contacts are run results and exports. See Build and export an audience.