Skip to main content

Orbit

Introduction​

The Orbit destination connector is under active development.

At this time, the connector supports credential validation (testing that your API token can access your Orbit workspace), but it does not yet support loading/syncing data into Orbit.

Setup​

  1. In Orbit, identify your workspace slug (the {workspace_slug} portion of your Orbit URL or API path).
  2. Create an API token in Orbit with access to your workspace.
  3. In your destination configuration, provide the workspace slug and API token.

Authentication​

Orbit uses Bearer token authentication.

During connection testing, the connector validates credentials by calling:

  • GET https://app.orbit.love/api/v1/{workspace_slug}/members?limit=1

If the request succeeds, the credentials are considered valid.

Configuration​

FieldTypeRequiredDescription
workspace_slugstring✅Your Orbit workspace slug. Used to build API requests like https://app.orbit.love/api/v1/{workspace_slug}/....
api_tokenstring✅Orbit API token used as a Bearer token for API requests.

Streams / Data model​

This destination connector does not currently expose any streams or a data model for loading data into Orbit.

Limitations​

  • Loading is not implemented yet. Sync runs will fail with a message indicating Orbit destination loading is still in development.

Hashing and normalization​

This connector does not currently expose field-level hashing options.

Data contract​

A destination data contract is not yet available because the connector does not currently support loading data into Orbit.