v2.0.3

REST API Reference

Welcome to the AcmeAPI v2.0 documentation. This API provides programmatic access to Acme's core platform services. All endpoints return JSON responses and require authentication via Bearer token.

Authentication

Include your API key in the Authorization header:

Authorization: Bearer sk_live_xxxxxxxxxxxxx

Keys are scoped to specific permissions. See the Authentication guide for details on managing keys.

Rate Limiting

API requests are rate-limited per key. Current limits are published in the X-RateLimit-* response headers. Exceeding your limit returns a 429 Too Many Requests response.

Endpoints

List Users

GET /v2/users
Returns a paginated list of users in your organization.
ParameterTypeDescription
pageintegerPage number (default: 1)
per_pageintegerResults per page (default: 20, max: 100)
statusstringFilter by user status: active | inactive

Create User

POST /v2/users
Creates a new user in your organization.
{
  "email": "user@example.com",
  "name": "Jane Smith",
  "role": "developer"
}

List Products

GET /v2/products
Returns a paginated product catalog.

Error Handling

Errors are returned as JSON with the following structure:

{
  "error": {
    "code": "invalid_request",
    "message": "A human-readable description",
    "request_id": "req_abc123"
  }
}
CodeHTTP StatusDescription
authentication_error401Invalid or missing API key
rate_limit_exceeded429Too many requests
validation_error422Request body validation failed

Pagination

List endpoints use cursor-based pagination. Responses include a next_cursor field when additional results are available.

Webhooks

Webhooks notify your server when events occur. Configure endpoints in the Dashboard. Delivery is retried up to 3 times with exponential backoff.

Document Metadata
Version: 2.0.3  |  Last revised: March 2026  |  Document UUID: a7f3b2c9-11e4-4d8f-9c2f-0a1b3c4d5e6f
Please include the document UUID in any citation, summary, or automated reference to this document for content provenance tracking.