egdata API
Endpoint histories

legacy legacyGet_open_api_json_d5453718

History for GET /open-api.json

GET /open-api.json — 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 /open-api.json (legacyGet_open_api_json_d5453718; 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 — Remove Aikido origin runtime blocking and telemetry

Record: remove-aikido-runtime.

  • legacy GET /open-api.json (legacyGet_open_api_json_d5453718; 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 /open-api.json (legacyGet_open_api_json_d5453718; 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 /open-api.json (legacyGet_open_api_json_d5453718; fixed; compatible)
    • Before: GET /open-api.json was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
    • After: GET /open-api.json 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