Get an API key
Keep it on your server.
A contributor API for adding projects, evidence, metrics, prototypes, and development updates.
Keep it on your server.
Include evidence and sourced project data.
New links appear in the feed.
Players can discuss and react.
Generate a Stats only key in Dashboard → API access. Existing project keys do not gain stats access automatically. Use a server-side Bearer key with the stats:read scope.
curl 'https://galaphoenixlabs.com/api/v1/stats?days=30' -H 'Authorization: Bearer YOUR_STATS_API_KEY'
Choose 7, 30 or 90 days. The JSON matches the dashboard metrics: verified GALA burns, full voting weight, network and project totals, traffic, wallet events, errors, community activity, prototype submissions and votes, referrals and status alerts. Some fields are explicitly all-time; daily charts use Pacific calendar days. Traffic counters include repeat visits, bots and QA. GET only; invalid periods return 400, missing/revoked keys 401, missing scopes 403 and rate limits 429. Keys are limited to 60 requests per minute and can be revoked immediately.
GET /api/phoenix/prototypes?game=walking-dead lists published prototypes ranked by confirmed GALA voting weight. Each includes its title, external HTTPS link, description, public author, vote count and votingGala. Prototype votes also count toward the game total.
Players can submit from the game’s Prototypes tab as guests. Submissions create a feed announcement and shared discussion automatically. The website uses same-origin POST /api/phoenix/prototypes with game, title, url, description, clientKey, optional displayName and rightsConfirmed:true. Submission retries are idempotent; duplicate links and unsafe URLs are rejected. A prototype vote is a separate wallet-authorized contribution from 1,000 GALA and does not unlock an original design brief.
Read the top 100 voters and most-supported authors for a public game without an API key. Only confirmed GALA contributions count. Self-support is excluded from community support, and recommendations remain readable in full.
curl 'https://galaphoenixlabs.com/api/phoenix/leaderboard?game=walking-dead'
Authorization: Bearer YOUR_API_KEY Content-Type: application/json
curl -X POST https://galaphoenixlabs.com/api/v1/projects \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
--data '{
"id": "example-comeback",
"name": "Example Comeback",
"stage": "grave",
"genre": "Cooperative adventure",
"description": "A community-proposed comeback project.",
"known": "Describe the evidence and distinguish facts from plans.",
"sources": [{"label": "Studio announcement", "url": "https://example.com/announcement"}],
"metrics": [{"label": "Historical players", "value": "Source required", "asOf": "2026-11-13", "sourceUrl": "https://example.com/data"}],
"prototypes": [{"label": "Playable prototype", "url": "https://example.com/prototype"}],
"developmentUpdates": [{"title": "Exploration", "description": "A concept is being evaluated.", "date": "2026-11-13"}]
}'curl -X DELETE https://galaphoenixlabs.com/api/v1/projects/example-comeback \ -H 'Authorization: Bearer YOUR_API_KEY'
DELETE removes your project from the public catalog, game page, social previews, and feed, and disables new burns. Only the key that created it can delete it. Unsigned prepared burn requests are cancelled; submitted transactions and historical burns, votes, recommendations, discussions, terms records, and referral payments are retained.
A successful deletion returns 200 with {"deleted":true,"id":"example-comeback","deletedAt":1794850000000,"historyPreserved":true}. Repeating DELETE with the same key returns 200. Deleted records no longer appear in API lists; GET and PATCH return 404. The ID stays reserved, so it cannot be reused. Built-in projects cannot be deleted through the contributor API.
Add prototypes: [{"label":"Playable prototype v1","url":"https://example.com/play"}] when creating or updating your project. New links on published projects appear prominently in the game details and create a community feed announcement automatically. Sending the same link again does not create another announcement. Hidden projects stay out of the public feed until published.
Creation requires id, name, and description. IDs are lowercase slugs of 2–64 characters and cannot use built-in project IDs. Stage is grave, lab, risen, or wishlist; it defaults to grave. Set stage: "wishlist" for games or NFT collections the community wants brought to Gala. Set projectType to game (default) or nft-collection. NFT projects can use sources for official collection or marketplace links and metrics for sourced collection data. Optional fields are logo, genre, known, launch, ended, history, status, artworkUrl, sources, prototypes, metrics, and developmentUpdates. Links must use HTTPS.
PATCH accepts only changed fields. Project IDs cannot change. Keys cannot edit another key’s projects or alter publication, burn settings, balances, votes, terms records, or referral credits. A key can be revoked immediately by the owner.
{
"id": "example-collection-gala",
"name": "Example Collection on Gala",
"stage": "wishlist",
"projectType": "nft-collection",
"description": "A community request for a game featuring this NFT collection.",
"status": "Community request · Not announced",
"sources": [{"label": "Official collection", "url": "https://example.com/collection"}]
}Use POST to create and PATCH to update these records with your existing contributor key. A Wishlist listing represents community interest, not an announced partnership, license, bridge, or development commitment. Real burns remain disabled until an admin enables them.
Requests are limited to 16 KB and 60 per minute per key, with a shared site request limit. Responses use JSON. Create returns 201; validation errors return 400, invalid/revoked keys 401, another contributor’s project 403, missing projects 404, duplicate IDs 409, oversized input 413, and rate limits 429.
OpenAPI specification ↗