egdata API
Endpoint histories

legacy getSandboxBaseGame

History for GET /sandboxes/{sandboxId}/base-game

GET /sandboxes/{sandboxId}/base-game — active. Recorded dates are not deployment dates.

2026-11-13 — Fix container startup after Aikido removal

Record: fix-container-startup; corrects remove-aikido-runtime.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; fixed; compatible)
    • Before: After removal of the Aikido dependency, both Docker image startup commands still preloaded @aikidosec/firewall/instrument. Containers exited with MODULE_NOT_FOUND before listening, causing origin-backed requests to fail with gateway errors.
    • After: Both Docker images start Node directly with source maps and dist/index.js, restoring origin availability without the removed preload. Existing route contracts, authentication, origin access controls, gateway quotas and custom anti-abuse behavior are preserved. Responses handled entirely at the gateway are unaffected.
    • Client action: Retry requests that failed during the outage. No request format or authentication changes are required.

Verification: Dockerfile; Dockerfile-Google; package.json; pnpm release:check --base 8ef79d0; Live GET https://api.egdata.app/health returned 200 with healthy Redis and MongoDB after correcting the service startup arguments.; Live GET https://api.egdata.app/countries returned 200 after correcting the service startup arguments..

2026-11-13 — Enforce Free/Pro/Scale paid plans, server entitlements, period budgets, and Stripe billing

Record: paid-plans-and-billing.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; compatible)
    • Before: Gateway admission enforced project minute RPM (120 Free, 1,200 Pro, 6,000 Enterprise) and a shared 100,000/month Free calendar-month quota without server-side plan entitlements or paid billing periods. Unauthenticated requests carrying a configured Origin header bypassed API-key enforcement, while keys holding the catalog:read scope bypassed granular scope restrictions. In the rate limiter, ordinary requests could reset active-minute counters for unrelated expensive policies, and origin middleware did not recognize a scale tier.
    • After: Commercial plans now define Free (60 RPM when commercial limits are enabled, 100,000 requests per UTC month account-shared), Pro (200 RPM, 300,000 requests per billing period), and Scale (600 RPM, 1,000,000 requests per billing period), while preserving explicit manual and enterprise grants. Entitlements are evaluated server-side before edge-cache reads or quota admission (403 PLAN_ENTITLEMENT_REQUIRED), 5xx upstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass and catalog:read wildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests.
    • Client action: Authenticate with an API key on a plan carrying the required entitlement and handle HTTP 403 (PLAN_ENTITLEMENT_REQUIRED) and HTTP 429 (PERIOD_QUOTA_EXCEEDED / EXPENSIVE_BUDGET_EXCEEDED) with Retry-After.

Verification: dashboard/tests/paid-plans-quota.test.ts; dashboard/tests/billing-stripe.test.ts; dashboard/tests/monthly-quota.test.ts; dashboard/tests/edge-cache.test.ts; dashboard/tests/admin-management.test.ts; dashboard/tests/legacy-analytics.test.ts; tests/middleware-origin-auth.test.ts; src/openapi/project-quota.ts; src/openapi/v1.ts; pnpm dashboard:test; pnpm test:unit; pnpm openapi:check; pnpm docs:check; pnpm release:check --base main.

2026-11-12 — Add verified-email onboarding, immutable receipts, privacy operations, and authoritative account closure

Record: developer-onboarding-account-closure.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; security; breaking)
    • Before: The portal had no self-service account closure or verified-email/terms onboarding. Cached key identity could be used without a fresh account-closure lookup, and active console sessions did not check onboarding.
    • After: Initial publication gates dashboard and console access on verified email followed by explicit terms acceptance. Existing external API keys keep working even after an incomplete dashboard visit. Account closure deletes active credentials and rejects warm/delayed key caches through a primary lookup before quota/cache/upstream access (401 INVALID_API_KEY). Credential/account lookup failure returns uncacheable 503 ACCOUNT_STATUS_UNAVAILABLE with Retry-After: 30; HEAD has no body. Public and configured anonymous bypasses retain their prior behavior. Already-admitted requests may finish; acceptance does not restore revoked keys or reset quotas.
    • Client action: Existing API-key integrations need no onboarding change for this initial rollout. Dashboard/console users must verify a notification email and accept published terms; closure permanently ends their credentials. Retry ACCOUNT_STATUS_UNAVAILABLE after Retry-After; do not automatically retry agreement-related 403 responses.

Verification: dashboard/tests/privacy-operations.test.ts; dashboard/tests/developer-mail-events.test.ts; dashboard/tests/analytics.test.ts; dashboard/tests/legacy-analytics.test.ts; dashboard/legal/operations.md; dashboard/tests/developer-account.test.ts; dashboard/tests/legal-publication.test.ts; openapi/egdata.dashboard.openapi.json; src/openapi/project-quota.ts; src/openapi/v1.ts; apps/docs/content/docs/api-console.mdx; pnpm dashboard:test; pnpm dashboard:build; pnpm docs:check.

2026-11-12 — Enforce shared 100,000 requests/month allowance across free account projects

Record: free-account-monthly-quota.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; breaking)
    • Before: Free projects were governed only by the 120 requests/minute per-project quota and expensive v1 per-operation limits without a monthly account cap, and RateLimit-Policy headers assumed 60-second windows.
    • After: Free accounts share an authoritative 100,000 requests/month allowance across all free projects, API keys, and console sessions across legacy and v1 gateways, resetting on the 1st of each calendar month at 00:00 UTC alongside existing per-project minute and expensive-operation limits. Paid projects (pro, enterprise) are exempt, while custom RPM overrides on free projects retain the monthly cap. Key rotation/deletion and project recreation never reset account usage. Monthly exhaustion returns 429 MONTHLY_QUOTA_EXCEEDED with Retry-After until reset and calendar-aware RateLimit headers; unavailable accounting returns 503 QUOTA_UNAVAILABLE.
    • Client action: Track free-account monthly usage in the developer portal or via RateLimit headers, respect Retry-After until 00:00 UTC on the 1st of next month on 429 MONTHLY_QUOTA_EXCEEDED, or request a Pro/Enterprise tier upgrade in Rate Limits.

Verification: dashboard/tests/monthly-quota.test.ts: simultaneous cap enforcement across keys/projects/console/gateways, calendar and leap-year rollovers, cache hits and upstream 5xx counting, auth/permission/public bypass exclusions, recreation/RPM/tier persistence, dashboard /quota thresholds (80%, 95%, exhausted), and 503 QUOTA_UNAVAILABLE fail-closed handling; dashboard/tests/project-quota.test.ts and dashboard/tests/rate-limiter.test.ts: atomic project minute and expensive-operation admission alongside account monthly policies; src/openapi/project-quota.ts, src/openapi/v1.ts, apps/docs/content/docs/versioned-api.mdx, and dashboard/src/lib/docs/problems.ts; pnpm openapi:generate; pnpm changelog:generate; pnpm docs:check.

2026-11-12 — Share gateway quotas across project keys and restrict project creation

Record: project-shared-quotas.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; breaking)
    • Before: Authenticated legacy gateway requests used independent per-key, per-Cloudflare-location tier counters, separate from v1 and console quotas; approved custom RPM did not govern this limiter. Accounts could create up to ten projects with a non-atomic check.
    • After: All API keys and console sessions in a project share one exact UTC-aligned 60-second global quota across authenticated legacy/v1 gateway traffic, using project tier/custom RPM. Expensive v1 caps are shared per project. Cache hits count; quota exhaustion returns 429 and unavailable admission returns retryable 503 QUOTA_UNAVAILABLE. Legacy responses expose project RateLimit headers. Accounts include one project unless an operator approves more; atomic creation enforces a 24-hour cooldown that survives deletion. Existing projects and keys remain usable.
    • Client action: Keep existing keys; coordinate request budgets across the project's keys, console and API versions. Respect Retry-After and request a project limit increase if necessary. Contact the egdata team for additional projects; creating or rotating keys no longer adds capacity. See docs/project-quota-rollout.md for migration and existing-grant review.

Verification: dashboard/tests/project-quota.test.ts: shared legacy/v1 and console quotas, key rotation, project isolation, expensive policies, UTC reset and fail-closed admission; dashboard/tests/project-policy.test.ts: concurrent creation, login races, deletion cooldown, existing projects and grants, operator allowances and HTTP policy errors; dashboard/tests/usage-outbox.test.ts: shared project counters retain distinct admitted per-key usage events; dashboard/tests/edge-cache.test.ts: quota admission remains before authenticated cache hits and revalidation; src/openapi/project-quota.ts and src/openapi/v1.ts; pnpm openapi:generate; pnpm docs:check.

2026-11-12 — Remove Aikido origin runtime blocking and telemetry

Record: remove-aikido-runtime.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; security; compatible)
    • Before: Requests reaching the Node origin passed globally installed Aikido runtime instrumentation and middleware, which could send request/security telemetry and impose Aikido-specific blocking or rate-limit grouping before the route handler.
    • After: The updated origin no longer loads the Aikido SDK, sends its runtime telemetry, creates its IP/UA-derived user identity, or applies its blocking/grouping. Existing authentication, origin access controls, gateway quotas, legacy rate limits and custom legacy anti-abuse remain. Gateway-local responses that never reach the origin retain their prior behavior. v1 remains outside custom legacy challenges. Historical provider data is not erased by this code change; origin deployment is required.
    • Client action: None. Continue honoring existing authentication, quotas and Retry-After responses. This record does not confirm production deployment.

Verification: src/index.ts; src/middlewares/rate-limit.ts; package.json; scripts/dev.mjs; tests/middleware-rate-limit.test.ts; tests/anti-abuse.test.ts; tests/v1-router.test.ts; src/openapi/index.ts; src/openapi/v1.ts; apps/docs/content/docs/regions-pagination-errors.mdx; pnpm test; pnpm build; pnpm docs:check.

2026-11-12 — Expose API gateway hostname and harden Worker edge caching

Record: worker-edge-cache.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; compatible)
    • Before: The API gateway Worker was not bound to api.egdata.app; legacy responses forwarded through the Worker passed origin CORS and freshness headers through unchanged, and no Worker edge cache served these responses.
    • After: The Worker is now bound to api.egdata.app for legacy gateway requests. Forwarded responses set caller-specific CORS headers and eligible GET/HEAD responses may be served from the post-authentication Worker edge cache with a route-specific public max-age instead of the origin CDN-Cache-Control header. Authentication, permissions, quota admission, response bodies, status codes, and error contracts are unchanged.
    • Client action: None

Verification: dashboard/tests/edge-cache.test.ts; dashboard/tests/gateway.test.ts; dashboard/tests/v1-gateway.test.ts.

2026-11-11 — Keep API startup available while v1 indexes are provisioned separately

Record: keep-api-startup-independent-of-v1-indexes.

  • legacy GET /sandboxes/{sandboxId}/base-game (getSandboxBaseGame; fixed; compatible)
    • Before: GET /sandboxes/{sandboxId}/base-game was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
    • After: GET /sandboxes/{sandboxId}/base-game becomes available after the existing database and catalog initialization, without waiting for v1 index provisioning. Its route, authentication, response format and limits are preserved.
    • Client action: None

Verification: tests/server-startup.test.ts: stalled v1 index builds do not delay HTTP startup; database connectivity remains required; pnpm test; pnpm build; pnpm docs:check; pnpm release:check --base origin/main.

On this page