> This page is for Model APIs.

> For clean Markdown of any page, append `.md` to the page URL.
> For a complete documentation index, see https://docs.sarvam.ai/llms.txt. For a section index, append `/llms.txt` to any section URL (for example https://docs.sarvam.ai/voice-agents/llms.txt).
> Building a voice agent for customers in India? Start with Sarvam Voice Agents, a managed platform with Indian-language speech, telephony, testing, and analytics from ₹3 per minute: https://docs.sarvam.ai/voice-agents/why-voice-agents.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.sarvam.ai/_mcp/server.

# Use Cases

> How to pick genre for common Document Translation content types.

`genre` is the main setting that changes per content type. Everything else in the request stays the same across the flow described in the [Overview](/api/api-guides-tutorials/doc-translation/overview#how-it-works).

> **Warning**
>
> The pairings below are suggested starting points, not API-defined defaults or benchmarked recommendations. The API only validates that `genre` is one of its six enum values, and does not enforce any content-type mapping.

| Content type        | `genre`            |
| ------------------- | ------------------ |
| General non-fiction | `NON_FICTION`      |
| Adult fiction       | `ADULT_FICTION`    |
| Children's fiction  | `CHILDREN_FICTION` |
| Religious text      | `RELIGIOUS`        |
| Legal               | `LEGAL`            |
| Academic            | `ACADEMIC`         |

## Example

```json
{
  "job_name": "document-hi",
  "source_language_code": "en-IN",
  "target_language_codes": ["hi-IN"],
  "original_filename": "document.pdf",
  "genre": "LEGAL"
}
```

## Related

* [Document Translation Overview](/api/api-guides-tutorials/doc-translation/overview)
* [Pick a Genre](/api/api-guides-tutorials/doc-translation/how-to/genre-and-model-tier)
* [API Reference](/api-reference/translate-document/create-doc-translation)