Developer support
Contact BEFIANA
Section titled “Contact BEFIANA”Use the official BEFIANA contact form and include “SMS API integration” in your request subject. This is BEFIANA’s published general contact point, where you can ask to be directed to the appropriate support team.
If your agreement includes a dedicated support channel, use that channel. Response times and service commitments are those confirmed with BEFIANA.
For account, key or credit management, open BEFIANA Cloud. Cloud usage guides remain available in the help center.
Choose the right diagnosis
Section titled “Choose the right diagnosis”Scroll horizontally if needed. Keyboard: Tab, then the left and right arrow keys.
| Situation | Before contacting support |
|---|---|
401 or 403 | Check authentication, key permissions and the organization. |
409 | Record the precise code from the SMS error catalogue. |
| Lost response | Find the business operation and retry with the same idempotency key. |
| Uncertain provider outcome | Keep message_id, read its status and avoid an automatic new submission. |
| Rejected sender | Check the exact name and its state using the sender names guide. |
| Specific volume or integration | Describe the expected volume, sending window and type of messages. |
Prepare a technical request
Section titled “Prepare a technical request”Copy this template and fill it with your integration details. Fields are identical in both languages to make diagnosis easier.
Subject: SMS API integrationOrganization: <organization name or public identifier>API version: <documented contract version>Time and timezone: <YYYY-MM-DD HH:MM:SS +HH:MM>Operation: <HTTP method and path>HTTP status: <status received, or no response>Error code: <error.code, if present>Message or batch ID: <public UUID, if available>Expected behavior: <what should happen>Observed behavior: <what happened>Already checked: <authentication, permissions, credits, sender, retries>Add a minimal request and response with sensitive information removed. Remove the Authorization header, cookies, secrets, complete phone numbers and personal message content. Do not put an API key in the contact form.
Preserve useful evidence
Section titled “Preserve useful evidence”Keep the message or batch identifier, timestamp with timezone, error code and idempotency key in protected logs. An idempotency key may contain a business identifier: redact it in a general enquiry if it discloses personal information.
For an unknown outcome, state whether you received the creation response and which status the last lookup returned. A missing receipt does not prove failure. Do not resend the SMS to “repair” its tracking.
Read versions and availability to identify the documented contract. API availability and an SMS delivery status are separate pieces of information.