POST
/
v1
/
experimental
/
templatize_prompt
curl -X POST https://api.anthropic.com/v1/experimental/templatize_prompt \
     --header "x-api-key: $ANTHROPIC_API_KEY" \
     --header "anthropic-version: 2023-06-01" \
     --header "anthropic-beta: prompt-tools-2025-04-02" \
     --header "content-type: application/json" \
     --data \
'{
    "messages": [{"role": "user", "content": "Translate hello to German"}],
    "system": "You are an English to German translator"
}'
{
  "messages": [
    {
      "content": [
        {
          "text": "Translate {{WORD_TO_TRANSLATE}} to {{TARGET_LANGUAGE}}",
          "type": "text"
        }
      ],
      "role": "user"
    }
  ],
  "system": "You are a professional English to {{TARGET_LANGUAGE}} translator",
  "usage": [
    {
      "input_tokens": 490,
      "output_tokens": 661
    }
  ],
  "variable_values": {
    "TARGET_LANGUAGE": "German",
    "WORD_TO_TRANSLATE": "hello"
  }
}

Les APIs d’outils de prompt sont en aperçu de recherche fermé. Demander à rejoindre l’aperçu de recherche fermé.

​
Avant de commencer

Les outils de prompt sont un ensemble d’APIs pour générer et améliorer les prompts. Contrairement à nos autres APIs, il s’agit d’une API expérimentale : vous devrez demander l’accès, et elle n’a pas le même niveau d’engagement pour le support à long terme que les autres APIs.

Ces APIs sont similaires à ce qui est disponible dans l’Anthropic Workbench, et sont destinées à être utilisées par d’autres plateformes d’ingénierie de prompt et terrains de jeu.

​
Commencer avec l’améliorateur de prompt

Pour utiliser l’API de génération de prompt, vous devrez :

  1. Avoir rejoint l’aperçu de recherche fermé pour les APIs d’outils de prompt
  2. Utiliser l’API directement, plutôt que le SDK
  3. Ajouter l’en-tête beta prompt-tools-2025-04-02

Cette API n’est pas disponible dans le SDK

​
Modéliser un prompt

Headers

​
anthropic-beta
string[]

Optional header to specify the beta version(s) you want to use.

To use multiple betas, use a comma separated list like beta1,beta2 or specify the header multiple times for each beta.

​
x-api-key
string
required

Your unique API key for authentication.

This key is required in the header of all API requests, to authenticate your account and access Anthropic's services. Get your API key through the Console. Each key is scoped to a Workspace.

Body

application/json
​
messages
object[]
required

The prompt to templatize, structured as a list of message objects.

Each message in the messages array must:

  • Contain only text-only content blocks
  • Not include tool calls, images, or prompt caching blocks

Example of a simple text prompt:

[
  {
    "role": "user", 
    "content": [
      {
        "type": "text",
        "text": "Translate hello to German"
      }
    ]
  }
]

Note that only contiguous user messages with text content are allowed. Assistant prefill is permitted, but other content types will cause validation errors.

Examples:
[
  {
    "content": [
      {
        "text": "Translate hello to German",
        "type": "text"
      }
    ],
    "role": "user"
  }
]
​
system
string | null

The existing system prompt to templatize.

{
  "system": "You are a professional English to German translator",
  [...]
}

Note that this differs from the Messages API; it is strictly a string.

Examples:

"You are a professional English to German translator"

Response

200
application/json
Successful Response
​
messages
object[]
required

The templatized prompt with variable placeholders.

The response includes the input messages with specific values replaced by variable placeholders. These messages maintain the original message structure but contain uppercase variable names in place of concrete values.

For example, an input message content like "Translate hello to German" would be transformed to "Translate {{WORD_TO_TRANSLATE}} to {{TARGET_LANGUAGE}}".

{
  "messages": [
    {
      "role": "user",
      "content": [
        {
          "type": "text",
          "text": "Translate {{WORD_TO_TRANSLATE}} to {{TARGET_LANGUAGE}}"
        }
      ]
    }
  ]
}
Examples:
[
  {
    "content": [
      {
        "text": "Translate {{WORD_TO_TRANSLATE}} to {{TARGET_LANGUAGE}}",
        "type": "text"
      }
    ],
    "role": "user"
  }
]
​
system
string
required

The input system prompt with variables identified and replaced.

If no system prompt was provided in the original request, this field will be an empty string.

Examples:

"You are a professional English to {{TARGET_LANGUAGE}} translator"

​
usage
object
required

Usage information

​
variable_values
object
required

A mapping of template variable names to their original values, as extracted from the input prompt during templatization. Each key represents a variable name identified in the templatized prompt, and each value contains the corresponding content from the original prompt that was replaced by that variable.

Example:

"variable_values": {
  "WORD_TO_TRANSLATE": "hello",
  "TARGET_LANGUAGE": "German"
}

In this example response, the original prompt – Translate hello to German – was templatized to Translate WORD_TO_TRANSLATE to TARGET_LANGUAGE, with the variable values extracted as shown.

Examples:
{
  "TARGET_LANGUAGE": "German",
  "WORD_TO_TRANSLATE": "hello"
}