About
Read the key owner’s profile, organization role, timezones, and permissions; update profile details; and inspect or disconnect integrations. Profile and mailbox reads use the key owner’s account; shared integrations use the key’s organization. Connecting integrations requires a human’s login in the app. All operations go through the developer API gateway — one endpoint, called byoperationId. If you haven’t set up a key yet, start with the
Developer API Overview.
Operations
Reading your account (READ scope)
organizationRole is ADMIN, MEMBER, ISA, or INDEPENDENT_OPERATOR;
membership status is ACTIVE or SUSPENDED. Use resolvedTimezone when
interpreting times for the key owner. A null personal or organization
timezone means none was chosen, not UTC; the resolved value applies the
availability-schedule and organization fallbacks.
For standard member/ISA seats, the three VIEW_ALL_* capabilities and
CONTRACTS_VIEW/CONTRACTS_MANAGE are opt-in. The contract capabilities govern
viewing and managing contracts wherever the contract surface enforces them;
their presence does not add contract operations to this API.
CAN_SKIPTRACE, CAN_EXPORT, and CAN_WORKFLOW are on unless revoked.
VIEW_TEAM_DIRECTORY controls whether teammate identities are visible.
Independent-operator seats lack it and have fixed role permissions that
cannot be granted individually.
Writing your account (WRITE scope)
Your accountThese operations act on the calling key’s own user and profile. There is no
caller-supplied entity id and no cross-user access — the subject is always the
key owner, derived from the key.
Integrations (ADMIN scope)
Facebook Lead Ads is connected only when a returned Page has
connected: true;
facebookAccountConnected alone means the account is signed in. A null Page
list means Facebook did not answer. Direct-mail connections report state
and authHealth; phone-enrichment providers report connectionStatus.