Files
mintlify__docs/fr/components/responses.mdx
mintlify[bot] fbdd913d8e Add translation audit tracker (#5055)
* Add translation tracker for stale translations audit

Generated-By: mintlify-agent

* translations: add missing pages and update content for es, fr, zh

Phase 1: Add translations for 4 new API analytics pages (feedback-by-page,
searches, views, visitors) in es, fr, and zh.

Phase 2: Update 3 pages with content changes:
- agent/workflows: add "Disable a workflow" subsection
- ai/skillmd: add 24-hour generation note
- editor/publish: add AI PR title tip, reformat publishing workflows,
  promote "Publish your changes" heading from h3 to h2

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* update descriptions

* translations

* translations

* translations

* Delete TRANSLATION_TRACKER.md

* translations

* a

* a

* translations

* translations

* translations

* translations

* translations

* translations

* translations

* translations

* Update use-cases.mdx

* translations

* translations

* Update ai-native.mdx

* Update accordions.mdx

* Update accordions.mdx

* Update accordions.mdx

* translations

* translations

* Update fonts.mdx

* translations

* translations: update SEO descriptions for es, fr, zh (150 pages)

Update the description: frontmatter field across 150 pages × 3 languages
to match the current English descriptions updated on 2026-03-31.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-02 10:52:59 -07:00

60 lines
1.7 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
title: "Champs de réponse"
description: "Documentez les champs de réponse d’une API avec des annotations de type, des descriptions et des indicateurs obligatoire/facultatif."
keywords: ["sortie d’API", "valeurs de retour", "structure de réponse"]
---
Utilisez le composant `<ResponseField>` pour définir les valeurs de retour d’une API. De nombreuses documentations utilisent également `<ResponseField>` sur les pages lorsque vous devez lister les types de certains éléments.
<ResponseField name="response" type="string" required>
Exemple de champ de réponse
</ResponseField>
```mdx
<ResponseField name="response" type="string" required>
Exemple de champ de réponse
</ResponseField>
```
<div id="props">
## Props
</div>
<ResponseField name="name" type="string" required>
Nom de la valeur de réponse.
</ResponseField>
<ResponseField name="type" type="string" required>
Type attendu de la valeur de réponse — peut être n’importe quelle chaîne.
</ResponseField>
<ResponseField name="default" type="string">
Valeur par défaut.
</ResponseField>
<ResponseField name="required" type="boolean">
Afficher « required » à côté du nom du champ.
</ResponseField>
<ResponseField name="deprecated" type="boolean">
Indique si un champ est obsolète.
</ResponseField>
<ResponseField name="pre" type="string[]">
Étiquettes affichées avant le nom du champ
</ResponseField>
<ResponseField name="post" type="string[]">
Étiquettes affichées après le nom du champ
</ResponseField>
<RequestExample>
```mdx Response Field Example
<ResponseField name="response" type="string" required>
Exemple de champ de réponse
</ResponseField>
```
</RequestExample>