GET /v1/agent-templates/{slug}
const url = 'https://seu-endereco-da-api/v1/agent-templates/example';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://seu-endereco-da-api/v1/agent-templates/example \ --header 'Authorization: Bearer <token>'Permissão que a Chave de acesso precisa: Ler agentes de IA (agents:read).
Authorizations
Seção intitulada “Authorizations”Parameters
Seção intitulada “Parameters”Path Parameters
Seção intitulada “Path Parameters”Responses
Seção intitulada “Responses”object
Key of the closed icon catalog the gallery draws
object
Name the agent introduces itself with
Https address of the agent picture
The first customer message of the example conversation and the agent reply to it, for the gallery card
object
What the template does and its whole example conversation, so the gallery search finds it by task
object
The published version an agent created now would get
object
The template works without it, with less
The account does not have it yet: the gallery shows it in orange with Connect
Belongs to the agent being created (knowledge): the setup wizard prepares it, so it is never missing
Stable key of the screen where the owner connects it
First message of the template, so the test chat starts as the agent would
Messages { from: contact | agent, text }
object
{ conversation: string[], system: string[] }
object
{ question, expected }
object
At most 3 { key, label, suggestions by business type, target }
object
Template suggested to take the conversation when this one finishes
object
Example
{ "icon": "sparkles", "preview": [ { "from": "contact" } ], "requirements": [ { "key": "asaas" } ]}