Capability · Integrate

Plug into your stack. Keep what works. Move what matters.

Fairshift is the customer-facing layer. The rest of your stack keeps running. Connectors, REST API, webhooks, custom workspace apps for the deployments that need to go further.

Talk to engineeringSee deployment surfaces →
Connector library
24+ live · routing in real time
WA
EM
SM
TG
IG
SL
MS
LN
VC
CR
PY
$$
AD
GA
WD
VD
FS
AP
CL
DB
AN
BL
BK
RV
· Messaging· Voice· Payments· Ad platforms· Web data· Video· Forms / Calendar / API
Connectors

What Fairshift connects to today.

Six categories, all live. Messaging, voice, payments, ad platforms, web data, real-time video. Plus webhooks and a public REST API for everything else.

Messaging
  • WhatsApp Business
  • SMS
  • Email (IMAP + outbound)
  • Telegram
  • Instagram DMs
  • Slack
  • Messenger
  • LINE
Voice
  • Inbound numbers (provisioned or bring-your-own)
  • Outbound calling
  • Bridge to existing telephony
Payments and billing
  • Stripe (USD + multi-currency)
  • Razorpay (INR)
Ad platforms
  • Meta conversion events
  • Google Ads conversion import
Web data
  • Account and contact enrichment
  • Public-source company data
  • Bulk contact import
Real-time video
  • Live video sessions with AI avatar
  • Screen-share demos
  • Lead capture from video
REST API

A clean JSON REST API. No surprises.

Use a bearer token to sign in. Resource paths stay clear and steady. An Idempotency-Key keeps a repeated update from running twice. The example lists leads, then updates one.

curl · list leads
bash
1curl https://api.fairshift.co/v1/leads \
2  -H "Authorization: Bearer fs_live_..." \
3  -H "Accept: application/json" \
4  -G \
5  --data-urlencode "stage=qualified" \
6  --data-urlencode "limit=50"
curl · update lead stage
bash
1curl https://api.fairshift.co/v1/leads/lead_L4128 \
2  -X PATCH \
3  -H "Authorization: Bearer fs_live_..." \
4  -H "Content-Type: application/json" \
5  -H "Idempotency-Key: lead.update.lead_L4128.20260425" \
6  -d '{"stage": "negotiation"}'
Webhooks

Signed deliveries. Idempotent retries. Twenty-four hours.

Set webhook events for each account. Fairshift signs each event with HMAC-SHA256. If delivery fails, it tries again for 24 hours. Each event has a key that helps block a repeat.

webhook · lead.qualified
json
1{
2  "event": "lead.qualified",
3  "id": "evt_2K9aC",
4  "occurred_at": "2026-04-25T10:14:31Z",
5  "tenant": "acme",
6  "data": {
7    "lead": {
8      "id": "lead_L4128",
9      "email": "rohan@acme.co",
10      "score": 87,
11      "source": "web_chat",
12      "owner": "user_8K2nQ",
13      "tags": ["pricing-engaged", "enterprise"]
14    },
15    "qualified_via": "auto_score_threshold"
16  },
17  "previous_stage": "new",
18  "current_stage": "qualified",
19  "idempotency_key": "lead.qualified:lead_L4128:1745575671402"
20}

Verify the X-Fairshift-Signature header against your webhook secret using HMAC-SHA256.

Save each event key after you process it. If the same key arrives again, reject it. This stops a retry from running the same task twice.

Subscribe to as many or as few events as you want. Common subscriptions: conversation.started, lead.qualified, deal.closed, conversation.escalated.

Authentication

Scoped keys. Signed webhooks. Audited rotation.

Servers use API keys with limited rights. Browser and online tool links use OAuth when it fits. No key gets access to everything by default.

API keys (server)
Bearer-token in Authorization header. Scoped to a role and an endpoint allowlist. Rotate from the dashboard.
OAuth (third-party SaaS)
Where supported by the destination (calendar, CRM). We are the OAuth client; consent and revocation are user-side.
Webhook signatures
Every webhook delivery signed with HMAC-SHA256 using your tenant secret. Verify on receipt before processing.
Per-environment keys
Live keys (fs_live_) and test keys (fs_test_) are separate by design. Test keys hit a sandboxed tenant.
Key rotation
One-click rotation in the dashboard. Audited. Old keys remain valid for a configurable grace window (default 24h).
Rate limits
Per-tenant baseline with burst handling. Standard plan: 10 req/s sustained. Enterprise: scoped per engagement. 429 responses include Retry-After.
Roadmap

Honest about what ships next.

Below is what is confirmed for the next two quarters. We do not ship vapor. If a connector is listed as live on this page, it is actually live. Anything in planned is a real engagement, not a checkbox.

Live today

  • WhatsApp Business · SMS · Email (IMAP + outbound)
  • Telegram · Instagram DMs · Slack · Messenger · LINE
  • Voice (provisioned numbers + bring-your-own)
  • Stripe · Razorpay
  • Meta CAPI · Google Ads conversion import
  • Web data enrichment · bulk import
  • REST API · Webhooks · Real-time video

Planned, next 2 quarters

  • HubSpot CRM (bidirectional sync)
  • Salesforce (read-write, field mapping)
  • Calendly + Google Calendar (native scheduling)
  • Pipedrive (read-write)
  • Zapier + Make (low-code automation)
  • Microsoft Teams (channel + chat)
  • Native ServiceNow connector
Back to the whole shape

Capabilities, layers, industries. One platform.

Tell us your stack. We’ll tell you how it slots in.

In 30 minutes, we map your sales tool, phones, ads, and data store. You leave with a simple map of how the tools can connect.

Talk to engineeringBack to Platform