Skip to content
SMSGELY — Naimur SMS BD

Integrations

Connect SMS to the tools you already use

Send SMS automatically from your website, online store, app or business software. SMSGELY integrates through a REST API and signed webhooks, so almost any system can send messages and receive delivery updates.

Options

Integration options

What is available today, and how each option works.
  • Via REST API · official plugin planned

    WordPress

    Send SMS when a form is submitted, a user registers or anything else happens on your site. Today this uses a small PHP snippet in a site-specific plugin that calls the SMSGELY API.

  • Via REST API · official plugin planned

    WooCommerce

    Notify customers when their order is received, processing, completed or cancelled by hooking into WooCommerce order status changes — with one SMS per order status, never duplicates.

  • Available via REST API

    Custom websites and apps

    Laravel, Django, Node.js, .NET, Go or plain PHP — any backend that can make an HTTPS request can send SMS, check status and manage contacts with JSON.

  • Available via REST API

    CRM, ERP and POS systems

    Trigger payment reminders, invoices, loyalty messages or stock alerts from the business software you already use, and sync customers with the contacts API.

  • Available

    Webhooks

    Receive signed message.status and campaign.completed events at your HTTPS endpoint, so your system knows when messages are delivered or fail.

  • Available in the dashboard

    Spreadsheets and CSV

    No API in your software? Export customers as CSV from Excel, Google Sheets or your POS and import them as contacts or campaign recipients.

How it works

How an integration sends a message

  1. Something happens

    An order changes status, a form is submitted, a payment arrives or a job finishes in your system.
  2. Your server calls the API

    It sends POST /sms (or /sms/bulk) with your API key and an Idempotency-Key, so a retry never sends twice.
  3. SMSGELY sends it

    The message is stored, queued and submitted to the SMS provider. You receive a message ID immediately.
  4. Status flows back

    Your webhook receives signed status updates, or your system checks GET /sms/{id} when it needs to.

Choose

Which approach fits your business?

Recommended integration approach by situation
If you have…Recommended approachStart here
A WooCommerce storeOrder status hook with a PHP snippet, one SMS per order statusWooCommerce guide
A WordPress site with forms or membershipsSite-specific plugin that calls the API with wp_remote_postWordPress guide
Your own website or mobile app backendCall the REST API from your server; use webhooks for delivery updatesDeveloper quick start
A CRM, ERP or POS with scripting or HTTP actionsTrigger POST /sms from the system’s automation, or sync contacts with the contacts APIAPI reference
Software without any API featuresExport a CSV and send a campaign from the dashboardBulk SMS

Security

Integrate safely

An API key can spend your wallet balance, so treat it like a password. API keys are stored hashed on our side and shown to you only once, when you create them. If a key is ever exposed — committed to a public repository, pasted into a support chat, left in a theme file — revoke it in the dashboard and create a new one.

The authentication guide covers scopes and IP allowlists in detail, and our SMS API security checklist is a good review before you go live.

  • Create one API key per integration, so you can revoke one without breaking the others.
  • Give each key only the scopes it needs — a store that only sends SMS needs just sms:send.
  • Store keys in server-side configuration (environment variables, wp-config.php), never in browser JavaScript, mobile apps or theme files.
  • Restrict keys to your server’s IP addresses with the optional IP allowlist.
  • Verify the SMSGELY-Signature header on every webhook before trusting it.

FAQ

Integration questions

Is there an official SMSGELY WordPress or WooCommerce plugin?

Not yet. An official plugin is planned. Today, WordPress and WooCommerce sites integrate through the REST API using a small PHP snippet added as a site-specific plugin. Our developer documentation includes ready-to-adapt code.

Can SMSGELY connect to my CRM or POS?

If your system can make HTTPS requests — directly, through a script or through an automation tool that supports custom HTTP requests — it can send SMS through the SMSGELY API. If it cannot, you can export customers as CSV and import them into SMSGELY.

Which programming languages are supported?

Any language that can send an HTTPS request with a JSON body. Our documentation includes examples in cURL, JavaScript (Node.js), PHP and Python.

How do I keep my API key safe in an integration?

Create a separate key for each integration with only the scopes it needs, store it in server-side configuration such as environment variables or wp-config.php, never in browser code or theme files, and optionally restrict it to your server’s IP addresses.

Connect your first integration

Create an account, generate a scoped API key and follow the guide for your platform.