Loading ...

REST API: Axero Copilot Get Profiles | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Axero Copilot » REST API: Axero Copilot Get Profiles
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 24

REST API: Axero Copilot Get Profiles

0 
 /5
0 (0votes)
Open API Guide
GET/api/chatbot/profile

Retrieve all Axero Copilot profiles accessible to the authenticated user. Only profiles whose configured roles include the current user are returned. Use this to discover available profiles before initiating conversations.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.

Required Parameters

ParameterTypeRequiredLocationDescription
Bearer TokenStringYESHeaderAuthorization Header: Authorization: Bearer YOUR_JWT_TOKEN Most secure method. Include your Bearer token in the Authorization header of every request.

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

https://your-site.com/api/chatbot/profile

Success Response

{
  "IsError": false,
  "ResponseMessage": "Success message.",
  "ResponseData": null
}

Error Response

{
  "IsError": true,
  "ResponseMessage": "Required parameter is missing or invalid.",
  "ResponseData": null
}

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestOne or more required fields are missing or invalid.Verify the request payload against the required parameters.
401 UnauthorizedMissing or invalid Bearer token.Check token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissions.Confirm the user has the required roles for this action.
500 Server ErrorInternal failure.Retry later.

Rate Limits

While Axero does not enforce hard rate limits by default, we recommend the following best practices to ensure optimal performance:

  • Sustained Request Rate: Do not exceed 5 API calls per second
  • Sequential Processing: Wait for each request to complete before sending the next in automated workflows
  • Concurrent Connections: If parallel processing is required, limit to 3 or fewer simultaneous requests
  • Response Timeout: Ensure API responses complete within 15 seconds during testing

Axero may implement temporary rate restrictions if excessive API usage affects overall site performance. For high-volume integrations, contact Axero to discuss your requirements.

Wiki Index

Pages