Changes and versions

Documented SMS contract : 2.0.2

This documentation describes the reviewed SMS contract identified above. Live service availability is separate from its version.

SMS v2.0.2 · Retries after erasure of personal data

The SMS v2.0.2 contract specifies the 410 personal_data_erased response when replaying POST /api/sms/v2/messages/ after targeted erasure of a completed message’s personal data. The same key and content trigger no new send or credit movement. Retain the key and stop retrying that operation; do not resubmit the message with a new key.

Different content with the same key remains a 409 idempotency_conflict. The error catalogue and idempotency guide provide the exact response and required action.

September 30, 2026 · SMS v2.0.1 and developer portal available

SMS v2.0.1 is available to organizations with an active SMS installation. The contract covers immediate sending, scheduling, batches, credits, contacts and delivery tracking. Organization keys and the permissions required by each operation still apply.

Version 2.0.1 makes SMS v2 temporary unavailability responses consistent. The service_unavailable code and retry rules using the same idempotency key are detailed in the error catalogue.

Befiana for Developers launches with:

• Complete French and English guides for preparing access, sending, scheduling and tracking messages.
• A first SMS walkthrough and Node.js/Python recipes for retries and pagination.
• An API reference generated from the SMS v2.0.1 contract, with translated descriptions and identical JSON examples in both languages.
• A published SMS v2.0.1 Postman collection with all seven operations, private variables to fill in and idempotency keys retained for retries.

V1 integrations remain available during migration. No retirement date is announced.

SMS v2

The v2 reference covers organization Bearer keys, UUID message identifiers, required idempotency, RFC 3339 scheduling and retrievable batches. V1 remains accessible during migration.

The exact contract version appears in the English OpenAPI document. Documentation is published with the contract for the corresponding backend release.

Compatibility

A correction preserves the public contract. A compatible enhancement can add a capability without invalidating existing usage. A breaking change requires a new major namespace. Cloud interface changes and product API changes have separate versions.

Public release notes are also available in the BEFIANA Cloud developer area.

Service availability

The contract version describes supported requests and responses. It does not report live API health or a message’s delivery. No real-time service status page is currently announced in this portal.

For an integration incident, prepare a support request. For an individual SMS, read its delivery reports.

V1 deprecation

Migration begins with v2 general availability, after validation of functional coverage. No v1 retirement date is set here. A later announcement will describe affected use cases, timing and available migration support.

Follow the migration guide to prepare your application. Confirm commitments specific to your agreement with BEFIANA.