Get your product credentials.
Use the product sp_id and the configured signature or password hash. Treat both passwords and reusable hashes as secrets.
Connect your CRM, website or business application through the HTTP SMS API. Send requests from your server using the credentials assigned to your product.
Use the product sp_id and the configured signature or password hash. Treat both passwords and reusable hashes as secrets.
The Single SMS Send endpoint accepts recipient number and message content with your account credentials. Consult the documentation for exact parameters.
The endpoint returns JSON. Handle errors explicitly; an accepted API response should not be treated as proof of handset delivery.
Use the endpoint supplied for your account. Keep credentials out of browser JavaScript, logs and public repositories. Confirm transport protection with support before deploying production credentials.
Yes, if your backend can make the required HTTP requests. Your developer must implement recipient validation, event triggers and response handling.
No native plugin is included in this package. Integration requires development or a separately confirmed compatible connector.
Include SMPP requirements in your request. Availability, access and connection parameters must be confirmed for your account.
Share your destination, use case and monthly volume. We’ll discuss the next steps.