Enjo API

introduction this api allows external clients to connect with enjo's ai agents users can send messages to the agents and automate workflows like generating support tickets the api provides endpoints for seamless communication with ai agents through enjo's platform the api supports secure communication through bearer token based authentication authentication to access the api, developers must authenticate using bearer tokens these tokens are generated through the personal access token settings within your workspace once created, the bearer token can be included in the authorization header of your api requests to authenticate and interact with the api securely accessing api settings navigate to personal access tokens click on your settings icon in the bottom right corner of the enjo dashboard select personal access token from the left sidebar create a token click the create token button assign a name to your token a new token will be generated— make sure to copy it immediately, as it will not be displayed again make sure to copy it immediately, as it will not be displayed again making your first api request ticketing configuration the bot can automatically generate a ticket if it is configured with a ticketing platform if ticketing is not configured, refer to the ai agent ticketing configuration guide https //docs enjo ai/ai agent ticketing api response structure upon a successful interaction with the bot or the creation of a ticket, the api response will include comprehensive details this ensures full transparency and traceability of the conversation and any actions the bot takes, such as creating a ticket table format describes the structure and details of the response field type description success boolean indicates whether the api call was successful (true) or encountered an error (false) data object contains the primary data in the response when the api call is successful ├── answers string the bot's response or answer to the user query, may include detailed text, facts, or solutions ├── sources array of objects lists the sources from where the answers are derived │ ├── type the type of source (e g jira , knowledge base) │ ├── name string name or title of the source │ ├── score float confidence score of the source's relevance to the query │ ├── url string url link to the source where more information can be found ├── conversationid string a unique identifier to track the conversation and ensure continuity across multiple interactions ├── ticketdetails object details about the ticket created in the external system (if applicable) │ ├── url string url to access the ticket in the external system │ ├── attributes string metadata and additional information about the ticket │ ├── id string unique identifier for the ticket │ ├── type string the category or type of issue raised in the ticket │ ├── status string current status of the ticket (e g , open, closed) │ ├── priority string priority level of the ticket (e g , low, medium, high) │ ├── description string description of the issue or request in the ticket │ ├── createddate string timestamp indicating when the ticket was created │ ├── lastmodifieddate string timestamp indicating the last time the ticket was modified rate limiting limit 20 requests per minute per ip response (when limit exceeded) { "code" "rate limit error", "message" "rate limit exceeded", "status" 429 } throttling limit 10 requests per 5 seconds per ip response (when throttling triggered) { "code" "rate limit error", "message" "rate limit exceeded", "status" 429 } troubleshooting guid e issue "invalid botid" error solution double check that the bot id in your request matches the one listed in your enjo dashboard issue no ticket response was received solution confirm that the bot is properly set up for ticketing for setup details, refer to the ai agent ticketing configuration guide