API Reference

This page describes the expected structure of AeThex APIs.

Note

Endpoint names may vary by active service. Use this as a contract guide until individual service references are published.


Base Concepts

AeThex APIs generally use:

  • HTTPS JSON requests
  • Bearer tokens or API keys
  • Scoped permissions
  • Structured error objects
  • Webhooks for async events

Common Resources

Resource Purpose
/auth Authentication and token exchange
/passport User identity and profile context
/accounts Linked account references
/projects Creator/developer projects
/games Game and experience integration
/locker Inventory and asset context
/webhooks Event subscription management

Example Response Shape

{
  "ok": true,
  "data": {},
  "requestId": "req_..."
}

Example Error Shape

{
  "ok": false,
  "error": {
    "code": "unauthorized",
    "message": "Missing or invalid credentials"
  },
  "requestId": "req_..."
}

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9