Documentation Index
Fetch the complete documentation index at: https://v4-docs.alfaone.app/llms.txt
Use this file to discover all available pages before exploring further.
Base URL
All API requests should be made to:Authentication
All endpoints require an API key passed in thex-api-key header:
Response Format
All responses are returned in JSON format. Successful responses will include the requested data, while error responses will include anerror field with a descriptive message.
Success Response
Error Response
HTTP Status Codes
| Status Code | Description |
|---|---|
200 | Success - Request completed successfully |
201 | Created - Resource was created successfully |
400 | Bad Request - Invalid or missing request parameters |
401 | Unauthorized - Invalid or missing API key |
404 | Not Found - The requested resource doesn’t exist |
409 | Conflict - The resource already exists |
429 | Too Many Requests - Rate limit exceeded |
500 | Internal Server Error - Something went wrong on our end |
Available Endpoints
Assessments
List, retrieve, and view questions for assessments
Members
Access organization member information
Invites
Send assessment invites and track their status
Tags
Create, update, and manage organization tags
Pagination
All list endpoints support pagination through query parameters. Results are returned alongside apagination metadata object.
Query Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
page | integer | 1 | Page number (1-indexed) |
limit | integer | 20 | Items per page (min 1, max 100) |
sort | string | varies | Field to sort by (see each endpoint for allowed values) |
order | string | desc | Sort direction: asc or desc |
Example Request
Paginated Response
Every list response includes apagination object alongside the resource array:
| Field | Description |
|---|---|
page | The current page number |
limit | The number of items per page |
total | The total number of items across all pages |
totalPages | The total number of pages |
Versioning
The API is versioned via the URL path (/api/v1/). When breaking changes are introduced, a new version will be released while maintaining support for previous versions during a deprecation period.