{"id":593,"date":"2026-07-09T02:10:59","date_gmt":"2026-07-09T02:10:59","guid":{"rendered":"https:\/\/smppcenter.com\/journal\/?p=593"},"modified":"2026-07-09T02:11:01","modified_gmt":"2026-07-09T02:11:01","slug":"api-signatures","status":"publish","type":"post","link":"https:\/\/smppcenter.com\/journal\/api-signatures\/","title":{"rendered":"API Signatures: Let Your Customers Keep Their API While You Host the SMS Platform"},"content":{"rendered":"\n

Every SMS gateway<\/a> owner knows the hardest part of winning a new enterprise customer is not pricing. It is integration.<\/p>\n\n\n\n

Your prospect already has PHP scripts, ERP connectors, CRM workflows, or middleware talking to another vendor\u2019s HTTP API. Those systems use fixed parameter names like to<\/code>, text<\/code>, username<\/code>, or send_to<\/code>. In many cases, the customer cannot change the request body<\/strong> at all. They can only point traffic to a new base URL.<\/p>\n\n\n\n

That is exactly why we built API Signatures<\/strong> in SMPP Center.<\/p>\n\n\n\n

As a license holder<\/strong>, you configure this from your own platform admin panel<\/strong> (not from smppcenter.com). Your customers keep sending the same parameters they always have. Your platform translates those requests into the standard SMPPCenter send format behind the scenes.<\/p>\n\n\n\n

\"API<\/figure>\n\n\n\n
\n\n\n\n

What is an API Signature?<\/h2>\n\n\n\n

An API Signature is a configurable translation layer between your customer\u2019s HTTP API request and your SMPPCenter SMS engine.<\/p>\n\n\n\n

You define:<\/p>\n\n\n\n

    \n
  • A display name<\/strong> (for your operations team)<\/li>\n\n\n\n
  • A URL key<\/strong> (the path segment in the endpoint)<\/li>\n\n\n\n
  • A customer account<\/strong> (one user, or all users on your platform)<\/li>\n\n\n\n
  • A parameter map<\/strong> (customer field names \u2192 system fields like login, password, mobile, message, sender ID, DLT fields)<\/li>\n<\/ul>\n\n\n\n

    After setup, the customer calls a dedicated endpoint on your licensed domain<\/strong>, for example:<\/p>\n\n\n\n

    https://your-domain.com\/SMSApi\/signature\/flash49<\/code><\/pre>\n\n\n\n
    They send username<\/code>, password<\/code>, to<\/code>, text<\/code>, and from<\/code>. Your platform receives it, maps it internally, and processes the SMS like any normal send request.<\/p>\n\n\n\n
    Supported methods: GET<\/strong> and POST<\/strong> (query string or application\/x-www-form-urlencoded<\/code> form body).<\/p>\n\n\n\n
    \n\n\n\n
    Where license holders manage this<\/h2>\n\n\n\n
    If you run a licensed SMPPCenter installation, open your admin panel<\/strong> and go to:<\/p>\n\n\n\n
    Settings \u2192 API Signatures<\/strong><\/p>\n\n\n\n
    From there you can:<\/p>\n\n\n\n
    Action<\/th>What it does<\/th><\/tr><\/thead>
    List \/ Read<\/strong><\/td>View all signatures, URL keys, customer scope, status, and full endpoint URLs<\/td><\/tr>
    Create<\/strong><\/td>Add a new signature using the two-step wizard<\/td><\/tr>
    Update<\/strong><\/td>Edit mappings without asking the customer to change their integration (if the URL key stays the same)<\/td><\/tr>
    Delete<\/strong><\/td>Remove a signature permanently<\/td><\/tr>
    Enable \/ Disable<\/strong><\/td>Pause traffic without losing configuration<\/td><\/tr>
    Refresh cache<\/strong><\/td>Push changes live to the SMS API server immediately<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Access is controlled through admin roles under the Settings<\/strong> category, feature API Signatures<\/strong> (Create, Read, Update, Delete). Assign permissions only to trusted operations or technical admins on your team.<\/p>\n\n\n\n
    Full in-panel documentation is also available under Admin \u2192 Documentation \u2192 Settings \u2192 API Signatures<\/strong> on your licensed installation.<\/p>\n\n\n\n
    \n\n\n\n
    Why this feature matters for your business<\/h2>\n\n\n\n
    1. Faster customer onboarding<\/h3>\n\n\n\n
    When a prospect says \u201cWe can only change the hostname, not our code\u201d<\/em>, you no longer lose the deal. You absorb their API shape on your side and go live in hours instead of weeks.<\/p>\n\n\n\n
    2. Lower integration cost for you and your customer<\/h3>\n\n\n\n
    No custom PHP patches per customer. No asking their developer to rewrite Postman collections, Java services, or billing system connectors. You configure mappings in the admin UI once and share one URL.<\/p>\n\n\n\n
    3. White-label and reseller advantage<\/h3>\n\n\n\n
    Resellers can offer an API that looks and behaves like the customer\u2019s previous provider<\/strong> while routing through your SMPPCenter cluster. That makes competitive takeaways smoother and reduces switching friction.<\/p>\n\n\n\n
    4. Multiple formats on one platform<\/h3>\n\n\n\n
    Customer A sends to<\/code> \/ text<\/code>. Customer B sends send_to<\/code> \/ msg_type<\/code>. Customer C still uses Flash49-style DLT field names. Each gets their own signature URL and mapping. One platform, many compatibility layers.<\/p>\n\n\n\n
    5. Safe rollout and maintenance<\/h3>\n\n\n\n