Search

Type to search documentation...

API Overview

Explore the Ajrly REST API — endpoints, request format, pagination, and filtering.

The Ajrly REST API gives you programmatic access to all platform features. This page covers the conventions and patterns used across all endpoints.

Base URL

https://api.ajrly.com/v1

All endpoints are relative to this base URL.

Request Format

Headers

Every request should include:

HeaderValueRequired
AuthorizationBearer <token>Yes
Content-Typeapplication/jsonFor POST/PUT
Acceptapplication/jsonRecommended
X-Request-IdUUID for request tracingOptional

Request Body

For POST and PUT requests, send JSON in the request body:

{
  "name": "My Project",
  "description": "A sample project",
  "visibility": "private"
}

Response Format

All responses follow a consistent structure:

Success Response

{
  "data": { ... },
  "meta": {
    "request_id": "req_abc123"
  }
}

List Response

{
  "data": [ ... ],
  "meta": {
    "total": 42,
    "page": 1,
    "per_page": 20,
    "request_id": "req_abc123"
  }
}

Error Response

{
  "error": {
    "code": "not_found",
    "message": "The requested resource was not found.",
    "status": 404,
    "request_id": "req_abc123"
  }
}

Pagination

List endpoints support cursor-based pagination:

ParameterTypeDefaultDescription
pagenumber1Page number
per_pagenumber20Items per page (max 100)
GET /v1/projects?page=2&per_page=50

Filtering

Most list endpoints support filtering:

GET /v1/projects?status=active&sort=created_at&order=desc

Common Filter Parameters

ParameterDescription
statusFilter by status
sortField to sort by
orderSort direction (asc or desc)
searchFull-text search
created_afterFilter by creation date
created_beforeFilter by creation date

HTTP Status Codes

CodeMeaning
200Success
201Created
204No Content (successful delete)
400Bad Request — invalid parameters
401Unauthorized — invalid or missing credentials
403Forbidden — insufficient permissions
404Not Found
429Too Many Requests — rate limit exceeded
500Internal Server Error

Versioning

The API is versioned through the URL path. The current version is v1.

When breaking changes are introduced, a new version will be released. Previous versions remain supported for at least 12 months after deprecation.

Last updated: February 25, 2026 Edit this page on GitHub

Was this page helpful?