> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# API reference template

> Create API operation pages that Mintlify renders from the matching service specification.

## Endpoint pages

***

API operation pages are rendered from the matching OpenAPI or Swagger source. Each operation page contains only frontmatter: an `openapi` key that points to the rendered specification, plus optional `title` and `description` keys that override the rendered values:

```mdx theme={null}
---
openapi: "/en/openapi/v3-current/<spec>.yaml <method> <path>"
---
```

Use the matching `/es/` or `/pt/` specification prefix in the translated page. The method and path stay identical in every locale.

Mintlify renders the operation details from the specification. Do not manually duplicate parameters, request and response examples, error bodies, or endpoint descriptions in an operation page.

## Updating an operation

***

Update the service's canonical API contract first. Then sync the rendered specifications and keep the operation stubs aligned with the resulting method and path. This keeps the reference accurate across all supported languages.

## Before publishing

***

* Verify that the rendered specification contains the operation.
* Use the same method and path in each locale.
* Keep behavioral descriptions, schemas, and examples in the service contract rather than in a hand-written operation page.
