Orbit API

Name: Orbit API API
Brand: Orbit API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer Successbearer33 EndpointsREST

For Agents

Manage Orbit workspace members, activities, organizations, notes, and webhooks via Bearer-authenticated REST calls.

Connect the Orbit API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Orbit API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Orbit API API.

Create and update Orbit members across multiple identity sources

Resolve a member from a GitHub, Discord, or email identity

Record activities of any defined type against a member

Manage activity types used to label community events

GET STARTED

Start building with Orbit API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Orbit API, keeping it validated and agent-ready.

The Orbit API exposes workspaces, members, activities, organizations, notes, reports, and webhooks for community-led teams operating across GitHub, Discord, Slack, and other channels. Integrations use it to push activities from external sources, look up members by source identity, and pull engagement data into BI or CRM systems. Authentication is Bearer-only and every collection endpoint is scoped to a workspace_slug, which keeps multi-workspace accounts cleanly isolated.

Use Cases

Patterns agents use Orbit API API for, with concrete tasks.

★ Source-of-Truth Member Sync

Treat Orbit as the source of truth for community members and replicate the member graph into a CRM or warehouse. The /workspaces/{workspace_slug}/members endpoints expose paginated reads and the /members/find endpoint resolves cross-source identities, so a sync job can keep the downstream system aligned with Orbit.

Page through GET /{workspace_slug}/members and upsert each record into the warehouse keyed by Orbit member id

Activity Webhooks for Real-Time Reactions

Subscribe to Orbit's webhook events to trigger real-time reactions when members hit milestones — first contribution, returning after dormancy, posting in a key channel. The webhooks endpoints register subscriptions that forward events to any HTTPS URL, keeping the reaction logic outside Orbit itself.

POST /{workspace_slug}/webhooks with a target URL, then handle incoming activity-created events to trigger Slack alerts

Organization-Level Account Mapping

Link Orbit organizations to CRM accounts so sales reps can see which active community members belong to which target accounts. The organizations endpoints return company records and member affiliations that can be joined to a CRM company id for account-based reporting.

GET /{workspace_slug}/organizations and join the resulting list with CRM accounts on company domain

Custom Activity Types for Internal Channels

Define activity types for tools Orbit does not natively support — internal Slack workflows, training platforms, customer events — so the love score reflects the full member journey. The activity_types endpoints manage these definitions and the activities endpoints record the events themselves.

POST a new activity_type for 'training-completed', then POST an activity of that type when a member finishes a course

Agent-Driven Community Workflow via Jentic

An AI assistant for community managers can resolve a person's Orbit profile, record an activity, and post a note in one workflow. Jentic resolves natural-language intents like 'log a Discord reply for this member' to the right workspace-scoped endpoint without exposing the Bearer token to the model.

Search Jentic for 'find an Orbit member by email and add a note', load the matching operations, and execute in sequence

Key Endpoints

33 endpoints — the orbit api exposes workspaces, members, activities, organizations, notes, reports, and webhooks for community-led teams operating across github, discord, slack, and other channels.

METHOD

PATH

DESCRIPTION

GET

/{workspace_slug}/members

List members in a workspace

GET

/{workspace_slug}/members/find

Find a member by source identity

GET

/{workspace_slug}/activities

List activities in a workspace

GET

/{workspace_slug}/activity_types

List activity types

GET

/workspaces

List accessible workspaces

GET

/workspaces/{workspace_slug}

Retrieve a workspace

GET

/{workspace_slug}/members

List members in a workspace

GET

/{workspace_slug}/members/find

Find a member by source identity

GET

/{workspace_slug}/activities

List activities in a workspace

GET

/{workspace_slug}/activity_types

List activity types

GET

/workspaces

List accessible workspaces

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Orbit Bearer token is stored encrypted in the Jentic vault per workspace, with the workspace_slug pinned to the credential. Agents receive a scoped session and never see the raw token.

Intent-based discovery

Agents search by intent like 'find an Orbit member' or 'record a Discord activity', and Jentic returns the matching workspace-scoped endpoint with its parameter schema.

Time to first call

Direct integration: half a day for Bearer auth, workspace_slug threading, and activity pagination. Through Jentic: under 30 minutes from signup to first member or activity call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Discourse API

Forum platform Orbit commonly ingests activity from for community engagement scoring

Use Discourse for direct read and write of forum posts; use Orbit to roll those posts up into a member-level engagement view.

Alternative

Circle.so API

All-in-one community platform with hosted spaces, events, and member profiles

Pick Circle.so when the community lives in a single hosted platform; pick Orbit when engagement is spread across GitHub, Discord, Slack, and forums.

Alternative

inSided Community API

Customer-success community platform with native engagement and Q&A modules

Choose inSided for B2B customer community on a hosted platform; choose Orbit when you need to combine many community sources into one graph.

FAQs

Specific to using Orbit API API through Jentic.

What authentication does the Orbit API use?

HTTP Bearer authentication. Tokens are generated inside Orbit and scoped to a workspace, so calls must use the workspace_slug the token was created under. Through Jentic the Bearer token is stored encrypted in the vault and the agent receives a scoped session, never the raw token.

How do I subscribe to Orbit events as webhooks?

POST a webhook definition to /{workspace_slug}/webhooks with a target URL and the events you want forwarded. Orbit then delivers JSON payloads to the URL whenever those events fire — for example new member created or new activity recorded.

Can I create custom activity types for events Orbit does not natively track?

Yes. Use /{workspace_slug}/activity_types to define a new type — for example 'training-completed' or 'webinar-attended' — then post activities of that type via /{workspace_slug}/activities. The love score and member timeline include those custom activities.

Why is workspace_slug required on every collection endpoint?

Orbit accounts can hold many workspaces and the API enforces isolation at the URL level. Every list and search endpoint scopes its results to the workspace named in the path, which means cross-workspace queries require multiple calls.

How do I find an Orbit member by email through Jentic?

Install the SDK with pip install jentic, then search Jentic for 'find an Orbit member by email'. Jentic returns the GET /{workspace_slug}/members/find operation with its schema; load it, supply the email and source, and execute. Sign up at https://app.jentic.com/sign-up.