Introduction

Connecfy is an API and infrastructure layer that sends and receives SMS through real SIM cards connected to your account as gateways. There is no telecom-grade SMPP connection or carrier aggregator underneath — the SIM is the sending mechanism, and Connecfy is the queue, routing, and API in front of it.

Architecture

A message you send through the API takes this path:

Your application
  │ HTTPS, POST /api/v1/sms/send/
  ▼
Connecfy API — validates the request, checks your plan's quota, writes the message to the queue
  │
  ▼
Connecfy infrastructure — holds the message until the right gateway polls for work
  │ polled roughly every 20 seconds
  ▼
Gateway — Connecfy's connection to the SIM
  ▼
SIM → Mobile network → Recipient

Nothing in that chain is push-based. The gateway polls for outbound work and reports results back the same way — there's no persistent socket or carrier webhook. That's a deliberate tradeoff of the SIM-gateway model: it works with any prepaid or postpaid SIM, in any country, at the cost of a queue-and-poll latency of up to about 20 seconds instead of true real-time dispatch.

Receiving works in reverse: a text arrives on the SIM, the gateway picks it up and reports it to Connecfy on its next check-in. It shows up wherever your account reads messages — the dashboard, or your own integration via the API.

The five things that matter

Account: Your Connecfy login. Owns SIMs, API keys, a billing plan with a monthly SMS/device allowance, and every message sent or received through anything it owns.
SIM (device): A physical SIM card connected to your account as a gateway. This is the thing that actually transmits — see SIM Cards. If your account has none connected, sends are auto-routed to Connecfy's own shared pool so you can start before setting one up.
Gateway: Connecfy's connection to a SIM — the thing that polls for work, drives the SIM, and reports status back. "SIM" and "gateway" are often used interchangeably in these docs; the SIM is the resource, the gateway is what makes it usable remotely.
API key: The credential your server uses to call the Connecfy API — a bearer token, generated from the dashboard, shown once. See API Keys.
Message / status: Every SMS — sent or received — is one record with a direction and a status. Outbound moves queued → sending → sent → delivered (or failed); inbound arrives directly as received. See Message Lifecycle.

Current API versionAll endpoints in this documentation are under /api/v1/. There is no v2 yet — where these docs say "the API," they mean v1.

Where to go next

5 minutes

Quickstart →

Connect a SIM, get an API key, send your first message.