> For the complete documentation index, see [llms.txt](https://www.docpartner.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.docpartner.dev/api/sms-partner/envoyer-des-sms/compteur-de-caracteres.md).

# Compteur de caractères

Estime un SMS avant envoi : nombre de segments, encodage détecté, prix unitaire et coût total, selon le tarif de votre compte.

## URL

`POST` `https://api.smspartner.fr/v1/sms/estimate`

Rate limit : 30 requêtes / 30 secondes

## Paramètres

<table><thead><tr><th width="220">Nom</th><th>Valeur</th></tr></thead><tbody><tr><td><code>apiKey</code></td><td><a href="https://my.smspartner.fr/dashboard/api/paramaters">Votre clé API</a></td></tr><tr><td><code>text</code></td><td><strong>Obligatoire.</strong> Contenu du message à estimer. 10 000 caractères maximum.</td></tr><tr><td><code>country</code></td><td>Optionnel. Code pays ISO 3166-1 alpha-2 (ex : <code>FR</code>, <code>BE</code>) utilisé pour déterminer le tarif. Valeur par défaut : <code>FR</code>.</td></tr></tbody></table>

{% hint style="info" %}
Un message ne peut pas dépasser **10 SMS** (segments). Au-delà, l'API renvoie une erreur.
{% endhint %}

## Exemple de requête

```json
{
    "apiKey": "xxx",
    "text": "Merci pour votre commande livraison prévue demain avant midi !",
    "country": "FR"
}
```

## Réponse

<table><thead><tr><th width="220">Champ</th><th>Valeur</th></tr></thead><tbody><tr><td><code>sms_count</code></td><td>Nombre de segments SMS nécessaires pour envoyer le message.</td></tr><tr><td><code>encoding</code></td><td>Encodage détecté : <code>GSM-7</code> (alphabet standard) ou <code>UCS-2</code> (caractères Unicode, ex : emojis, accents étendus).</td></tr><tr><td><code>cost_per_sms</code></td><td>Prix unitaire par segment SMS, selon le tarif de votre compte.</td></tr><tr><td><code>total_cost</code></td><td>Coût total estimé (<code>cost_per_sms</code> × <code>sms_count</code>).</td></tr><tr><td><code>is_unicode_required</code></td><td>Présent et à <code>true</code> uniquement lorsque l'encodage est <code>UCS-2</code> (le message contient des caractères Unicode). Absent sinon.</td></tr></tbody></table>

{% tabs %}
{% tab title="Réponse (UCS-2)" %}

```json
{
    "sms_count": 2,
    "encoding": "UCS-2",
    "cost_per_sms": 0.038,
    "total_cost": 0.076,
    "is_unicode_required": true
}
```

{% endtab %}

{% tab title="Réponse (GSM-7)" %}

```json
{
    "sms_count": 1,
    "encoding": "GSM-7",
    "cost_per_sms": 0.038,
    "total_cost": 0.038
}
```

{% endtab %}
{% endtabs %}

## Erreurs

En cas d'erreur, la réponse a la forme `{ "success": false, "message": "..." }` avec le statut HTTP correspondant.

<table><thead><tr><th width="160">Statut HTTP</th><th>Cas</th></tr></thead><tbody><tr><td><code>400</code></td><td>JSON invalide, paramètre <code>text</code> manquant, <code>text</code> de plus de 10 000 caractères, ou message dépassant 10 SMS.</td></tr><tr><td><code>401</code></td><td><code>apiKey</code> manquante ou invalide.</td></tr><tr><td><code>429</code></td><td>Limite de débit dépassée (30 requêtes / 30 secondes).</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.docpartner.dev/api/sms-partner/envoyer-des-sms/compteur-de-caracteres.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.