SendLit DocsProvisioning teams
Create organization-scoped SendLit teams for external tenants.
Provisioning is for trusted multi-tenant platform integrations. First create
an organization, configure its shared delivery policy, then create an
organization API key with teams:provision. Call the provisioning endpoint
with that key as a Bearer token and a stable externalId for the source
tenant.
POST /provisioning/teams
Authorization: Bearer sl_org_live_…The first successful creation returns the team and its plaintext API key.
Persist that key immediately: subsequent calls for the same externalId return
the existing team without returning the secret again. If the key is lost,
create a replacement through the provisioning team-key route.
The key’s organization determines where the team is created. Do not send an owner email, organization ID, or global provisioning secret as an authority signal. Provisioned teams do not create human team members by default.
For shared delivery, choose an active default organization mailbox and enable automatic grants before provisioning. See Organizations for the complete setup and delivery model.
Transactional email
Send a single email through the REST API.
List contacts GET
Returns a paginated list of contacts. Pass filter as serialized ContactFilterWithAggregator JSON for inline filtering, or segmentId to only return contacts currently matching that saved segment's filter (404 if the segment doesn't exist). SendLit supports fixed generic contact filters over first-class fields, tags, and custom fields; client-specific concepts should be synced into namespaced tags or customFields. q, filter, and segmentId combine with AND. The response's total reflects the combined filters.