Files
mintlify[bot] 63f716768d Improve SEO descriptions on 19 pages (#5152)
* Improve SEO descriptions on 19 pages with short metadata

Generated-By: mintlify-agent

* Apply suggestions from code review

Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
2026-04-06 10:26:12 -07:00

58 lines
1.5 KiB
Plaintext

---
title: "Response fields"
description: "Document API response fields using the ResponseField component with type annotations, descriptions, and required or optional indicators."
keywords: ["API output", "return values", "response structure"]
---
Use the `<ResponseField>` component to define the return values of an API. Many docs also use `<ResponseField>` on pages when you need to list the types of something.
<ResponseField name="response" type="string" required>
A response field example
</ResponseField>
```mdx
<ResponseField name="response" type="string" required>
A response field example
</ResponseField>
```
## Props
<ResponseField name="name" type="string" required>
The name of the response value.
</ResponseField>
<ResponseField name="type" type="string" required>
Expected type of the response value - this can be any arbitrary string.
</ResponseField>
<ResponseField name="default" type="string">
The default value.
</ResponseField>
<ResponseField name="required" type="boolean">
Show "required" beside the field name.
</ResponseField>
<ResponseField name="deprecated" type="boolean">
Whether a field is deprecated or not.
</ResponseField>
<ResponseField name="pre" type="string[]">
Labels that are shown before the name of the field
</ResponseField>
<ResponseField name="post" type="string[]">
Labels that are shown after the name of the field
</ResponseField>
<RequestExample>
```mdx Response Field Example
<ResponseField name="response" type="string" required>
A response field example
</ResponseField>
```
</RequestExample>