---
title: "Write the surety's handwritten mention (guarantor, no login)"
method: POST
path: "/public/guest-signature/{token}/mention"
tags: ["Guest Signature", "Signatures"]
---

# Write the surety's handwritten mention (guarantor, no login)

`POST /public/guest-signature/{token}/mention`

## Request

- Base URL: `https://api.faireplace.com/api`
- URL: `https://api.faireplace.com/api/public/guest-signature/{token}/mention`
- Auth: none required

A guarantor (caution) types, in their own words, the mention required by
article 2297 of the French Civil Code. **This must happen before
`POST /public/guest-signature/{token}/sign`**: without a mention written by the surety themselves, the
undertaking is void. The deed is regenerated with their characters and
only then can be signed.

The text is compared to the expected mention by the domain, which owns
the tolerance on accents and punctuation. Nothing is normalised
client-side: the proof has to stay literal, so send the keystrokes as
typed.

## Typing evidence
The optional `mode_saisie`, `evenements_saisie` and `duree_saisie_ms`
fields record *how* the text arrived in the field. Case law accepts a
keyboard-entered mention on the basis that the surety actually typed it,
and these fields are what lets you say so. They are reported by the
client, so they are never probative on their own, but omitting
`mode_saisie` records the undertaking with an unknown input mode, and it
will never be assumed to have been typed.

## Why a rejection is 422 and not 400
A non-conforming mention is a well-formed request; what is not
constituted is the undertaking. On `MENTION_NON_CONFORME` the response
carries `mention_attendue` so the surety can copy it without guessing
what they missed.

## Path parameters

- `token` string, required

## Request body

- object
  - `mention` string, required: The text as typed, unmodified.
  - `mode_saisie` 'TYPED' | 'PASTED' | 'DROPPED', nullable: How the text entered the field. Omit only if you genuinely cannot tell: the undertaking is then recorded with an unknown input mode.
  - `evenements_saisie` integer, nullable: Number of input events. Real typing produces hundreds.
  - `duree_saisie_ms` integer, nullable: Milliseconds between the first keystroke and validation.

## Response `200`

Mention accepted and the deed regenerated: signing can follow.

- object
  - `apposee_le` string, date-time: When the mention was recorded.

## Other responses

- `404`: Unknown, invalid or not-yet-wired session. Deliberately indistinguishable from "feature not deployed" so nothing leaks about the deployment state.
- `410`: The guest session expired or was already used.
- `422`: The undertaking is not constituted. `mention_attendue` is present on `MENTION_NON_CONFORME`.
- `423`: Too many attempts: the session is temporarily locked. See `Retry-After`.
- `500`: Internal Server Error

---

[API](https://skmtc.dev/faireplace/apis/faireplace-property-management-api.md) · [All operations](https://skmtc.dev/faireplace/apis/faireplace-property-management-api/llms.txt) · [OpenAPI document](https://skmtc.dev/faireplace/apis/faireplace-property-management-api/revisions/69de39762919?raw)