v1 getHealth
History for GET /v1/health
GET /v1/health — active. Recorded dates are not deployment dates.
2026-11-13 — Fix container startup after Aikido removal
Record: fix-container-startup; corrects remove-aikido-runtime.
- v1 GET /v1/health (getHealth; 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-12 — Report email verification before terms acceptance in dashboard and console onboarding
Record: developer-onboarding-error-order.
- v1 GET /v1/health (getHealth; fixed; compatible)
- Before: During an active rollout, signed-in dashboard console requests with unverified email and no terms acceptance returned 403 AGREEMENT_REQUIRED. Dashboard gates also advertised terms before verification.
- After: Dashboard console requests return 403 EMAIL_VERIFICATION_REQUIRED until email is verified, then 403 AGREEMENT_REQUIRED until the current terms edition is accepted. Dashboard gates list required terms only after verification. Public API-key access, anonymous access, eligibility, quotas and successful responses are unchanged.
- Client action: Console clients should handle EMAIL_VERIFICATION_REQUIRED by verifying the notification email first, then handle AGREEMENT_REQUIRED by accepting the current terms. Existing application API-key integrations require no change.
Verification: dashboard/tests/developer-account.test.ts; dashboard/tests/console-sessions.test.ts; openapi/egdata.dashboard.openapi.json; src/openapi/v1.ts; apps/docs/content/docs/api-console.mdx; pnpm docs:check; pnpm release:check --base origin/main.
2026-11-12 — Remove Aikido origin runtime blocking and telemetry
Record: remove-aikido-runtime.
- v1 GET /v1/health (getHealth; 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.
- v1 GET /v1/health (getHealth; fixed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app; additionally, eligible GET/HEAD requests used an edge-cache key that sorted repeated query values, allowing opposite value orders to share a cached representation. - After: The Worker is now bound to
api.egdata.appfor v1 requests. Eligible GET/HEAD cache keys sort query parameter names while preserving the original order of values with the same name, preserving origin query semantics. Protected requests still pass authentication, permissions, and quota admission before cache access; response contracts and outgoing private/no-store headers are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
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.
- v1 GET /v1/health (getHealth; fixed; compatible)
- Before: GET /v1/health was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/health 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.
2026-11-11 — Preserve public v1 metadata responses through the Worker
Record: public-v1-metadata-response.
- v1 GET /v1/health (getHealth; fixed; compatible)
- Before: The Worker could throw while modifying immutable upstream response headers, returning HTTP 500 instead of forwarding the health response.
- After: The Worker clones the response before applying its existing headers, preserving the upstream health status and streaming body. Public authentication and quota behavior are unchanged.
- Client action: None
Verification: dashboard/tests/v1-gateway.test.ts; pnpm dashboard:test; pnpm openapi:check.
2026-11-11 — Add the versioned v1 API with explicit scopes and per-key quotas
Record: versioned-v1-api.
- v1 GET /v1/health (getHealth; added; compatible)
- Before: GET /v1/health was not available in the versioned API.
- After: Service health. Reports Redis and MongoDB connectivity. This endpoint is public and does not require an API key. Response media: application/json. Public metadata operation; no API key required.
- Client action: None
Verification: tests/v1-router.test.ts; tests/v1-operations.test.ts; tests/v1-origin-provenance.test.ts; tests/middleware-origin-auth.test.ts; dashboard/tests/v1-gateway.test.ts; dashboard/tests/rate-limiter.test.ts; pnpm openapi:check.