Skip to main content

Frequently Asked Questions

Billing & Pricing

How am I charged for SMS?

D0.25 per SMS sent, billed daily. There are no monthly fees, no setup fees, and no minimum spend. You pay only for what you send. View your usage and daily totals in the dashboard under Billing → Usage.

Are there monthly fees?

No. Integify is pay-as-you-go only. You are charged D0.25 per outbound SMS, nothing else.

Can I cancel anytime?

Yes. There are no contracts or long-term commitments. You can stop using the service at any time — you'll only be charged for messages already sent.

Do you offer volume discounts?

Not currently. Custom pricing is available for Enterprise tier customers with high volumes. Contact sms@integify.io to discuss.

Where can I see my invoice history?

In your dashboard, go to Billing → Invoices. Monthly invoices are generated on the 1st of each month for the previous month's usage.

Technical

What is the SMS delivery latency?

Typically under 5 seconds from API call to recipient receiving the message. Actual delivery time depends on the operator network — Africell and QCell are generally fastest. You can verify delivery time by checking the delivered_at timestamp in webhook events.

Can I schedule SMS for a future time?

Not in the current version. All messages are sent immediately. Scheduled sending is on the roadmap — submit a feature request at sms@integify.io.

What are the API rate limits?

10 requests per second per API key, with bursts up to 20 requests per second. If you exceed this, the API returns HTTP 429 Too Many Requests. Add exponential backoff to your retry logic.

Do you support Unicode characters and emoji?

Yes. Unicode messages are supported. Standard SMS (Latin characters) fits 160 characters per SMS segment. Unicode messages fit 70 characters per segment — anything longer is sent as a multi-part SMS and charged per segment.

Can I send to international numbers?

Not currently. Integify routes SMS through Gambian SIM cards, so only Gambian numbers (+220) are supported in the MVP. International support is planned for a future release.

What is your uptime SLA?

Best-effort availability for the current tier. A 99.5% SLA is available for Enterprise customers. Check the status page for historical uptime data.

Do you support two-way SMS?

Yes. Inbound SMS is surfaced to your webhook URL as sms.received events. See the Webhooks guide for setup instructions.

Troubleshooting

My SMS is not delivering. What should I check?

  1. Confirm the phone number is in E.164 format (+220XXXXXXX)
  2. Check the Messages log for error codes or a stuck queued status
  3. Verify your API key and rate limits (429) are not blocking sends
  4. If webhooks are enabled, inspect Webhook Logs for sms.failed payloads

My webhook is not firing. What do I check?

  1. Verify the webhook URL is registered in Settings → Webhooks
  2. Make sure your endpoint is publicly reachable (not localhost)
  3. Check the Webhook Logs in your dashboard for delivery attempts and error responses
  4. Verify your server responds with HTTP 200 within 10 seconds

My API key is returning 401 Unauthorized.

The most common cause is a malformed Authorization header. The correct format is:

Authorization: Bearer sk_your_key_here

Note the space after Bearer. Do not include quotes around the key. If the format is correct, the key may have been rotated — generate a new key in Settings → API Keys.

I'm getting 429 Too Many Requests.

You've exceeded the rate limit of 10 req/s. Implement exponential backoff: wait 1 second, retry; if it fails again, wait 2 seconds, then 4, then 8. Most use cases don't hit this limit in normal operation.

Features

Do you support MMS?

No. SMS only in the current version. MMS support is not planned for the near term.

Can I customise the sender ID?

Not currently. The visible sender is determined by Integify's outbound routing. Alphanumeric sender IDs are not supported in the MVP.

What about GDPR and data privacy?

Your application calls Integify over HTTPS; message content is processed for delivery per your agreement and deployment model. You are responsible for compliance (e.g. consent, retention, and lawful basis) in your jurisdiction.

Can I use Integify for OTP / verification codes?

Yes. OTP messages work the same as any other transactional SMS. Keep messages under 160 characters to avoid multi-part billing. Use a short expiry (60–120 seconds) and implement rate limiting on your end to prevent abuse.

What operators are supported?

Africell, QCell, Comium, and Gamcel. Actual reachability depends on Integify's live routing for your account — ask sms@integify.io if you need a coverage matrix.

Still have questions?

Email sms@integify.io — we typically respond within one business day.