Organizer API private pilot

Connect your award programto your own systems

The current API is tenant-scoped: an organizer can read data from its own Awardee workspace. It is not a global talent, credential-verification, or public-directory API.

Request pilot access Create a Professional workspace

Tenant scoped

Every API key is bound to one organization. Award lookups never cross that organization boundary.

Bearer-key authentication

Organization admins create an API key after the Integrations module is enabled. The full key is shown once.

Plan-based limits

Professional includes 1,000 requests per hour. Enterprise includes 10,000 requests per hour.

Implemented read endpoints

GET /api/v1/awards
GET /api/v1/awards/:slug
GET /api/v1/awards/:slug/editions
GET /api/v1/awards/:slug/categories
GET /api/v1/awards/:slug/stats
GET /api/v1/awards/:slug/judges
GET /api/v1/awards/:slug/winners
GET /api/v1/awards/:slug/nominees

Write access for POST /api/v1/submissions is included only in an approved Professional or Enterprise pilot. API voting is not available.

Request

curl https://awardee.org/api/v1/awards \
  -H "Authorization: Bearer ak_live_YOUR_KEY"

Response envelope

{
  "data": [],
  "meta": {
    "requestId": "request-uuid",
    "rateLimit": {
      "limit": 1000,
      "remaining": 999,
      "resetAt": "2026-08-01T18:00:00.000Z"
    }
  }
}

Pilot acceptance criteria

We review the integration use case, required permissions, expected volume, data handling, and launch support before enabling access.

Discuss an integration pilot