Developer overview
Taverity API
A REST API for triggering personal follow-up messages from your existing systems. Available with Taverity team plans. This page is a public overview. The full reference is included with team-plan onboarding, and organization API keys are created in the Taverity portal.
Example request
# Illustrative shape — exact path and fields confirmed during team-plan onboarding
curl -X POST https://api.taverity.com/v1/follow-ups \
-H "Authorization: Bearer YOUR_TEAM_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"user": "agent@your-brokerage.com",
"to": "+15551234567",
"message": "Hope you are doing well — let me know if you ever want a market update on the area.",
"require_approval": true
}'Illustrative shape — the exact endpoint path, field names, and response codes are confirmed during team-plan onboarding. require_approval: true sends a push notification for the team member to tap; false lets the message send when the user's shortcut next runs.
What the API does
Trigger personal follow-ups
Start a Taverity follow-up from your own systems. Specify the recipient, the message, and whether it requires user approval before sending.
Approval-gated or pre-authorized
Each request can require user approval — a push notification lands on the user's phone, they review and optionally edit before tapping send. Or pre-authorize routine messages to send when the user's shortcut next runs.
Route to the right team member
Team API keys can target any user under the organization, so messages send from the right team member's iPhone — not a shared number or a generic sender.
How it works
Bearer-token authentication
Each request includes a single Authorization: Bearer … header. Keys are 32 random characters, auto-generated by the system, stored as SHA-256 hashes at rest, and displayed once at creation.
REST + JSON
Standard HTTP verbs and JSON bodies. Works with any HTTP client and any platform that supports a custom request header. The full endpoint reference is issued during team-plan onboarding.
Organization-scoped keys
One key represents your team. Use it to trigger messages on behalf of any user under your organization. Keys are created, listed, and revoked by your company or super admin from the organization settings page.
Triggered, not blast
API messages always land on a user's iPhone for review or pre-authorized send via the Taverity shortcut. No bulk sending, no shared sender number — the message goes out from the right team member's number.
Works with what you already use
n8n
HTTP Request node with Header Auth.
Zapier
Webhooks by Zapier with a custom Authorization header.
Make / other low-code
HTTP module with Bearer auth.
Custom backends
Any HTTP client. REST + JSON, single header for auth.
Authentication is a single header, so any platform that lets you make an HTTP request with a custom header will work.
Other ways to trigger Taverity
The REST API is one trigger surface. Two others are available to any Taverity user — no team plan required — and both follow the same iPhone-side approval model.
Chrome extension for Google Sheets
Queue follow-ups directly from a Google Sheet. Each row becomes a pending message that lands on your iPhone for review, or sends when your shortcut next runs if you pre-authorized it. Useful when your list already lives in a sheet and you do not want to stand up an API integration.
MCP server for your favorite LLM
Connect Taverity to any LLM that speaks the Model Context Protocol. Your assistant can draft a follow-up and queue it for you — the message still lands on your iPhone, and nothing sends until you approve it.
Getting access
- 1. Start a team plan with Taverity — contact sales@taverity.com to set up your organization.
- 2. Receive the full API reference (endpoints, payloads, response codes, examples) as part of onboarding.
- 3. An organization admin creates the API key from the Taverity portal. The full key is shown once at creation — save it in a password manager or secret store.
- 4. Start triggering follow-ups from your CRM, transaction system, or wherever the right signal lives.
Frequently asked
Is the API on individual plans too?
Individual users can use Taverity's webhook and shortcut surface, the Chrome extension for Google Sheets, and the MCP server for LLMs to trigger personal follow-ups from their own tools. The organization-scoped API key — the one that can target any user under your team — is part of the team plan.
Can a key be lost or rotated?
Keys are revocable any time from the portal. They are stored as SHA-256 hashes and cannot be recovered if lost. To rotate, create a new key, update your integrations, then revoke the old one.
Does the API blast messages?
No. Every API message surfaces on a user's iPhone — either as a push notification requiring approval, or pre-authorized to send when the user's shortcut next runs. There is no shared Taverity number and no bulk send path.