Notrel Messaging

Notrel Messaging provides two HTTP interfaces for submitting SMS messages, checking customer balances, and retrieving destination rates.

• HTTP API v1 (Legacy) is GET-only and uses query parameters.
• REST API v2 uses JSON and HTTP Basic Authentication.

Both APIs and SMPP use the same account balance and Service. Deposited credit does not expire, and there is no monthly commitment or mandatory monthly SMS volume. The selected Service’s minimum deposit applies to every top-up.

Explore Services and pricing for live public prices, operational limits, and the unauthenticated pricing API. Message submission and customer balance endpoints still require account credentials.

Base URL

https://sms.notrel.net

Always use HTTPS. A successful submission response confirms that the message was durably accepted into the Notrel Messaging pipeline. It does not confirm delivery to the destination handset.

Credentials

Use the credentials shown on the SMPP account page in the customer portal:

• Username: the SMPP account system_id
• Password: the SMPP account password

The same credentials are used by HTTP API v1, REST API v2, and SMPP.

Passwords are displayed only when an account is created or its password is rotated.

Content and segmentation

Text encoding is selected automatically when coding is omitted:

• GSM-7 is used when every character is representable in the GSM alphabet.
• UCS-2 is used for characters that require Unicode encoding.
• Long messages are segmented automatically.
• Billing is applied per resulting SMS segment.

Use hex-content in v1 or hex_content in v2 for binary content. Hexadecimal content must contain complete byte pairs.

Sender IDs

When from is omitted, the SMPP account's default sender ID is used. A sender ID must be approved and assigned to the account before it can be used. The availability and presentation of sender IDs can vary by destination network.

Request correlation

Successful single-message submissions include an X-Request-ID response header. This correlation identifier can be supplied when contacting support, together with the submission UUID. Do not include account passwords in support messages.

Security recommendations

• Always use HTTPS.
• Use REST API v2 for new integrations so credentials are carried through HTTP Basic Authentication instead of query parameters.
• Do not write SMPP passwords into application logs.
• Store credentials using a secrets manager or equivalent protected storage.
• Rotate the SMPP password immediately if it is exposed.
• Validate and authenticate DLR callbacks at the receiving application where appropriate.