Skip to content

Handle

A Handle is an account or name a Startup or Brand holds on an outside platform, bound to an Integration credential.

Properties

PropertyTypeRequiredDescription
venuestringrequiredThe venue it lives on, by id.
namestringrequiredThe name as the platform shows it, such as @example.
sharedbooleanTrue for a Studio account shared across sibling Startups; every Post names the Startup it speaks for.
agentbooleanTrue when an Agent runs it; its bio says so.
integrationIntegrationThe Integration credential it publishes through.

Object

JSON
{
  "$id": "https://api.sb/tutorloop.com/handles/handle_1",
  "$type": "Handle",
  "venue": "Example venue",
  "name": "TutorLoop",
  "shared": true,
  "agent": true,
  "integration": "integration_1"
}

Relationships

  • A Handle publishes many Posts: every Post goes out from one Handle, so its reach and replies count toward that Handle. publishes, inverse handle.

Verbs

  1. createCreates a Handle.
    POST /{namespace}/handlesdoHandle.created
  2. getReturns one Handle by id.
    GET /{namespace}/handles/{id}readNo Event
  3. listReturns Handles, newest first, one page at a time.
    GET /{namespace}/handlesreadNo Event
  4. updateChanges the given properties of a Handle.
    PATCH /{namespace}/handles/{id}doHandle.updated
  5. connectConnect binds a Handle to the Integration credential it publishes through, once the platform confirms the account.
    POST /{namespace}/handles/{handle}/connectdoHandle.connected

Permissions

Which Access level may call each Verb. One-way Verbs wait their delay window.

Operationowneradminmemberviewer
Handle.createYesYesYesNo
Handle.getYesYesYesYes
Handle.listYesYesYesYes
Handle.updateYesYesYesNo
Handle.connectYesYesYesNo

Call it

Text
Connect the latest handle with an integration.

Example

A recipe app holds the Handle @weeknightplates on two social venues, both bound to one Integration. An Agent runs them, and each bio says so.