Executes the specified agent and returns a non-streaming JSON response with the complete agent output. The agent must be in active status and belong to the specified account. locationId is required in the request body. Session Management:Documentation Index
Fetch the complete documentation index at: https://developers.leadwaycrm.com/llms.txt
Use this file to discover all available pages before exploring further.
- For the first message in a new session, do not include the
executionIdin the request payload. - The API will return an
executionIdalong with the agent response, which uniquely identifies this conversation session. - To continue the conversation within the same session, include the
executionIdfrom the previous response in subsequent requests. This allows the agent to maintain conversation context and history across multiple interactions.
Autorizacion
Bearer token generado desde el portal Leadway. Ver Autenticacion.
Version de la API.
Path parameters
Query parameters
Body
Message to send to the agent
Unique session identifier that maintains conversational context across multiple interactions within the same agent session. Omit this field for the first message in a new session. Include the executionId returned from the previous response to maintain context in subsequent messages.
Input variables to pass to the agent. These should match the input variables defined in the agent configuration.
Published version ID to execute. If not provided, the latest published production version will be used.
Attachments for the message
Account ID
Contact ID to associate with this execution. When provided, contact data will be hydrated and made available to the agent.
Respuestas
200 - Agent executed successfully
200 - Agent executed successfully
Success status
Unique session identifier that maintains conversational context across multiple interactions within the same agent session. Use this ID in subsequent requests to continue the conversation.
Unique identifier for a single interaction cycle, consisting of one user input and the corresponding agent response. Each message exchange generates a new interactionId.
Agent response text
Response type
Expected input type for next interaction
When end node is added in the graph, this will be true if the agent reached the end node in the graph
Execution status
Whether flow was switched
Response attachments
Generated outputs
400 - Agent is not active or invalid request - locationId is required
400 - Agent is not active or invalid request - locationId is required
401 - Unauthorized
401 - Unauthorized
403 - User does not have required scopes to execute this agent
403 - User does not have required scopes to execute this agent
404 - Agent not found
404 - Agent not found
422 - Unprocessable Entity
422 - Unprocessable Entity
500 - Internal Server Error
500 - Internal Server Error

