# Why is my UAE sender ID being rejected?

> In the UAE, an unregistered or non-compliant sender ID is the top reason A2P SMS fails — the gateway returns HTTP06 (Invalid Sender ID) or the message is silently dropped. The TDRA requires every alphanumeric sender ID to be pre-registered with Etisalat/e& and du before use, promotional and transactional traffic are separated, and the sender ID must match its registration exactly, character for character.

- Canonical URL: https://www.broadnet.me/developers/troubleshooting-uae-sender-id
- Language: en
- Last updated: 2026-10-21
- Publisher: BroadNet (https://www.broadnet.me)

## Register with both operators via the TDRA

The UAE's Telecommunications and Digital Government Regulatory Authority (TDRA) governs A2P messaging, and sender IDs must be registered on both national networks — Etisalat/e& and du — before they will deliver. An unregistered sender ID returns HTTP06 (Invalid Sender ID) or is dropped after acceptance. BroadNet handles the TDRA registration; don't send with an unregistered string in sid. The parameter names (sid, mno, type) and HTTPxx error codes on this page are those of the legacy HTTP API (/websmpp); on the Bearer REST API (POST /sms/sendSms) the equivalents are senderId, destinationNumber and messageType (UNICODE for Arabic).

- TDRA governs UAE A2P; register on both e& and du.
- Unregistered sender ID → HTTP06 or a silent drop.
- Registration is per-operator across the country.
- Send only the approved sender ID in the sid parameter.

## Match the registered sender ID exactly

The sid you submit must match the registered sender ID exactly — same spelling, case, and spacing. 'BroadNet', 'broadnet', and 'Broad Net' are three different strings, and a mismatch is treated as unregistered and rejected with HTTP06. Copy the approved value verbatim into sid rather than retyping it.

- Exact match: spelling, case, and spacing all count.
- 'BroadNet' ≠ 'broadnet' ≠ 'Broad Net'.
- A mismatch reads as unregistered → HTTP06.
- Copy the approved sender ID verbatim into sid.

## Keep promotional and transactional separate

The UAE separates promotional and transactional messaging, and each generally uses its own registered sender ID and route. Sending promotional content on a transactional sender ID (or vice versa) can get the message filtered even when the sender ID itself is registered. Register the right sender ID for the traffic type and route each stream accordingly.

- Promotional and transactional use separate sender IDs/routes.
- Content that doesn't match the sender-ID type can be filtered.
- Register the correct sender ID per traffic type.
- Route promo and transactional streams separately.

## HTTP06 checklist

When you get HTTP06, work through: is the sender ID registered on both e& and du; does the sid string match the registration exactly; is it the right sender ID for promotional vs transactional; and is the account and route approved for the UAE. Verify a known-good, registered sender ID delivers first, then isolate what differs in the failing send.

- Registered on both operators? Exact string match?
- Correct sender ID for the traffic type?
- Account/route approved for the UAE?
- Test a known-good registered sender ID to isolate the issue.

## Related

- [Sender ID registration — UAE (TDRA)](https://www.broadnet.me/answers/sender-id-registration-uae-tdra)
- [SMS API reference](https://www.broadnet.me/developers/api)
- [What is a sender ID?](https://www.broadnet.me/answers/what-is-sender-id)