Integrating Connecfy

Two design decisions come up in almost every real integration: don't block a request on delivery, and decide up front how you'll correlate a Connecfy message with your own record of why it was sent.

Don't wait for delivery in the request path

Because a send can take up to ~20 seconds to even reach a phone, never make a user-facing request (a signup, a checkout) block on status reaching delivered. Call /api/v1/sms/send/, treat the 202 as success for your own flow, and track final delivery status separately — a background job, a queue consumer, whatever your stack already uses for async work.

Correlating messages with your own records

Store the returned message_id against whatever triggered the send — an order, a user, a verification attempt. It's the only handle you'll have for checking status later, and Connecfy has no concept of your own object ids to join against.

If your own system might send the same logical message twice (a retried job, a double-clicked button), generate your own request_id up front — a UUID, or your own primary key — and pass it every time. See Building Reliable Integrations.

There are no webhooks

Neither outbound status changes nor inbound messages push anything to your server. If you need to know when a message reaches delivered or failed, that's a polling job you run — see Building Reliable Integrations for a sane interval. If your integration fundamentally needs push notification of inbound texts, read the limitation in Receiving SMS API before committing to an architecture around it.

Separate keys per environment

Generate a distinct API key for staging versus production rather than sharing one — see API Keys. It makes usage in each environment separately visible on the dashboard and means revoking a compromised staging key never touches production traffic.

Testing without spending your quota

There's no separate sandbox mode — a call to /api/v1/sms/send/ queues a real message and counts against your plan the same as production traffic. Send to numbers you control while testing, and be mindful of the monthly SMS cap on lower plans while iterating.