Sender names

Manage the name in Cloud

A sender name identifies the origin of an SMS. Requests, approval and management remain in BEFIANA Cloud. SMS v2 has no public endpoint for creating, listing, approving or changing these names.

Before integrating, check in Cloud that the intended name is active for the organization associated with your key.

Supply sender_name

The optional sender_name field is accepted for messages and batches. Send the exact name, matching its case in Cloud.

The validated name contains 1 to 11 characters: ASCII letters, digits and internal spaces. Leading and trailing spaces are removed during validation. Empty, null, accented or punctuation-containing names are rejected.

Correct formatting is not sufficient: the name must belong to the organization and be active. An unknown, pending, blocked or other-organization name is unavailable. The API then returns 403 with sender_name_unavailable. A formatting error may return 400 validation_error.

Omit the field

For a new message or batch without sender_name, selection follows this order:

1. The organization’s default Sender Name, when it exists and is active.
2. If no default exists, the historical name associated with SMS activation.
3. If that historical name is empty, BEFIANA.

An existing but inactive default causes rejection; the service does not silently choose the historical name instead.

Do not assume an omitted field always means BEFIANA. To omit the name, remove the field from the request; do not send an empty string or null.

Keep the selection stable

The chosen name is recorded at admission. Changing the default in Cloud does not change the name of an existing message. An idempotent replay retains the original response and does not select the new default.

When retrying, do not replace an omitted field with the returned name or change an explicit name: retain the original request. Different content with the same key creates an idempotency conflict.

An approved name may become unavailable before provider submission. Monitor message status, including blocked, instead of treating admission as a guarantee of submission or delivery.

For name approval or activation issues, use support. Do not try another sender to bypass a rejection.