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. Run it through Jentic One, the self-hosted execution layer.

Can I limit what my agent is allowed to do with the Orbit API?

Yes. Because Jentic One is self-hosted, your own rules decide which Orbit operations the agent may call, so you can allow it to list members and activities but block webhook or note writes. Since Orbit puts the workspace_slug in the URL path, such as /{workspace_slug}/members and /{workspace_slug}/activities, you can pin the agent to a single workspace and keep every other workspace out of reach. The bearer token is injected by your instance at execution time and never enters the agent's prompt or context, so it only ever acts within the operations and workspace you permit.