Complete API documentation for developers to integrate with the AIVY platform
Your API key grants access to the AIVY API. Keep it secure and never share it publicly. Learn more about authentication
The AIVY API allows developers to integrate with our platform and access its features programmatically. This documentation provides all the information you need to get started with the API, including authentication, endpoints, and examples.
All API requests should be made to the following base URL:
The API accepts request data in JSON format. Make sure to set the following headers in your requests:
All responses are returned in JSON format. A typical response structure looks like this:
In case of an error, the API will return a JSON response with an error message and appropriate HTTP status code:
The AIVY API uses API keys for authentication. Each request must include your API key in the Authorization header.
To get an API key, follow these steps:
Your API key carries many privileges, so be sure to keep it secure. Don't share your API key in publicly accessible areas such as GitHub, client-side code, or in your frontend application.
Include your API key in the Authorization header of each request:
When creating an API key, you can specify the permissions it should have. Available permissions include:
To ensure the stability of the API, rate limits are applied to all endpoints. The current rate limits are:
Plan | Rate Limit | Burst Limit |
---|---|---|
Free | 60 requests per minute | 100 requests |
Pro | 300 requests per minute | 500 requests |
Enterprise | 1000 requests per minute | 2000 requests |
Each response includes headers that provide information about your current rate limit status:
If you exceed the rate limit, you will receive a 429 Too Many Requests response with a Retry-After header indicating how long to wait before making another request.
The API uses conventional HTTP response codes to indicate the success or failure of an API request. In general:
Status Code | Description |
---|---|
400 Bad Request | The request was invalid or cannot be otherwise served |
401 Unauthorized | Authentication credentials were missing or incorrect |
403 Forbidden | The request is understood, but it has been refused or access is not allowed |
404 Not Found | The requested resource could not be found |
429 Too Many Requests | You have exceeded the rate limit |
500 Internal Server Error | Something went wrong on our end |
All error responses follow this format:
These endpoints allow you to access and manage user information.
Retrieves the profile information of the authenticated user.
No parameters required.