Archiver une restriction alimentaire (status → archived)

DELETE

/v1/guests/{id}/dietary/{rid}

const url = 'https://example.com/v1/guests/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/dietary/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0';
const options = {method: 'DELETE', headers: {'X-API-Key': '<X-API-Key>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url https://example.com/v1/guests/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/dietary/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0 \
  --header 'X-API-Key: <X-API-Key>'

Archive une restriction (status → ‘archived’). L’archivage n’est PAS un DELETE physique — la traçabilité est conservée. Le DELETE physique est réservé à l’anonymisation RGPD art.17. Idempotent : si déjà archivée, retourne 204. :rid = UUID surrogate de la restriction (champ id de GET /v1/guests/:id/dietary).

Authorizations

ApiKeyAuth
BearerAuth

Parameters

Path Parameters

required

string format: uuid

UUID du profil guest

rid

required

string format: uuid

UUID surrogate de la restriction

Responses

204

Restriction archivée

404

Guest introuvable

application/json

object

code

required

Code machine de l’erreur

string

message

required

Message lisible

string

origin

Origine domaine de l’erreur (optionnel)

object

boundedContext

string

module

string

status

required

integer

traceId

required

Identifiant de corrélation pour le support

string

Example

{
  "code": "RESERVATION_NOT_FOUND",
  "message": "Réservation introuvable",
  "status": 404
}