Arkloop Developers

API Overview

The Arkloop API is a RESTful HTTP API with a base path of /v1.

Base URL

EnvironmentURL
Local Development (Direct)http://127.0.0.1:19001
Local Development (via Gateway)http://127.0.0.1:19000

Authentication

All protected endpoints require a Bearer Token in the request header:

Authorization: Bearer <access_token>

Tokens are obtained via POST /v1/auth/login. After expiration, use the Refresh Token to obtain a new token (POST /v1/auth/refresh). After login, the Refresh Token is stored in an HttpOnly cookie by the server; the front-end refreshes the Access Token by calling the refresh endpoint.

API Key authentication is also supported for some endpoints:

Authorization: Bearer al_...

Error Response Format

{
  "error": "error.code",
  "message": "human-readable description",
  "trace_id": "...",
  "details": {}
}

Common error codes:

HTTP Status CodeError CodeDescription
400validation.errorRequest parameter validation failed
401auth.unauthorizedUnauthorized or invalid token
403auth.forbiddenInsufficient permissions
404not_foundResource not found
409conflictResource conflict (e.g., duplicate creation)
422validation.errorRequest body parsing failed
429rate_limitRequest frequency limit exceeded
500internal_errorInternal server error

Pagination

List endpoints that support pagination use cursor-based pagination:

GET /v1/threads?limit=20&before=<cursor>

SSE (Server-Sent Events)

Run execution progress is pushed via SSE events. For details, see Run Execution Endpoints.

Endpoint Index

Auth & Account

  • Auth — Login, registration, token refresh, email verification
  • Me — Personal info, usage, credits, invitation codes
  • API Keys — Programmatic access keys

Core Resources

Accounts

  • Accounts — personal and workspace accounts, memberships

Configuration

Billing & Entitlements

Notifications & Webhooks

Admin

System

On this page