Endpoint histories
Dated API behavior changes, independent of deployment.
2026-11-20 — Split search facets into a dedicated endpoint, default search facets to none, and add an opt-in card offer projection
Record: search-facets-and-card-projection.
- v1 GET /v1/search (searchOffers; changed; breaking)
- Before:
facetsdefaulted tofull, so every response embedded offer type, technology, tag, developer, publisher, and seller aggregations plus price statistics inmeta.facets, even when the client did not render filters. Offers always returned the complete documented offer document. - After:
facetsdefaults tonone, someta.facetsis{}unless the client passesfacets=fullorfacets=minimal. Adds optionalfields=card, which returns only the audited fields rendered by egdata.app offer cards (id,namespace,title,offerType,keyImages,seller,tags,developerDisplayName,publisherDisplayName,prePurchase,releaseDate,price, and locale metadata);fields=fullremains the default and keeps the complete offer document. - Client action: Clients that read
meta.facetsmust passfacets=full(orminimal) or load sections fromGET /v1/search/facets. Clients that only render offers need no change.
- Before:
- v1 GET /v1/search/facets (searchOfferFacets; added; compatible)
- Before: No dedicated facet endpoint existed; aggregations were only available alongside a page of offer hits from
GET /v1/search. - After: New
GET /v1/search/facetsaccepts the same filters asGET /v1/searchwithout pagination plus a comma-separatedfacetssection list (offerType,tags,technologies,developer,publisher,seller,price, orall; defaultall). It executes an OpenSearch aggregation query withsize: 0andtrack_total_hits: false, returns the requested aggregation body asdata, and returnsmeta.sectionsplusmeta.result. Thepricesection returnspriceStatswithcount,min,max,avg, andsum. Invalid sections, pagination parameters, inverted price ranges, and unsupported sorts return400. - Client action: Call once per filter section (for example
facets=tags) when the section is opened instead of requesting all facets with the result list.
- Before: No dedicated facet endpoint existed; aggregations were only available alongside a page of offer hits from
- v1 POST /v1/search (searchOffersRedirect; changed; compatible)
- Before: Validated the JSON filter object and redirected to the equivalent
GET /v1/searchURL without a fields projection option. - After: Accepts an optional
fieldsvalue (fullorcard), rejects other values with400 INVALID_BODY, and forwards the value in theLocationquery string. - Client action: None
- Before: Validated the JSON filter object and redirected to the equivalent
- legacy GET /search/v2/search (searchOffersV2Get; changed; breaking)
- Before:
facetsdefaulted tofull; responses embeddedofferType,technologies,price_stats, and full-mode tag, developer, publisher, and seller aggregations. - After:
facetsdefaults tonone; theaggregationsrequest is omitted and the responseaggregationsobject is empty unless the client passesfacets=fullorfacets=minimal. All other legacy v2 behavior is unchanged. - Client action: Pass
facets=fullorfacets=minimalto restore aggregations.
- Before:
- legacy POST /search/v2/search (searchOffersV2; changed; breaking)
- Before: Omitted
facetsdefaulted tofull; the redirected GET and its response included all full-mode aggregations. - After: Omitted
facetsdefaults tonone; the redirected GET omits theaggregationsrequest and the responseaggregationsobject is empty unlessfacets=fullorfacets=minimalis supplied. All other legacy v2 behavior is unchanged. - Client action: Send
facets=fullorfacets=minimalto restore aggregations.
- Before: Omitted
- legacy GET /search/{id} (getSavedSearchQuery; changed; compatible)
- Before: Returned a stored search response from the
search:v2:*cache payload. - After: Unchanged. The shared
src/routes/search.tsmodule gained the v1 facets handler and the v2 facet default, but this handler, its cache key format, and its serialization are untouched. - Client action: None
- Before: Returned a stored search response from the
- legacy POST /search (searchOffersLegacy; changed; compatible)
- Before: Returned
410 Gonewith codeDEPRECATEDand directed clients to/search/v2/search. - After: Unchanged. The shared
src/routes/search.tsmodule gained the v1 facets handler and the v2 facet default; this deprecated handler still returns the same410 Goneresponse. - Client action: None
- Before: Returned
- legacy GET / (legacyGet__c767025d; changed; compatible)
- Before: The root endpoint inventory listed
GET /v1/searchand the other mounted v1 routes but not/v1/search/facets. - After: The root endpoint inventory includes
GET /v1/search/facets, matching the mounted route in both origins. - Client action: None
- Before: The root endpoint inventory listed
Verification: tests/search-route.test.ts; tests/rust-search-oracle.test.ts; cargo test -p egdata-routes-v1 search::; cargo test -p egdata-routes-legacy; cargo test -p egdata-openapi; pnpm openapi:check; pnpm docs:check.
2026-11-19 — Add profile games completion filter and offer expiryDate to v1 responses
Record: v1-profile-filters-and-offer-expiry.
- v1 GET /v1/profiles/{id}/games (listProfileGames; changed; compatible)
- Before: Supported
sortand booleanplatinumfiltering onGET /v1/profiles/{id}/games. - After: Adds optional
filterquery parameter (all,completed,near-platinum,in-progress,platinum; defaultall) with cursor bindings, cache keys, and total counts scoped by the effective filter while preservingplatinum=truebackward compatibility. - Client action: None
- Before: Supported
- v1 GET /v1/autocomplete (autocomplete; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/base-game/{namespace} (getBaseGame; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/collections/{slug} (getCollection; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/featured (getFeaturedGames; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/franchises/{slug} (getFranchise; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/game-awards (getGameAwards; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/items/{id}/offer (getItemOffer; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/latest-games (getLatestGames; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id} (getOffer; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/collection (getOfferCollection; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/events/{id} (getOfferEvent; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/overview (getOfferOverview; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/related (getRelatedOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/search/{id} (getSearchQuery; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/active-sales (listActiveSales; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/free-games (listFreeGames; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/free-games/history (listFreeGamesHistory; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/latest-released (listLatestReleased; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/genres (listOfferGenres; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers (listOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/promotions/{id} (listPromotionOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/sales (listSales; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/sellers/{id} (listSellerOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/top-sellers (listTopSellers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/offers/upcoming (listUpcomingOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/multisearch/offers (multisearchOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 POST /v1/search/natural-language (naturalLanguageSearch; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/free-games/search (searchFreeGames; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/search (searchOffers; changed; compatible)
- Before: Serialized
/v1Offer objects omittedexpiryDate. - After: Serialized
/v1Offer objects includeexpiryDateformatted as a UTC ISO 8601 timestamp ornull. - Client action: None
- Before: Serialized
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; changed; compatible)
- Before: Offer documents serialized via generic value normalization left
expiryDateunnormalized. - After:
expiryDateis included inDATE_FIELDSand normalized to a UTC ISO 8601 timestamp when present on returned offer payloads. - Client action: None
- Before: Offer documents serialized via generic value normalization left
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; changed; compatible)
- Before: Offer documents serialized via generic value normalization left
expiryDateunnormalized. - After:
expiryDateis included inDATE_FIELDSand normalized to a UTC ISO 8601 timestamp when present on returned offer payloads. - Client action: None
- Before: Offer documents serialized via generic value normalization left
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; changed; compatible)
- Before: Offer documents serialized via generic value normalization left
expiryDateunnormalized. - After:
expiryDateis included inDATE_FIELDSand normalized to a UTC ISO 8601 timestamp when present on returned offer payloads. - Client action: None
- Before: Offer documents serialized via generic value normalization left
Verification: pnpm openapi:check; pnpm test; cargo test -p egdata-core -p egdata-infra -p egdata-graphql -p egdata-diff --locked; cargo clippy --locked --workspace --all-targets -- -D warnings.
2026-11-18 — Persist owner review changes and include newly saved reviews in public counts
Record: persist-owner-review-edits.
- legacy GET /offers/{id}/reviews (listOfferReviews; fixed; compatible)
- Before: The legacy editor could fail to persist an owner's changes, leaving the earlier text and rating in subsequent review lists. The review form could also fail to locate a valid product after the origin started.
- After: After a successful edit and cache refresh, the list reflects the owner's saved review. Each edit keeps the review's identity and appends the prior version to its history. New reviews for resolved products appear after the same cache refresh.
- Client action: None
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; fixed; compatible)
- Before: The legacy editor sent an invalid MongoDB update, so an attempted rating or recommendation change could leave the original values in the summary. The review form could also fail to locate a valid product after the origin started.
- After: After a successful owner edit and cache refresh, the summary uses the saved rating, recommendation and verification status. Editing a review keeps the review count for the offer. New reviews for resolved products appear after the same cache refresh.
- Client action: None
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; fixed; compatible)
- Before: The legacy editor could fail to persist an owner's changes, leaving the earlier text and rating in subsequent review lists. The review form could also fail to locate a valid product after the origin started.
- After: After a successful edit and cache refresh, the list reflects the owner's saved review. Each edit keeps the review's identity and appends the prior version to its history. New reviews for resolved products appear after the same cache refresh.
- Client action: None
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; fixed; compatible)
- Before: The legacy editor sent an invalid MongoDB update, so an attempted rating or recommendation change could leave the original values in the summary. The review form could also fail to locate a valid product after the origin started.
- After: After a successful owner edit and cache refresh, the summary uses the saved rating, recommendation and verification status. Editing a review keeps the review count for the offer. New reviews for resolved products appear after the same cache refresh.
- Client action: None
- legacy GET /graphql (legacyGet_graphql_220e6fb1; fixed; compatible)
- Before: A review submitted for a valid product could fail before insertion, leaving the owner's review count unchanged.
- After: A successfully created review contributes to its owner's count after the profile cache refreshes. Editing an existing review preserves that count.
- Client action: None
- Schema fields: Profile.reviewsCount, ProfileHighlights.reviewsCount
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; fixed; compatible)
- Before: A review submitted for a valid product could fail before insertion, leaving the owner's review count unchanged.
- After: A successfully created review contributes to its owner's count after the profile cache refreshes. Editing an existing review preserves that count.
- Client action: None
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; fixed; compatible)
- Before: A review submitted for a valid product could fail before insertion, leaving the owner's review count unchanged.
- After: A successfully created review contributes to its owner's count after the profile cache refreshes. Editing an existing review preserves that count.
- Client action: None
- legacy POST /graphql (legacyPost_graphql_fac042a8; fixed; compatible)
- Before: A review submitted for a valid product could fail before insertion, leaving the owner's review count unchanged.
- After: A successfully created review contributes to its owner's count after the profile cache refreshes. Editing an existing review preserves that count.
- Client action: None
- Schema fields: Profile.reviewsCount, ProfileHighlights.reviewsCount
- v1 GET /v1/profiles/{id} (getProfile; fixed; compatible)
- Before: A review submitted for a valid product could fail before insertion, leaving the owner's review count unchanged.
- After: A successfully created review contributes to its owner's count after the profile cache refreshes. Editing an existing review preserves that count.
- Client action: None
- v1 GET /v1/profiles/{id}/information (getProfileInformation; fixed; compatible)
- Before: A review submitted for a valid product could fail before insertion, leaving the owner's review count unchanged.
- After: A successfully created review contributes to its owner's count after the profile cache refreshes. Editing an existing review preserves that count.
- Client action: None
Verification: tests/rust-legacy-account-admin-oracle.test.ts compares authenticated review edits, edition history, concurrent writes and deletion during an edit.; rust/scripts/compare-origins.mjs exercises signed-in owners against the Node and Rust HTTP origins and checks the stored review in MongoDB..
2026-11-16 — Accept dashboard console session key identities on v1 endpoints
Record: console-session-v1-key-context.
- v1 GET /v1/autocomplete (autocomplete; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/offers/exists (checkOfferExistence; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/offers/slugs (checkOfferSlugs; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/assets/{id} (getAsset; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/base-game/{namespace} (getBaseGame; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds/{id} (getBuild; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds/{id}/history (getBuildHistory; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds/{id}/tree (getBuildTree; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/changelist/{id} (getChangelogEntry; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/collections/{slug} (getCollection; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/featured (getFeaturedGames; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/franchises/{slug} (getFranchise; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/free-games/og (getFreeGamesOg; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/free-games/stats (getFreeGamesStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/game-awards (getGameAwards; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/game-awards/og (getGameAwardsOg; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/stats/homepage (getHomepageStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items/{id} (getItem; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items/{id}/assets (getItemAssets; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items/{id}/builds (getItemBuilds; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items/{id}/changelog (getItemChangelog; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items/{id}/offer (getItemOffer; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/items/bulk (getItemsBulk; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/latest-games (getLatestGames; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id} (getOffer; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/assets (getOfferAssets; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/collection (getOfferCollection; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/events/{id} (getOfferEvent; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/features (getOfferFeatures; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/genres (getOfferGenres; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/items (getOfferItems; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/media (getOfferMedia; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/og (getOfferOg; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/overview (getOfferOverview; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/polls (getOfferPolls; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/price (getOfferPrice; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/tops (getOfferTops; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id} (getProfile; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/information (getProfileInformation; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/region (getRegion; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/related (getRelatedOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/robots.txt (getRobots; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search/{id} (getSearchQuery; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search/{id}/count (getSearchQueryCount; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sellers/{id}/stats (getSellerStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sitemap.xml (getSitemap; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/stats (getStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/catalog/hydrate (hydrateCatalog; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/active-sales (listActiveSales; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds/{id}/files (listBuildFiles; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds/{id}/items (listBuildItems; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/builds (listBuilds; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/changelist (listChangelist; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/changelog (listChangelog; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/countries (listCountries; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/free-games/sellers (listFreeGameSellers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/free-games (listFreeGames; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/free-games/history (listFreeGamesHistory; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items (listItems; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/latest-released (listLatestReleased; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/free-games/mobile (listMobileFreeGames; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/events (listOfferEvents; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/genres (listOfferGenres; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers (listOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/games (listProfileGames; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/promotions/{id} (listPromotionOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/promotions (listPromotions; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/regions (listRegions; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sales (listSales; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sandboxes (listSandboxes; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search/developers (listSearchDevelopers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search/offer-types (listSearchOfferTypes; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search/publishers (listSearchPublishers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search/tags (listSearchTags; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sellers/{id} (listSellerOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/sellers (listSellers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/tags (listTags; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/top-sellers (listTopSellers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/offers/upcoming (listUpcomingOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/multisearch/items (multisearchItems; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/multisearch/offers (multisearchOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/multisearch/sellers (multisearchSellers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/search/natural-language (naturalLanguageSearch; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search/changelog (searchChangelog; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/free-games/search (searchFreeGames; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 GET /v1/search (searchOffers; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
- v1 POST /v1/search (searchOffersRedirect; fixed; compatible)
- Before: Requests authenticated via an ephemeral dashboard console session sent a console_<projectId> key identity that the v1 origin rejected with HTTP 401 MISSING_KEY_CONTEXT.
- After: The v1 origin accepts verified gateway console_<projectId> identities alongside key_<id> identities, allowing authenticated dashboard Try It console requests to succeed with the same project permissions and quotas.
- Client action: None
Verification: tests/v1-origin-provenance.test.ts; tests/v1-router.test.ts; dashboard/tests/console-sessions.test.ts.
2026-11-16 — Add total count to v1 pagination metadata while preserving forward-only signed cursors
Record: v1-pagination-total-count.
- v1 GET /v1/builds (listBuilds; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/builds/{id}/history (getBuildHistory; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/builds/{id}/files (listBuildFiles; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/builds/{id}/tree (getBuildTree; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/builds/{id}/items (listBuildItems; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sales (listSales; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/active-sales (listActiveSales; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/changelog (listChangelog; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/changelist (listChangelist; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/collections/{slug} (getCollection; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/franchises/{slug} (getFranchise; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/free-games/history (listFreeGamesHistory; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/free-games/search (searchFreeGames; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }withouttotal, and OpenSearch queries skipped or capped hit counting. - After:
meta.paginationincludestotal(exact integer count when available, ornull) withtrack_total_hits: true, while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/items (listItems; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/items/{id}/changelog (getItemChangelog; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/multisearch/offers (multisearchOffers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }withouttotal, and OpenSearch queries skipped or capped hit counting. - After:
meta.paginationincludestotal(exact integer count when available, ornull) withtrack_total_hits: true, while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/multisearch/items (multisearchItems; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }withouttotal, and OpenSearch queries skipped or capped hit counting. - After:
meta.paginationincludestotal(exact integer count when available, ornull) withtrack_total_hits: true, while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers (listOffers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/events/{id} (getOfferEvent; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/upcoming (listUpcomingOffers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/top-sellers (listTopSellers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/offers/latest-released (listLatestReleased; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/profiles/{id}/games (listProfileGames; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/promotions/{id} (listPromotionOffers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sandboxes (listSandboxes; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/search (searchOffers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }withouttotal, and OpenSearch queries skipped or capped hit counting. - After:
meta.paginationincludestotal(exact integer count when available, ornull) withtrack_total_hits: true, while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/search/changelog (searchChangelog; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }withouttotal, and OpenSearch queries skipped or capped hit counting. - After:
meta.paginationincludestotal(exact integer count when available, ornull) withtrack_total_hits: true, while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
- v1 GET /v1/sellers/{id} (listSellerOffers; changed; compatible)
- Before:
meta.paginationonly returned{ limit, hasMore, nextCursor }without a total matching item count. - After:
meta.paginationincludestotal(matching item count cached independently oflimitandcursor, ornullif unavailable), while preserving forward-only HMAC-signed cursor pagination (pageandoffsetremain rejected with 400). - Client action: None
- Before:
Verification: tests/v1-pagination.test.ts; tests/v1-offers-list.test.ts; tests/v1-pagination-totals.test.ts; tests/v1-router.test.ts; pnpm openapi:check.
2026-11-13 — Cache anonymous country, tag and genre reads at the edge
Record: anonymous-catalog-edge-cache.
- legacy GET /countries (listCountries; changed; compatible)
- Before: Anonymous country reads always forwarded upstream, despite an existing 24-hour CDN freshness policy.
- After: After the existing anonymous-access decision, eligible GET/HEAD requests use the Worker cache with the origin's 24-hour CDN TTL. Hits avoid the origin and its per-request checks. Query strings and Origin variants remain distinct, browser/CDN freshness and CORS headers are preserved, and cookies, user authorization, session tokens and ranges bypass caching. Only shareable successful responses are stored; API-key access checks and response schemas are unchanged. Requires Worker deployment.
- Client action: None
- legacy GET /tags (legacyGet_tags_803dea8c; changed; compatible)
- Before: Anonymous tag reads always forwarded upstream, despite an existing one-hour CDN freshness policy.
- After: After the existing anonymous-access decision, eligible GET/HEAD requests use the Worker cache with the origin's one-hour CDN TTL. Hits avoid the origin and its per-request checks. The group filter and all other query parameters remain in the cache key, with separate Origin variants preserving CORS. Browser/CDN freshness headers are preserved; cookies, user authorization, session tokens, ranges and non-shareable responses bypass caching. API-key access checks and response schemas are unchanged. Requires Worker deployment.
- Client action: None
- legacy GET /offers/genres (listOfferGenres; changed; compatible)
- Before: Anonymous genre reads always forwarded upstream, repeating genre and localized recent-game queries despite an existing one-hour CDN freshness policy.
- After: After the existing anonymous-access decision, eligible GET/HEAD requests use the Worker cache with the origin's one-hour CDN TTL. Hits avoid the origin and its per-request checks. Locale and all other query parameters remain in the cache key, with separate Origin variants preserving CORS. Browser/CDN freshness headers are preserved; cookies, user authorization, session tokens, ranges and non-shareable responses bypass caching. API-key access checks and response schemas are unchanged. Requires Worker deployment.
- Client action: None
Verification: dashboard/tests/edge-cache.test.ts; dashboard/tests/origin-proxy.test.ts; dashboard/tests/analytics.test.ts; pnpm dashboard:typecheck; pnpm docs:check; pnpm release:check --base origin/main.
2026-11-13 — Expand anonymous edge caching and normalize discovery response freshness
Record: expanded-anonymous-edge-cache.
- legacy GET /offers/{id}/tops (getOfferTopPositions; changed; compatible)
- Before: Anonymous offer-position requests always forwarded upstream despite the five-minute CDN policy.
- After: Eligible anonymous GET/HEAD requests use the isolated public Worker cache with the existing five-minute CDN TTL. Entries retain the offer ID, full query and Origin; hits avoid origin processing, including origin rate limits and anti-abuse checks. Gateway access checks, credential/range exclusions, CORS, client freshness headers and response schemas are preserved. Requires Worker deployment.
- Client action: None
- legacy GET /offers/{id}/assets (listOfferAssets; changed; compatible)
- Before: Anonymous offer-asset requests always forwarded upstream despite the five-minute CDN policy.
- After: Eligible anonymous GET/HEAD requests use the isolated public Worker cache with the existing five-minute CDN TTL. Entries retain the offer ID, full query and Origin; hits avoid origin processing, including origin rate limits and anti-abuse checks. Gateway access checks, credential/range exclusions, CORS, client freshness headers and response schemas are preserved. Requires Worker deployment.
- Client action: None
- legacy GET /offers/{id}/price (getOfferPrice; changed; compatible)
- Before: Anonymous price requests always reached the origin, including its offer eligibility lookup before Redis, despite the five-minute CDN policy.
- After: Eligible anonymous GET/HEAD requests use the isolated public Worker cache with the existing five-minute CDN TTL. Offer ID, country and all query parameters remain in the key, partitioned by Origin. Requests carrying cookies, user authorization, session tokens or ranges bypass the cache; only shareable successful responses are stored. Hits avoid origin processing and its per-request checks. Response schemas, country validation and gateway access requirements are preserved. Requires Worker deployment.
- Client action: None
- legacy GET /offers/top-sellers (listTopSellersOffers; changed; compatible)
- Before: Anonymous top-seller requests always forwarded upstream despite the one-hour CDN policy.
- After: Eligible anonymous GET/HEAD requests use the isolated public Worker cache with the existing one-hour CDN TTL. Full query keys preserve locale, page, limit and expansion, and entries are partitioned by Origin. Hits avoid origin processing and its per-request checks. Gateway access checks, credential/range exclusions, CORS, freshness headers and response schemas are preserved. Requires Worker deployment.
- Client action: None
- legacy GET /free-games (getFreeGames; changed; compatible)
- Before: Anonymous free-game requests always forwarded upstream despite the five-minute CDN policy.
- After: Eligible anonymous GET/HEAD requests use the isolated public Worker cache with the existing five-minute CDN TTL. Full query keys preserve country, locale and expansion; entries are partitioned by Origin. Cookie-selected countries, user authorization, session tokens and ranges bypass caching. Only shareable successful responses are stored. Hits avoid origin processing and its per-request checks. Response schemas, CORS and gateway access requirements are preserved. Requires Worker deployment.
- Client action: None
- legacy GET /free-games/stats (getFreeGamesStats; changed; compatible)
- Before: Anonymous free-game statistics always forwarded upstream despite the 24-hour CDN policy.
- After: Eligible anonymous GET/HEAD requests use the isolated public Worker cache with the existing 24-hour CDN TTL. Country and all query parameters remain in the key, partitioned by Origin; cookie/session/authorization/range exclusions remain in place. Hits avoid origin processing and its per-request checks. Response schemas, CORS, client freshness headers and gateway access requirements are preserved. Requires Worker deployment.
- Client action: None
- legacy GET /search/v2/search (searchOffersV2Get; changed; compatible)
- Before: Anonymous GET searches always forwarded upstream despite the five-minute CDN policy.
- After: Eligible anonymous GET/HEAD searches use the isolated public Worker cache with the existing five-minute CDN TTL. All search, country, locale, pagination, sort and expansion query parameters remain in the key, partitioned by Origin; repeated query-value ordering is preserved. Credential/range exclusions and non-shareable response exclusions remain in place. Hits avoid origin processing and its per-request checks. Request validation, response schemas and gateway access requirements are preserved. POST redirects are unchanged. Requires Worker deployment.
- Client action: None
- legacy GET /stats/homepage (getHomepageStats; changed; compatible)
- Before: Anonymous homepage statistics always forwarded upstream. Redis hits advertised a one-hour browser TTL while freshly computed responses had no explicit cache freshness.
- After: Successful fresh and Redis-cached responses consistently advertise 60-second browser freshness and five-minute shared freshness. Responses without an explicit country now vary on Cookie, preserving EGDATA_COUNTRY selection and excluding those responses from Worker storage. Eligible anonymous GET/HEAD requests with an explicit country use the isolated public Worker cache. Full queries and Origin variants remain distinct; credentials, cookies and ranges bypass caching. Hits avoid origin processing and its per-request checks. Body schemas and country resolution are unchanged; existing country inputs and new cache headers are documented in OpenAPI. Requires origin and Worker deployment.
- Client action: None
- legacy GET /autocomplete (autocompleteOffers; changed; compatible)
- Before: Autocomplete used Redis without explicit HTTP freshness, and anonymous requests always forwarded upstream.
- After: Successful fresh and Redis-cached responses consistently advertise 60-second browser and CDN freshness. Eligible anonymous GET/HEAD requests use the isolated public Worker cache with query, locale, limit and all other query parameters retained, partitioned by Origin. Credential/range exclusions and non-shareable response exclusions remain in place. Hits avoid origin processing and its per-request checks. Request validation, response schemas, CORS and gateway access requirements are preserved. Requires origin and Worker deployment.
- Client action: None
Verification: dashboard/tests/edge-cache.test.ts; dashboard/tests/legacy-analytics.test.ts; dashboard/tests/origin-proxy.test.ts; tests/middleware-edge-cache.test.ts; tests/search-route.test.ts; tests/anti-abuse.test.ts; pnpm dashboard:typecheck; pnpm docs:check; pnpm release:check --base origin/main.
2026-11-13 — Fix container startup after Aikido removal
Record: fix-container-startup; corrects remove-aikido-runtime.
- legacy GET /autocomplete (autocompleteOffers; 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.
- legacy POST /offers/exists (checkOffersExist; 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.
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- legacy GET /search/{id}/count (countSavedSearchResults; 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.
- legacy POST /auth/challenge (createAbuseChallenge; 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.
- legacy GET /builds/{id} (getBuild; 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.
- legacy GET /builds/{id}/tree (getBuildFileTree; 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.
- legacy GET /builds/{id}/history (getBuildHistory; 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.
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; 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.
- legacy GET /changelist/{id} (getChangelistEntry; 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.
- legacy GET /free-games (getFreeGames; 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.
- legacy GET /free-games/stats (getFreeGamesStats; 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.
- legacy GET /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.
- legacy GET /stats/homepage (getHomepageStats; 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.
- legacy GET /items/{id} (getItem; 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.
- legacy GET /items/{id}/assets (getItemAssets; 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.
- legacy GET /items/{id}/builds (getItemBuilds; 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.
- legacy GET /items/{id}/changelog (getItemChangelog; 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.
- legacy GET /items/{id}/offer (getItemOffer; 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.
- legacy POST /items/bulk (getItemsBulk; 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.
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; 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.
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; 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.
- legacy GET /offers/{id} (getOffer; 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.
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; 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.
- legacy GET /offers/{id}/bundle (getOfferBundle; 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.
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; 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.
- legacy GET /offers/events/{id} (getOfferEvent; 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.
- legacy GET /offers/{id}/features (getOfferFeatures; 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.
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; 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.
- legacy GET /offers/{id}/igdb (getOfferIgdb; 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.
- legacy GET /offers/{id}/mappings (getOfferMappings; 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.
- legacy GET /offers/{id}/media (getOfferMedia; 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.
- legacy GET /offers/{id}/og (getOfferOgPng; 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.
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; 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.
- legacy GET /offers/{id}/overview (getOfferOverview; 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.
- legacy GET /offers/{id}/polls (getOfferPolls; 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.
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; 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.
- legacy GET /offers/{id}/price (getOfferPrice; 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.
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; 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.
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; 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.
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; 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.
- legacy GET /offers/{id}/ratings (getOfferRatings; 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.
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; 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.
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; 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.
- legacy GET /offers/{id}/requirements (getOfferRequirements; 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.
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- legacy POST /items/bulk/offers (getOffersForItemsBulk; 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.
- legacy GET /offers/{id}/tops (getOfferTopPositions; 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.
- legacy GET /region (getRegionForCountry; 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.
- legacy GET /sandboxes/{sandboxId} (getSandbox; 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.
- 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.
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; 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.
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- legacy GET /search/{id} (getSavedSearchQuery; 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.
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; 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.
- legacy GET /sellers/{id}/stats (getSellerStats; 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.
- legacy GET /stats (getStats; 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.
- legacy GET /stats/creations/yearly (getYearlyCreationStats; 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.
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; 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.
- legacy POST /catalog/hydrate (hydrateCatalogGraph; 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.
- legacy GET / (legacyGet__c767025d; 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.
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; 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.
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; 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.
- legacy GET /changelog (legacyGet_changelog_038722cc; 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.
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; 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.
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; 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.
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; 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.
- legacy GET /doc (legacyGet_doc_f5f543a0; 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.
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; 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.
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; 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.
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; 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.
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; 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.
- legacy GET /graphql (legacyGet_graphql_220e6fb1; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements, GenreResult.genre, GenreResult.offers, GenreOffer.id, GenreOffer.title, GenreOffer.image, OfferConnection.elements, OfferConnection.total, OfferConnection.page, OfferConnection.limit, OfferConnection.count, ItemConnection.elements, ItemConnection.total, ItemConnection.page, ItemConnection.limit, SandboxConnection.elements, SandboxConnection.total, SandboxConnection.page, SandboxConnection.limit, Profile.accountId, Profile.displayName, Profile.avatar, Profile.linkedAccounts, Profile.creationDate, Profile.reviewsCount, Profile.highlights, Profile.heroGame, Profile.featuredAchievements, Profile.featuredGames, Profile.recentActivity, Profile.games, Profile.achievements, ProfileAvatar.small, ProfileAvatar.medium, ProfileAvatar.large, ProfileHighlights.level, ProfileHighlights.totalXP, ProfileHighlights.totalGames, ProfileHighlights.totalAchievements, ProfileHighlights.totalPlatinums, ProfileHighlights.reviewsCount, ProfileHeroGame.sandboxId, ProfileHeroGame.title, ProfileHeroGame.imageUrl, ProfileHeroGame.completionPercent, ProfileGame.sandboxId, ProfileGame.title, ProfileGame.imageUrl, ProfileGame.completionPercent, ProfileGame.unlocked, ProfileGame.total, ProfileGame.earnedXP, ProfileGame.totalXP, ProfileGame.hasPlatinum, ProfileGame.rarestAchievements, ProfileAchievement.name, ProfileAchievement.displayName, ProfileAchievement.description, ProfileAchievement.iconUrl, ProfileAchievement.rarityPercent, ProfileAchievement.xp, ProfileAchievement.sandboxId, ProfileAchievement.gameTitle, ProfileAchievement.unlockedAt, ProfileActivityItem.type, ProfileActivityItem.sandboxId, ProfileActivityItem.gameTitle, ProfileActivityItem.achievementName, ProfileActivityItem.achievementIconUrl, ProfileActivityItem.occurredAt, ProfileGameConnection.elements, ProfileGameConnection.total, ProfileGameConnection.page, ProfileGameConnection.limit, ProfileAchievementConnection.elements, ProfileAchievementConnection.total, ProfileAchievementConnection.page, ProfileAchievementConnection.limit, OfferMappings.pageSlug, OfferMappings.pageType, OfferMappings._id, CustomAttribute.key, CustomAttribute.value, CustomAttribute.type, CustomAttribute._id, Tag.id, Tag.name, Tag.groupName, Seller.id, Seller.name, KeyImage.type, KeyImage.url, KeyImage.md5, Price.country, Price.region, Price.namespace, Price.offerId, Price.price, Price.appliedRules, Price.updatedAt, SinglePrice.currencyCode, SinglePrice.discount, SinglePrice.discountPrice, SinglePrice.originalPrice, SinglePrice.basePayoutCurrencyCode, SinglePrice.basePayoutPrice, SinglePrice.payoutCurrencyExchangeRate, AppliedRule.id, AppliedRule.name, AppliedRule.namespace, AppliedRule.promotionStatus, AppliedRule.startDate, AppliedRule.endDate, AppliedRule.saleType, AppliedRule.regionIds, Asset._id, Asset.artifactId, Asset.downloadSizeBytes, Asset.installedSizeBytes, Asset.itemId, Asset.namespace, Asset.platform, Asset.title, Asset.updatedAt, Build._id, Build.appName, Build.labelName, Build.buildVersion, Build.hash, Build.metadata, Build.downloadSizeBytes, Build.installedSizeBytes, Build.createdAt, Build.updatedAt, Build.technologies, Build.items, Build.files, Build.installOptions, FileConnection.elements, FileConnection.total, FileConnection.page, FileConnection.limit, File.fileName, File.fileSize, File.fileHash, File.manifestHash, File.depth, File.installTags, BuildMetadata.installationPoolId, Technology.section, Technology.technology, Changelog._id, Changelog.metadata, Changelog.timestamp, Changelog.document, ChangelogMetadata.contextId, ChangelogMetadata.contextType, ChangelogMetadata.changes, ChangelogChange.changeType, ChangelogChange.field, ChangelogChange.before, ChangelogChange.after, Item._id, Item.id, Item.namespace, Item.title, Item.description, Item.keyImages, Item.categories, Item.status, Item.creationDate, Item.lastModifiedDate, Item.customAttributes, Item.entitlementName, Item.entitlementType, Item.itemType, Item.releaseInfo, Item.developer, Item.developerId, Item.eulaIds, Item.endOfSupport, Item.applicationId, Item.unsearchable, Item.requiresSecureAccount, Item.offers, Item.assets, Item.builds, Item.changelog, Item.mainOffer, ItemCategory.path, ReleaseInfo.id, ReleaseInfo.appId, ReleaseInfo.platform, Sandbox._id, Sandbox.name, Sandbox.displayName, Sandbox.namespace, Sandbox.parent, Sandbox.store, Sandbox.status, Sandbox.ageGatings, Sandbox.created, Sandbox.updated, Sandbox.items, Sandbox.offers, Sandbox.assets, Sandbox.builds, Sandbox.baseGame, Sandbox.achievements, Sandbox.stats, Sandbox.changelog, SandboxHub.id, SandboxHub.namespace, SandboxHub.title, SandboxHub.description, SandboxHub.primaryKind, SandboxHub.primaryOffer, SandboxHub.primaryItem, SandboxHub.sandbox, SandboxHub.price, SandboxHub.seller, SandboxHub.developer, SandboxHub.publisher, SandboxHub.keyImages, SandboxHub.genres, SandboxHub.platforms, SandboxHub.stats, SandboxHub.featuredOffers, SandboxHub.recentBuilds, SandboxHub.recentChanges, SandboxHub.ageRating, SandboxHub.achievements, SandboxHub.created, SandboxHub.updated, SandboxAchievementSummary.sets, SandboxAchievementSummary.total, SandboxAchievementSummary.baseTotal, SandboxAchievementSummary.xp, AssetConnection.elements, AssetConnection.total, AssetConnection.page, AssetConnection.limit, AssetConnection.count, BuildConnection.elements, BuildConnection.total, BuildConnection.page, BuildConnection.limit, BuildConnection.count, SandboxStats.offers, SandboxStats.items, SandboxStats.assets, SandboxStats.builds, SandboxStats.achievements, AchievementSet._id, AchievementSet.sandboxId, AchievementSet.isBase, AchievementSet.achievements, Achievement.id, Achievement.name, Achievement.description, Achievement.unlockedIcon, Achievement.lockedIcon, Achievement.rarity, Achievement.score, Franchise._id, Franchise.id, Franchise.name, Franchise.offers, Franchise.allOffers, Giveaway._id, Giveaway.id, Giveaway.namespace, Giveaway.startDate, Giveaway.endDate, Poll._id, Poll.options, PollOption.id, PollOption.name, PollOption.votes, Rating._id, Rating.overallScore, Rating.recommendedPercentage, Rating.totalReviews, Hltb._id, Hltb.hltbId, Hltb.name, Hltb.main, Hltb.mainExtra, Hltb.completionist, Offer._id, Offer.id, Offer.namespace, Offer.title, Offer.description, Offer.longDescription, Offer.offerType, Offer.effectiveDate, Offer.creationDate, Offer.lastModifiedDate, Offer.isCodeRedemptionOnly, Offer.productSlug, Offer.urlSlug, Offer.url, Offer.developerDisplayName, Offer.publisherDisplayName, Offer.prePurchase, Offer.releaseDate, Offer.pcReleaseDate, Offer.expiryDate, Offer.viewableDate, Offer.countriesBlacklist, Offer.countriesWhitelist, Offer.refundType, Offer.offerMappings, Offer.categories, Offer.customAttributes, Offer.items, Offer.tags, Offer.seller, Offer.keyImages, Offer.price, Offer.changelog, Offer.franchises, Offer.giveaways, Offer.related, Offer.suggestions, Offer.ratings, Offer.polls, Offer.hltb, Offer.sandbox, Offer.positions, Offer.ageRating, Offer.features, Offer.locale, Offer.localeStatus, Offer.canonicalLocale, Offer.localization, OfferLocalizationMetadata.source, OfferLocalizationMetadata.fetchedAt, OfferLocalizationMetadata.sourceUpdatedAt, OfferFeatures.launcher, OfferFeatures.features, OfferFeatures.epicFeatures, ChangelogConnection.elements, ChangelogConnection.totalCount, ChangelogConnection.totalPages, ChangelogConnection.hasNextPage, ChangelogConnection.hasPreviousPage
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; 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.
- legacy GET /items/sitemap.xml (legacyGet_items_sitemap_xml_57b8dd19; 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.
- legacy GET /items-sitemap.xml (legacyGet_items_sitemap_xml_e6f8185b; 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.
- legacy GET /multisearch (legacyGet_multisearch_229582ca; 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.
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; 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.
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; 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.
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; 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.
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; 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.
- 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.
- legacy GET /ping (legacyGet_ping_f7c2b7c6; 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.
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; 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.
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; 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.
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; 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.
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; 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.
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; 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.
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; 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.
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; 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.
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; 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.
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; 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.
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; 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.
- legacy GET /profiles/sitemap.xml (legacyGet_profiles_sitemap_xml_0e16a159; 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.
- legacy GET /promotions (legacyGet_promotions_83dd267d; 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.
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; 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.
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; 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.
- legacy GET /promotions-sitemap.xml (legacyGet_promotions_sitemap_xml_3578dc8e; 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.
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; 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.
- legacy GET /robots.txt (legacyGet_robots_txt_deae90bd; 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.
- legacy GET /sandboxes/sitemap.xml (legacyGet_sandboxes_sitemap_xml_5773ff84; 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.
- legacy GET /search (legacyGet_search_82dab022; 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.
- legacy GET /sitemap.xml (legacyGet_sitemap_xml_efe3322f; 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.
- legacy GET /tags (legacyGet_tags_803dea8c; 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.
- legacy GET /ui (legacyGet_ui_64976efd; 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.
- legacy OPTIONS /ping (legacyOptions_ping_9143aa8e; 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.
- legacy POST /graphql (legacyPost_graphql_fac042a8; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements, GenreResult.genre, GenreResult.offers, GenreOffer.id, GenreOffer.title, GenreOffer.image, OfferConnection.elements, OfferConnection.total, OfferConnection.page, OfferConnection.limit, OfferConnection.count, ItemConnection.elements, ItemConnection.total, ItemConnection.page, ItemConnection.limit, SandboxConnection.elements, SandboxConnection.total, SandboxConnection.page, SandboxConnection.limit, Profile.accountId, Profile.displayName, Profile.avatar, Profile.linkedAccounts, Profile.creationDate, Profile.reviewsCount, Profile.highlights, Profile.heroGame, Profile.featuredAchievements, Profile.featuredGames, Profile.recentActivity, Profile.games, Profile.achievements, ProfileAvatar.small, ProfileAvatar.medium, ProfileAvatar.large, ProfileHighlights.level, ProfileHighlights.totalXP, ProfileHighlights.totalGames, ProfileHighlights.totalAchievements, ProfileHighlights.totalPlatinums, ProfileHighlights.reviewsCount, ProfileHeroGame.sandboxId, ProfileHeroGame.title, ProfileHeroGame.imageUrl, ProfileHeroGame.completionPercent, ProfileGame.sandboxId, ProfileGame.title, ProfileGame.imageUrl, ProfileGame.completionPercent, ProfileGame.unlocked, ProfileGame.total, ProfileGame.earnedXP, ProfileGame.totalXP, ProfileGame.hasPlatinum, ProfileGame.rarestAchievements, ProfileAchievement.name, ProfileAchievement.displayName, ProfileAchievement.description, ProfileAchievement.iconUrl, ProfileAchievement.rarityPercent, ProfileAchievement.xp, ProfileAchievement.sandboxId, ProfileAchievement.gameTitle, ProfileAchievement.unlockedAt, ProfileActivityItem.type, ProfileActivityItem.sandboxId, ProfileActivityItem.gameTitle, ProfileActivityItem.achievementName, ProfileActivityItem.achievementIconUrl, ProfileActivityItem.occurredAt, ProfileGameConnection.elements, ProfileGameConnection.total, ProfileGameConnection.page, ProfileGameConnection.limit, ProfileAchievementConnection.elements, ProfileAchievementConnection.total, ProfileAchievementConnection.page, ProfileAchievementConnection.limit, OfferMappings.pageSlug, OfferMappings.pageType, OfferMappings._id, CustomAttribute.key, CustomAttribute.value, CustomAttribute.type, CustomAttribute._id, Tag.id, Tag.name, Tag.groupName, Seller.id, Seller.name, KeyImage.type, KeyImage.url, KeyImage.md5, Price.country, Price.region, Price.namespace, Price.offerId, Price.price, Price.appliedRules, Price.updatedAt, SinglePrice.currencyCode, SinglePrice.discount, SinglePrice.discountPrice, SinglePrice.originalPrice, SinglePrice.basePayoutCurrencyCode, SinglePrice.basePayoutPrice, SinglePrice.payoutCurrencyExchangeRate, AppliedRule.id, AppliedRule.name, AppliedRule.namespace, AppliedRule.promotionStatus, AppliedRule.startDate, AppliedRule.endDate, AppliedRule.saleType, AppliedRule.regionIds, Asset._id, Asset.artifactId, Asset.downloadSizeBytes, Asset.installedSizeBytes, Asset.itemId, Asset.namespace, Asset.platform, Asset.title, Asset.updatedAt, Build._id, Build.appName, Build.labelName, Build.buildVersion, Build.hash, Build.metadata, Build.downloadSizeBytes, Build.installedSizeBytes, Build.createdAt, Build.updatedAt, Build.technologies, Build.items, Build.files, Build.installOptions, FileConnection.elements, FileConnection.total, FileConnection.page, FileConnection.limit, File.fileName, File.fileSize, File.fileHash, File.manifestHash, File.depth, File.installTags, BuildMetadata.installationPoolId, Technology.section, Technology.technology, Changelog._id, Changelog.metadata, Changelog.timestamp, Changelog.document, ChangelogMetadata.contextId, ChangelogMetadata.contextType, ChangelogMetadata.changes, ChangelogChange.changeType, ChangelogChange.field, ChangelogChange.before, ChangelogChange.after, Item._id, Item.id, Item.namespace, Item.title, Item.description, Item.keyImages, Item.categories, Item.status, Item.creationDate, Item.lastModifiedDate, Item.customAttributes, Item.entitlementName, Item.entitlementType, Item.itemType, Item.releaseInfo, Item.developer, Item.developerId, Item.eulaIds, Item.endOfSupport, Item.applicationId, Item.unsearchable, Item.requiresSecureAccount, Item.offers, Item.assets, Item.builds, Item.changelog, Item.mainOffer, ItemCategory.path, ReleaseInfo.id, ReleaseInfo.appId, ReleaseInfo.platform, Sandbox._id, Sandbox.name, Sandbox.displayName, Sandbox.namespace, Sandbox.parent, Sandbox.store, Sandbox.status, Sandbox.ageGatings, Sandbox.created, Sandbox.updated, Sandbox.items, Sandbox.offers, Sandbox.assets, Sandbox.builds, Sandbox.baseGame, Sandbox.achievements, Sandbox.stats, Sandbox.changelog, SandboxHub.id, SandboxHub.namespace, SandboxHub.title, SandboxHub.description, SandboxHub.primaryKind, SandboxHub.primaryOffer, SandboxHub.primaryItem, SandboxHub.sandbox, SandboxHub.price, SandboxHub.seller, SandboxHub.developer, SandboxHub.publisher, SandboxHub.keyImages, SandboxHub.genres, SandboxHub.platforms, SandboxHub.stats, SandboxHub.featuredOffers, SandboxHub.recentBuilds, SandboxHub.recentChanges, SandboxHub.ageRating, SandboxHub.achievements, SandboxHub.created, SandboxHub.updated, SandboxAchievementSummary.sets, SandboxAchievementSummary.total, SandboxAchievementSummary.baseTotal, SandboxAchievementSummary.xp, AssetConnection.elements, AssetConnection.total, AssetConnection.page, AssetConnection.limit, AssetConnection.count, BuildConnection.elements, BuildConnection.total, BuildConnection.page, BuildConnection.limit, BuildConnection.count, SandboxStats.offers, SandboxStats.items, SandboxStats.assets, SandboxStats.builds, SandboxStats.achievements, AchievementSet._id, AchievementSet.sandboxId, AchievementSet.isBase, AchievementSet.achievements, Achievement.id, Achievement.name, Achievement.description, Achievement.unlockedIcon, Achievement.lockedIcon, Achievement.rarity, Achievement.score, Franchise._id, Franchise.id, Franchise.name, Franchise.offers, Franchise.allOffers, Giveaway._id, Giveaway.id, Giveaway.namespace, Giveaway.startDate, Giveaway.endDate, Poll._id, Poll.options, PollOption.id, PollOption.name, PollOption.votes, Rating._id, Rating.overallScore, Rating.recommendedPercentage, Rating.totalReviews, Hltb._id, Hltb.hltbId, Hltb.name, Hltb.main, Hltb.mainExtra, Hltb.completionist, Offer._id, Offer.id, Offer.namespace, Offer.title, Offer.description, Offer.longDescription, Offer.offerType, Offer.effectiveDate, Offer.creationDate, Offer.lastModifiedDate, Offer.isCodeRedemptionOnly, Offer.productSlug, Offer.urlSlug, Offer.url, Offer.developerDisplayName, Offer.publisherDisplayName, Offer.prePurchase, Offer.releaseDate, Offer.pcReleaseDate, Offer.expiryDate, Offer.viewableDate, Offer.countriesBlacklist, Offer.countriesWhitelist, Offer.refundType, Offer.offerMappings, Offer.categories, Offer.customAttributes, Offer.items, Offer.tags, Offer.seller, Offer.keyImages, Offer.price, Offer.changelog, Offer.franchises, Offer.giveaways, Offer.related, Offer.suggestions, Offer.ratings, Offer.polls, Offer.hltb, Offer.sandbox, Offer.positions, Offer.ageRating, Offer.features, Offer.locale, Offer.localeStatus, Offer.canonicalLocale, Offer.localization, OfferLocalizationMetadata.source, OfferLocalizationMetadata.fetchedAt, OfferLocalizationMetadata.sourceUpdatedAt, OfferFeatures.launcher, OfferFeatures.features, OfferFeatures.epicFeatures, ChangelogConnection.elements, ChangelogConnection.totalCount, ChangelogConnection.totalPages, ChangelogConnection.hasNextPage, ChangelogConnection.hasPreviousPage
- legacy POST /ping (legacyPost_ping_4242a078; 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.
- legacy GET /active-sales (listActiveSales; 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.
- legacy GET /builds/{id}/files (listBuildFiles; 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.
- legacy GET /builds/{id}/items (listBuildItems; 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.
- legacy GET /builds (listBuilds; 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.
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- legacy GET /changelist (listChangelist; 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.
- legacy GET /countries (listCountries; 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.
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; 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.
- legacy GET /featured (listFeaturedGames; 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.
- legacy GET /free-games/history (listFreeGamesHistory; 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.
- legacy GET /free-games/sellers (listFreeGamesSellers; 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.
- legacy GET /items (listItems; 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.
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; 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.
- legacy GET /latest-games (listLatestGames; 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.
- legacy GET /offers/latest-released (listLatestReleasedOffers; 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.
- legacy GET /free-games/mobile (listMobileFreeGames; 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.
- legacy GET /offers/{id}/achievements (listOfferAchievements; 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.
- legacy GET /offers/{id}/assets (listOfferAssets; 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.
- legacy GET /offers/{id}/builds (listOfferBuilds; 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.
- legacy GET /offers/{id}/changelog (listOfferChangelog; 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.
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; 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.
- legacy GET /offers/{id}/genres (listOfferDetailGenres; 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.
- legacy GET /offers/events (listOfferEvents; 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.
- legacy GET /offers/{id}/franchises (listOfferFranchises; 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.
- legacy GET /offers/genres (listOfferGenres; 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.
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; 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.
- legacy GET /offers/{id}/items (listOfferItems; 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.
- legacy GET /offers/{id}/reviews (listOfferReviews; 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.
- legacy GET /offers (listOffers; 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.
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; 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.
- legacy GET /offers/{id}/technologies (listOfferTechnologies; 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.
- legacy GET /regions (listRegions; 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.
- legacy GET /offers/{id}/related (listRelatedOffers; 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.
- legacy GET /sales (listSaleOffers; 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.
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; 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.
- legacy GET /sandboxes (listSandboxes; 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.
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; 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.
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- legacy GET /search/developers (listSearchDevelopers; 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.
- legacy GET /search/offer-types (listSearchOfferTypes; 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.
- legacy GET /search/publishers (listSearchPublishers; 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.
- legacy GET /search/tags (listSearchTags; 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.
- legacy GET /sellers/{id} (listSellerOffers; 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.
- legacy GET /sellers (listSellers; 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.
- legacy GET /offers/top-sellers (listTopSellersOffers; 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.
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; 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.
- legacy GET /offers/upcoming (listUpcomingOffers; 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.
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; 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.
- legacy POST /offers/slugs (resolveOfferSlugs; 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.
- legacy GET /search/changelog (searchChangelog; 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.
- legacy GET /free-games/search (searchFreeGames; 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.
- legacy POST /search (searchOffersLegacy; 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.
- legacy POST /search/v2/search (searchOffersV2; 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.
- legacy GET /search/v2/search (searchOffersV2Get; 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.
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; 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.
- v1 GET /v1/autocomplete (autocomplete; 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.
- v1 POST /v1/offers/exists (checkOfferExistence; 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.
- v1 POST /v1/offers/slugs (checkOfferSlugs; 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.
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- v1 GET /v1/assets/{id} (getAsset; 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.
- v1 GET /v1/base-game/{namespace} (getBaseGame; 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.
- v1 GET /v1/builds/{id} (getBuild; 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.
- v1 GET /v1/builds/{id}/history (getBuildHistory; 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.
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; 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.
- v1 GET /v1/builds/{id}/tree (getBuildTree; 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.
- v1 GET /v1/changelist/{id} (getChangelogEntry; 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.
- v1 GET /v1/collections/{slug} (getCollection; 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.
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; 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.
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; 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.
- v1 GET /v1/featured (getFeaturedGames; 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.
- v1 GET /v1/franchises/{slug} (getFranchise; 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.
- v1 GET /v1/free-games/og (getFreeGamesOg; 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.
- v1 GET /v1/free-games/stats (getFreeGamesStats; 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.
- v1 GET /v1/game-awards (getGameAwards; 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.
- v1 GET /v1/game-awards/og (getGameAwardsOg; 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.
- 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.
- v1 GET /v1/stats/homepage (getHomepageStats; 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.
- v1 GET /v1/items/{id} (getItem; 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.
- v1 GET /v1/items/{id}/assets (getItemAssets; 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.
- v1 GET /v1/items/{id}/builds (getItemBuilds; 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.
- v1 GET /v1/items/{id}/changelog (getItemChangelog; 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.
- v1 GET /v1/items/{id}/offer (getItemOffer; 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.
- v1 POST /v1/items/bulk (getItemsBulk; 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.
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; 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.
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; 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.
- v1 GET /v1/latest-games (getLatestGames; 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.
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; 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.
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; 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.
- v1 GET /v1/offers/{id} (getOffer; 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.
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; 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.
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; 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.
- v1 GET /v1/offers/{id}/assets (getOfferAssets; 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.
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; 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.
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; 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.
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; 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.
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- v1 GET /v1/offers/{id}/collection (getOfferCollection; 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.
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; 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.
- v1 GET /v1/offers/events/{id} (getOfferEvent; 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.
- v1 GET /v1/offers/{id}/features (getOfferFeatures; 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.
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; 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.
- v1 GET /v1/offers/{id}/genres (getOfferGenres; 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.
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; 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.
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; 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.
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; 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.
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; 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.
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; 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.
- v1 GET /v1/offers/{id}/items (getOfferItems; 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.
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; 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.
- v1 GET /v1/offers/{id}/media (getOfferMedia; 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.
- v1 GET /v1/offers/{id}/og (getOfferOg; 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.
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; 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.
- v1 GET /v1/offers/{id}/overview (getOfferOverview; 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.
- v1 GET /v1/offers/{id}/polls (getOfferPolls; 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.
- v1 GET /v1/offers/{id}/price (getOfferPrice; 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.
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; 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.
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; 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.
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; 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.
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; 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.
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; 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.
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; 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.
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; 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.
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; 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.
- v1 GET /v1/offers/{id}/tops (getOfferTops; 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.
- v1 GET /v1/profiles/{id} (getProfile; 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.
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/information (getProfileInformation; 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.
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; 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.
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; 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.
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; 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.
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; 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.
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; 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.
- v1 GET /v1/region (getRegion; 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.
- v1 GET /v1/offers/{id}/related (getRelatedOffers; 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.
- v1 GET /v1/robots.txt (getRobots; 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.
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; 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.
- v1 GET /v1/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.
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; 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.
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- v1 GET /v1/search/{id} (getSearchQuery; 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.
- v1 GET /v1/search/{id}/count (getSearchQueryCount; 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.
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; 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.
- v1 GET /v1/sellers/{id}/stats (getSellerStats; 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.
- v1 GET /v1/sitemap.xml (getSitemap; 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.
- v1 GET /v1/stats (getStats; 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.
- v1 GET /v1/open-api.json (getV1OpenApi; 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.
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; 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.
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; 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.
- v1 POST /v1/catalog/hydrate (hydrateCatalog; 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.
- v1 GET /v1/active-sales (listActiveSales; 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.
- v1 GET /v1/builds/{id}/files (listBuildFiles; 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.
- v1 GET /v1/builds/{id}/items (listBuildItems; 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.
- v1 GET /v1/builds (listBuilds; 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.
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- v1 GET /v1/changelist (listChangelist; 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.
- v1 GET /v1/changelog (listChangelog; 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.
- v1 GET /v1/countries (listCountries; 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.
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; 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.
- v1 GET /v1/free-games (listFreeGames; 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.
- v1 GET /v1/free-games/sellers (listFreeGameSellers; 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.
- v1 GET /v1/free-games/history (listFreeGamesHistory; 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.
- v1 GET /v1/items (listItems; 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.
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; 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.
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; 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.
- v1 GET /v1/offers/latest-released (listLatestReleased; 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.
- v1 GET /v1/free-games/mobile (listMobileFreeGames; 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.
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; 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.
- v1 GET /v1/offers/events (listOfferEvents; 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.
- v1 GET /v1/offers/genres (listOfferGenres; 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.
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; 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.
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; 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.
- v1 GET /v1/offers (listOffers; 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.
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/games (listProfileGames; 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.
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; 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.
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; 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.
- v1 GET /v1/promotions/{id} (listPromotionOffers; 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.
- v1 GET /v1/promotions (listPromotions; 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.
- v1 GET /v1/regions (listRegions; 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.
- v1 GET /v1/sales (listSales; 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.
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- v1 GET /v1/sandboxes (listSandboxes; 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.
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; 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.
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- v1 GET /v1/search/developers (listSearchDevelopers; 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.
- v1 GET /v1/search/offer-types (listSearchOfferTypes; 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.
- v1 GET /v1/search/publishers (listSearchPublishers; 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.
- v1 GET /v1/search/tags (listSearchTags; 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.
- v1 GET /v1/sellers/{id} (listSellerOffers; 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.
- v1 GET /v1/sellers (listSellers; 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.
- v1 GET /v1/tags (listTags; 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.
- v1 GET /v1/offers/top-sellers (listTopSellers; 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.
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; 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.
- v1 GET /v1/offers/upcoming (listUpcomingOffers; 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.
- v1 GET /v1/multisearch/items (multisearchItems; 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.
- v1 GET /v1/multisearch/offers (multisearchOffers; 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.
- v1 GET /v1/multisearch/sellers (multisearchSellers; 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.
- v1 POST /v1/search/natural-language (naturalLanguageSearch; 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.
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; 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.
- v1 GET /v1/search/changelog (searchChangelog; 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.
- v1 GET /v1/free-games/search (searchFreeGames; 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.
- v1 GET /v1/search (searchOffers; 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.
- v1 POST /v1/search (searchOffersRedirect; 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 /autocomplete (autocompleteOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitsearchper-minute expensive policy ceiling for the project's active plan (60/200/600 rpm on Free/Pro/Scale). - 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.
- 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
- legacy POST /offers/exists (checkOffersExist; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search/{id}/count (countSavedSearchResults; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /builds/{id} (getBuild; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /builds/{id}/tree (getBuildFileTree; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /builds/{id}/history (getBuildHistory; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /changelist/{id} (getChangelistEntry; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /free-games (getFreeGames; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /free-games/stats (getFreeGamesStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /stats/homepage (getHomepageStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /items/{id} (getItem; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /items/{id}/assets (getItemAssets; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /items/{id}/builds (getItemBuilds; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /items/{id}/changelog (getItemChangelog; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /items/{id}/offer (getItemOffer; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy POST /items/bulk (getItemsBulk; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id} (getOffer; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/bundle (getOfferBundle; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/events/{id} (getOfferEvent; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/features (getOfferFeatures; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/igdb (getOfferIgdb; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/mappings (getOfferMappings; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/media (getOfferMedia; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/og (getOfferOgPng; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /offers/{id}/overview (getOfferOverview; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/polls (getOfferPolls; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/price (getOfferPrice; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/ratings (getOfferRatings; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/requirements (getOfferRequirements; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/tops (getOfferTopPositions; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy POST /items/bulk/offers (getOffersForItemsBulk; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /region (getRegionForCountry; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId} (getSandbox; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search/{id} (getSavedSearchQuery; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /sellers/{id}/stats (getSellerStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /stats (getStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /stats/creations/yearly (getYearlyCreationStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy POST /catalog/hydrate (hydrateCatalogGraph; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitbulkper-minute expensive policy ceiling for the project's active plan (5/15/40 rpm on Free/Pro/Scale). Requires entitlementbulk:resolveand consumes the explicitbulkper-period expensive budget (1000/10000/40000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET / (legacyGet__c767025d; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /changelog (legacyGet_changelog_038722cc; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /doc (legacyGet_doc_f5f543a0; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /graphql (legacyGet_graphql_220e6fb1; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires server-side entitlementgraphql:read. - 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- 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
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /multisearch (legacyGet_multisearch_229582ca; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /promotions (legacyGet_promotions_83dd267d; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search (legacyGet_search_82dab022; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /tags (legacyGet_tags_803dea8c; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy POST /graphql (legacyPost_graphql_fac042a8; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires server-side entitlementgraphql:read. - 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- 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
- legacy GET /active-sales (listActiveSales; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /builds/{id}/files (listBuildFiles; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /builds/{id}/items (listBuildItems; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /builds (listBuilds; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /changelist (listChangelist; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /countries (listCountries; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /featured (listFeaturedGames; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /free-games/history (listFreeGamesHistory; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /free-games/sellers (listFreeGamesSellers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /items (listItems; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /latest-games (listLatestGames; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/latest-released (listLatestReleasedOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /free-games/mobile (listMobileFreeGames; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/achievements (listOfferAchievements; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/assets (listOfferAssets; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/builds (listOfferBuilds; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/changelog (listOfferChangelog; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/genres (listOfferDetailGenres; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/events (listOfferEvents; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/franchises (listOfferFranchises; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/genres (listOfferGenres; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/items (listOfferItems; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/reviews (listOfferReviews; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/technologies (listOfferTechnologies; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers (listOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitoffers-listper-minute expensive policy ceiling for the project's active plan (5/20/60 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /regions (listRegions; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/{id}/related (listRelatedOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sales (listSaleOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sandboxes (listSandboxes; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search/developers (listSearchDevelopers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search/offer-types (listSearchOfferTypes; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search/publishers (listSearchPublishers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search/tags (listSearchTags; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /sellers/{id} (listSellerOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /sellers (listSellers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/top-sellers (listTopSellersOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /offers/upcoming (listUpcomingOffers; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitbulkper-minute expensive policy ceiling for the project's active plan (5/15/40 rpm on Free/Pro/Scale). Requires entitlementbulk:resolveand consumes the explicitbulkper-period expensive budget (1000/10000/40000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- legacy POST /offers/slugs (resolveOfferSlugs; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy GET /search/changelog (searchChangelog; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitsearchper-minute expensive policy ceiling for the project's active plan (60/200/600 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /free-games/search (searchFreeGames; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitsearchper-minute expensive policy ceiling for the project's active plan (60/200/600 rpm on Free/Pro/Scale). - 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.
- 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
- legacy POST /search (searchOffersLegacy; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard 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.
- 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
- legacy POST /search/v2/search (searchOffersV2; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitsearchper-minute expensive policy ceiling for the project's active plan (60/200/600 rpm on Free/Pro/Scale). - 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.
- 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
- legacy GET /search/v2/search (searchOffersV2Get; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitsearchper-minute expensive policy ceiling for the project's active plan (60/200/600 rpm on Free/Pro/Scale). - 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.
- 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
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; 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:readscope 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 ascaletier. - 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),5xxupstream responses credit back consumed period units idempotently, spoofable Origin-header auth bypass andcatalog:readwildcard bypass are removed in favor of trusted first-party service tokens, and active-minute expensive counters are preserved across mixed requests. Requests are subject to the explicitheavyper-minute expensive policy ceiling for the project's active plan (20/60/180 rpm on Free/Pro/Scale). Requires entitlementsearch:nland consumes the explicitnl-searchper-period expensive budget (500/2500/10000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- 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
- v1 GET /v1/autocomplete (autocomplete; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/offers/exists (checkOfferExistence; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/offers/slugs (checkOfferSlugs; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/assets/{id} (getAsset; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/base-game/{namespace} (getBaseGame; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds/{id} (getBuild; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds/{id}/history (getBuildHistory; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds/{id}/tree (getBuildTree; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/changelist/{id} (getChangelogEntry; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/collections/{slug} (getCollection; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/featured (getFeaturedGames; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/franchises/{slug} (getFranchise; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/free-games/og (getFreeGamesOg; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/free-games/stats (getFreeGamesStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/game-awards (getGameAwards; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/game-awards/og (getGameAwardsOg; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/stats/homepage (getHomepageStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items/{id} (getItem; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items/{id}/assets (getItemAssets; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items/{id}/builds (getItemBuilds; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items/{id}/changelog (getItemChangelog; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items/{id}/offer (getItemOffer; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/items/bulk (getItemsBulk; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/latest-games (getLatestGames; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id} (getOffer; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/assets (getOfferAssets; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/collection (getOfferCollection; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/events/{id} (getOfferEvent; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/features (getOfferFeatures; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/genres (getOfferGenres; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/items (getOfferItems; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/media (getOfferMedia; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/og (getOfferOg; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/overview (getOfferOverview; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/polls (getOfferPolls; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/price (getOfferPrice; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/tops (getOfferTops; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id} (getProfile; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id}/information (getProfileInformation; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/region (getRegion; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/related (getRelatedOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/robots.txt (getRobots; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search/{id} (getSearchQuery; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search/{id}/count (getSearchQueryCount; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementimage:ogand consumes the explicitimageper-period expensive budget (2000/15000/50000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sellers/{id}/stats (getSellerStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sitemap.xml (getSitemap; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/stats (getStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/open-api.json (getV1OpenApi; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/catalog/hydrate (hydrateCatalog; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementbulk:resolveand consumes the explicitbulkper-period expensive budget (1000/10000/40000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/active-sales (listActiveSales; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds/{id}/files (listBuildFiles; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds/{id}/items (listBuildItems; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/builds (listBuilds; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/changelist (listChangelist; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/changelog (listChangelog; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/countries (listCountries; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/free-games/sellers (listFreeGameSellers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/free-games (listFreeGames; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/free-games/history (listFreeGamesHistory; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items (listItems; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/latest-released (listLatestReleased; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/free-games/mobile (listMobileFreeGames; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/events (listOfferEvents; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/genres (listOfferGenres; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers (listOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id}/games (listProfileGames; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/promotions/{id} (listPromotionOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/promotions (listPromotions; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/regions (listRegions; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sales (listSales; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sandboxes (listSandboxes; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search/developers (listSearchDevelopers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search/offer-types (listSearchOfferTypes; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search/publishers (listSearchPublishers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search/tags (listSearchTags; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sellers/{id} (listSellerOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/sellers (listSellers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/tags (listTags; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/top-sellers (listTopSellers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/offers/upcoming (listUpcomingOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/multisearch/items (multisearchItems; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/multisearch/offers (multisearchOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/multisearch/sellers (multisearchSellers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/search/natural-language (naturalLanguageSearch; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementsearch:nland consumes the explicitnl-searchper-period expensive budget (500/2500/10000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. Requires entitlementbulk:resolveand consumes the explicitbulkper-period expensive budget (1000/10000/40000 on Free/Pro/Scale), returning429 EXPENSIVE_BUDGET_EXCEEDEDwhen exhausted. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search/changelog (searchChangelog; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/free-games/search (searchFreeGames; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 GET /v1/search (searchOffers; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
- v1 POST /v1/search (searchOffersRedirect; changed; compatible)
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
catalog:readscope bypassed granular scope restrictions, and ordinary admitted requests could clear active-minute expensive-policy counters in the same window. - After: Version 1 gateway now enforces Free (60 RPM when commercial limits are enabled, 100,000/month UTC), Pro (200 RPM, 300,000/billing period), Scale (600 RPM, 1,000,000/billing period), and explicit manual/enterprise grants, returning RFC 9457 Problem JSON
403 PLAN_ENTITLEMENT_REQUIREDand429 PERIOD_QUOTA_EXCEEDEDwhen exceeded, with idempotent5xxperiod-unit credit-back. Server-owned entitlements are checked prior to edge cache and quota admission,catalog:readwildcard bypass is removed, and active-minute expensive counters remain isolated. - 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.
- Before: Version 1 gateway admission enforced Free/Pro/Enterprise RPM and monthly quota without server-side plan entitlement gates, Scale tier support, or paid billing-period allowances. Keys holding the
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 /autocomplete (autocompleteOffers; 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.
- legacy POST /offers/exists (checkOffersExist; 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.
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- legacy GET /search/{id}/count (countSavedSearchResults; 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.
- legacy GET /builds/{id} (getBuild; 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.
- legacy GET /builds/{id}/tree (getBuildFileTree; 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.
- legacy GET /builds/{id}/history (getBuildHistory; 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.
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; 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.
- legacy GET /changelist/{id} (getChangelistEntry; 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.
- legacy GET /free-games (getFreeGames; 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.
- legacy GET /free-games/stats (getFreeGamesStats; 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.
- legacy GET /stats/homepage (getHomepageStats; 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.
- legacy GET /items/{id} (getItem; 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.
- legacy GET /items/{id}/assets (getItemAssets; 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.
- legacy GET /items/{id}/builds (getItemBuilds; 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.
- legacy GET /items/{id}/changelog (getItemChangelog; 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.
- legacy GET /items/{id}/offer (getItemOffer; 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.
- legacy POST /items/bulk (getItemsBulk; 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.
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; 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.
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; 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.
- legacy GET /offers/{id} (getOffer; 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.
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; 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.
- legacy GET /offers/{id}/bundle (getOfferBundle; 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.
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; 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.
- legacy GET /offers/events/{id} (getOfferEvent; 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.
- legacy GET /offers/{id}/features (getOfferFeatures; 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.
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; 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.
- legacy GET /offers/{id}/igdb (getOfferIgdb; 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.
- legacy GET /offers/{id}/mappings (getOfferMappings; 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.
- legacy GET /offers/{id}/media (getOfferMedia; 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.
- legacy GET /offers/{id}/og (getOfferOgPng; 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.
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; 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.
- legacy GET /offers/{id}/overview (getOfferOverview; 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.
- legacy GET /offers/{id}/polls (getOfferPolls; 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.
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; 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.
- legacy GET /offers/{id}/price (getOfferPrice; 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.
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; 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.
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; 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.
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; 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.
- legacy GET /offers/{id}/ratings (getOfferRatings; 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.
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; 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.
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; 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.
- legacy GET /offers/{id}/requirements (getOfferRequirements; 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.
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- legacy POST /items/bulk/offers (getOffersForItemsBulk; 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.
- legacy GET /offers/{id}/tops (getOfferTopPositions; 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.
- legacy GET /region (getRegionForCountry; 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.
- legacy GET /sandboxes/{sandboxId} (getSandbox; 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.
- 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.
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; 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.
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- legacy GET /search/{id} (getSavedSearchQuery; 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.
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; 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.
- legacy GET /sellers/{id}/stats (getSellerStats; 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.
- legacy GET /stats (getStats; 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.
- legacy GET /stats/creations/yearly (getYearlyCreationStats; 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.
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; 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.
- legacy POST /catalog/hydrate (hydrateCatalogGraph; 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.
- legacy GET / (legacyGet__c767025d; 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.
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; 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.
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; 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.
- legacy GET /changelog (legacyGet_changelog_038722cc; 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.
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; 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.
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; 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.
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; 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.
- legacy GET /doc (legacyGet_doc_f5f543a0; 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.
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; 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.
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; 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.
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; 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.
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; 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.
- legacy GET /graphql (legacyGet_graphql_220e6fb1; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements, GenreResult.genre, GenreResult.offers, GenreOffer.id, GenreOffer.title, GenreOffer.image, OfferConnection.elements, OfferConnection.total, OfferConnection.page, OfferConnection.limit, OfferConnection.count, ItemConnection.elements, ItemConnection.total, ItemConnection.page, ItemConnection.limit, SandboxConnection.elements, SandboxConnection.total, SandboxConnection.page, SandboxConnection.limit, Profile.accountId, Profile.displayName, Profile.avatar, Profile.linkedAccounts, Profile.creationDate, Profile.reviewsCount, Profile.highlights, Profile.heroGame, Profile.featuredAchievements, Profile.featuredGames, Profile.recentActivity, Profile.games, Profile.achievements, ProfileAvatar.small, ProfileAvatar.medium, ProfileAvatar.large, ProfileHighlights.level, ProfileHighlights.totalXP, ProfileHighlights.totalGames, ProfileHighlights.totalAchievements, ProfileHighlights.totalPlatinums, ProfileHighlights.reviewsCount, ProfileHeroGame.sandboxId, ProfileHeroGame.title, ProfileHeroGame.imageUrl, ProfileHeroGame.completionPercent, ProfileGame.sandboxId, ProfileGame.title, ProfileGame.imageUrl, ProfileGame.completionPercent, ProfileGame.unlocked, ProfileGame.total, ProfileGame.earnedXP, ProfileGame.totalXP, ProfileGame.hasPlatinum, ProfileGame.rarestAchievements, ProfileAchievement.name, ProfileAchievement.displayName, ProfileAchievement.description, ProfileAchievement.iconUrl, ProfileAchievement.rarityPercent, ProfileAchievement.xp, ProfileAchievement.sandboxId, ProfileAchievement.gameTitle, ProfileAchievement.unlockedAt, ProfileActivityItem.type, ProfileActivityItem.sandboxId, ProfileActivityItem.gameTitle, ProfileActivityItem.achievementName, ProfileActivityItem.achievementIconUrl, ProfileActivityItem.occurredAt, ProfileGameConnection.elements, ProfileGameConnection.total, ProfileGameConnection.page, ProfileGameConnection.limit, ProfileAchievementConnection.elements, ProfileAchievementConnection.total, ProfileAchievementConnection.page, ProfileAchievementConnection.limit, OfferMappings.pageSlug, OfferMappings.pageType, OfferMappings._id, CustomAttribute.key, CustomAttribute.value, CustomAttribute.type, CustomAttribute._id, Tag.id, Tag.name, Tag.groupName, Seller.id, Seller.name, KeyImage.type, KeyImage.url, KeyImage.md5, Price.country, Price.region, Price.namespace, Price.offerId, Price.price, Price.appliedRules, Price.updatedAt, SinglePrice.currencyCode, SinglePrice.discount, SinglePrice.discountPrice, SinglePrice.originalPrice, SinglePrice.basePayoutCurrencyCode, SinglePrice.basePayoutPrice, SinglePrice.payoutCurrencyExchangeRate, AppliedRule.id, AppliedRule.name, AppliedRule.namespace, AppliedRule.promotionStatus, AppliedRule.startDate, AppliedRule.endDate, AppliedRule.saleType, AppliedRule.regionIds, Asset._id, Asset.artifactId, Asset.downloadSizeBytes, Asset.installedSizeBytes, Asset.itemId, Asset.namespace, Asset.platform, Asset.title, Asset.updatedAt, Build._id, Build.appName, Build.labelName, Build.buildVersion, Build.hash, Build.metadata, Build.downloadSizeBytes, Build.installedSizeBytes, Build.createdAt, Build.updatedAt, Build.technologies, Build.items, Build.files, Build.installOptions, FileConnection.elements, FileConnection.total, FileConnection.page, FileConnection.limit, File.fileName, File.fileSize, File.fileHash, File.manifestHash, File.depth, File.installTags, BuildMetadata.installationPoolId, Technology.section, Technology.technology, Changelog._id, Changelog.metadata, Changelog.timestamp, Changelog.document, ChangelogMetadata.contextId, ChangelogMetadata.contextType, ChangelogMetadata.changes, ChangelogChange.changeType, ChangelogChange.field, ChangelogChange.before, ChangelogChange.after, Item._id, Item.id, Item.namespace, Item.title, Item.description, Item.keyImages, Item.categories, Item.status, Item.creationDate, Item.lastModifiedDate, Item.customAttributes, Item.entitlementName, Item.entitlementType, Item.itemType, Item.releaseInfo, Item.developer, Item.developerId, Item.eulaIds, Item.endOfSupport, Item.applicationId, Item.unsearchable, Item.requiresSecureAccount, Item.offers, Item.assets, Item.builds, Item.changelog, Item.mainOffer, ItemCategory.path, ReleaseInfo.id, ReleaseInfo.appId, ReleaseInfo.platform, Sandbox._id, Sandbox.name, Sandbox.displayName, Sandbox.namespace, Sandbox.parent, Sandbox.store, Sandbox.status, Sandbox.ageGatings, Sandbox.created, Sandbox.updated, Sandbox.items, Sandbox.offers, Sandbox.assets, Sandbox.builds, Sandbox.baseGame, Sandbox.achievements, Sandbox.stats, Sandbox.changelog, SandboxHub.id, SandboxHub.namespace, SandboxHub.title, SandboxHub.description, SandboxHub.primaryKind, SandboxHub.primaryOffer, SandboxHub.primaryItem, SandboxHub.sandbox, SandboxHub.price, SandboxHub.seller, SandboxHub.developer, SandboxHub.publisher, SandboxHub.keyImages, SandboxHub.genres, SandboxHub.platforms, SandboxHub.stats, SandboxHub.featuredOffers, SandboxHub.recentBuilds, SandboxHub.recentChanges, SandboxHub.ageRating, SandboxHub.achievements, SandboxHub.created, SandboxHub.updated, SandboxAchievementSummary.sets, SandboxAchievementSummary.total, SandboxAchievementSummary.baseTotal, SandboxAchievementSummary.xp, AssetConnection.elements, AssetConnection.total, AssetConnection.page, AssetConnection.limit, AssetConnection.count, BuildConnection.elements, BuildConnection.total, BuildConnection.page, BuildConnection.limit, BuildConnection.count, SandboxStats.offers, SandboxStats.items, SandboxStats.assets, SandboxStats.builds, SandboxStats.achievements, AchievementSet._id, AchievementSet.sandboxId, AchievementSet.isBase, AchievementSet.achievements, Achievement.id, Achievement.name, Achievement.description, Achievement.unlockedIcon, Achievement.lockedIcon, Achievement.rarity, Achievement.score, Franchise._id, Franchise.id, Franchise.name, Franchise.offers, Franchise.allOffers, Giveaway._id, Giveaway.id, Giveaway.namespace, Giveaway.startDate, Giveaway.endDate, Poll._id, Poll.options, PollOption.id, PollOption.name, PollOption.votes, Rating._id, Rating.overallScore, Rating.recommendedPercentage, Rating.totalReviews, Hltb._id, Hltb.hltbId, Hltb.name, Hltb.main, Hltb.mainExtra, Hltb.completionist, Offer._id, Offer.id, Offer.namespace, Offer.title, Offer.description, Offer.longDescription, Offer.offerType, Offer.effectiveDate, Offer.creationDate, Offer.lastModifiedDate, Offer.isCodeRedemptionOnly, Offer.productSlug, Offer.urlSlug, Offer.url, Offer.developerDisplayName, Offer.publisherDisplayName, Offer.prePurchase, Offer.releaseDate, Offer.pcReleaseDate, Offer.expiryDate, Offer.viewableDate, Offer.countriesBlacklist, Offer.countriesWhitelist, Offer.refundType, Offer.offerMappings, Offer.categories, Offer.customAttributes, Offer.items, Offer.tags, Offer.seller, Offer.keyImages, Offer.price, Offer.changelog, Offer.franchises, Offer.giveaways, Offer.related, Offer.suggestions, Offer.ratings, Offer.polls, Offer.hltb, Offer.sandbox, Offer.positions, Offer.ageRating, Offer.features, Offer.locale, Offer.localeStatus, Offer.canonicalLocale, Offer.localization, OfferLocalizationMetadata.source, OfferLocalizationMetadata.fetchedAt, OfferLocalizationMetadata.sourceUpdatedAt, OfferFeatures.launcher, OfferFeatures.features, OfferFeatures.epicFeatures, ChangelogConnection.elements, ChangelogConnection.totalCount, ChangelogConnection.totalPages, ChangelogConnection.hasNextPage, ChangelogConnection.hasPreviousPage
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; 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.
- legacy GET /multisearch (legacyGet_multisearch_229582ca; 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.
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; 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.
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; 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.
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; 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.
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; 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.
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; 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.
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; 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.
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; 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.
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; 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.
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; 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.
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; 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.
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; 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.
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; 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.
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; 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.
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; 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.
- legacy GET /promotions (legacyGet_promotions_83dd267d; 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.
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; 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.
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; 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.
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; 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.
- legacy GET /search (legacyGet_search_82dab022; 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.
- legacy GET /tags (legacyGet_tags_803dea8c; 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.
- legacy POST /graphql (legacyPost_graphql_fac042a8; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements, GenreResult.genre, GenreResult.offers, GenreOffer.id, GenreOffer.title, GenreOffer.image, OfferConnection.elements, OfferConnection.total, OfferConnection.page, OfferConnection.limit, OfferConnection.count, ItemConnection.elements, ItemConnection.total, ItemConnection.page, ItemConnection.limit, SandboxConnection.elements, SandboxConnection.total, SandboxConnection.page, SandboxConnection.limit, Profile.accountId, Profile.displayName, Profile.avatar, Profile.linkedAccounts, Profile.creationDate, Profile.reviewsCount, Profile.highlights, Profile.heroGame, Profile.featuredAchievements, Profile.featuredGames, Profile.recentActivity, Profile.games, Profile.achievements, ProfileAvatar.small, ProfileAvatar.medium, ProfileAvatar.large, ProfileHighlights.level, ProfileHighlights.totalXP, ProfileHighlights.totalGames, ProfileHighlights.totalAchievements, ProfileHighlights.totalPlatinums, ProfileHighlights.reviewsCount, ProfileHeroGame.sandboxId, ProfileHeroGame.title, ProfileHeroGame.imageUrl, ProfileHeroGame.completionPercent, ProfileGame.sandboxId, ProfileGame.title, ProfileGame.imageUrl, ProfileGame.completionPercent, ProfileGame.unlocked, ProfileGame.total, ProfileGame.earnedXP, ProfileGame.totalXP, ProfileGame.hasPlatinum, ProfileGame.rarestAchievements, ProfileAchievement.name, ProfileAchievement.displayName, ProfileAchievement.description, ProfileAchievement.iconUrl, ProfileAchievement.rarityPercent, ProfileAchievement.xp, ProfileAchievement.sandboxId, ProfileAchievement.gameTitle, ProfileAchievement.unlockedAt, ProfileActivityItem.type, ProfileActivityItem.sandboxId, ProfileActivityItem.gameTitle, ProfileActivityItem.achievementName, ProfileActivityItem.achievementIconUrl, ProfileActivityItem.occurredAt, ProfileGameConnection.elements, ProfileGameConnection.total, ProfileGameConnection.page, ProfileGameConnection.limit, ProfileAchievementConnection.elements, ProfileAchievementConnection.total, ProfileAchievementConnection.page, ProfileAchievementConnection.limit, OfferMappings.pageSlug, OfferMappings.pageType, OfferMappings._id, CustomAttribute.key, CustomAttribute.value, CustomAttribute.type, CustomAttribute._id, Tag.id, Tag.name, Tag.groupName, Seller.id, Seller.name, KeyImage.type, KeyImage.url, KeyImage.md5, Price.country, Price.region, Price.namespace, Price.offerId, Price.price, Price.appliedRules, Price.updatedAt, SinglePrice.currencyCode, SinglePrice.discount, SinglePrice.discountPrice, SinglePrice.originalPrice, SinglePrice.basePayoutCurrencyCode, SinglePrice.basePayoutPrice, SinglePrice.payoutCurrencyExchangeRate, AppliedRule.id, AppliedRule.name, AppliedRule.namespace, AppliedRule.promotionStatus, AppliedRule.startDate, AppliedRule.endDate, AppliedRule.saleType, AppliedRule.regionIds, Asset._id, Asset.artifactId, Asset.downloadSizeBytes, Asset.installedSizeBytes, Asset.itemId, Asset.namespace, Asset.platform, Asset.title, Asset.updatedAt, Build._id, Build.appName, Build.labelName, Build.buildVersion, Build.hash, Build.metadata, Build.downloadSizeBytes, Build.installedSizeBytes, Build.createdAt, Build.updatedAt, Build.technologies, Build.items, Build.files, Build.installOptions, FileConnection.elements, FileConnection.total, FileConnection.page, FileConnection.limit, File.fileName, File.fileSize, File.fileHash, File.manifestHash, File.depth, File.installTags, BuildMetadata.installationPoolId, Technology.section, Technology.technology, Changelog._id, Changelog.metadata, Changelog.timestamp, Changelog.document, ChangelogMetadata.contextId, ChangelogMetadata.contextType, ChangelogMetadata.changes, ChangelogChange.changeType, ChangelogChange.field, ChangelogChange.before, ChangelogChange.after, Item._id, Item.id, Item.namespace, Item.title, Item.description, Item.keyImages, Item.categories, Item.status, Item.creationDate, Item.lastModifiedDate, Item.customAttributes, Item.entitlementName, Item.entitlementType, Item.itemType, Item.releaseInfo, Item.developer, Item.developerId, Item.eulaIds, Item.endOfSupport, Item.applicationId, Item.unsearchable, Item.requiresSecureAccount, Item.offers, Item.assets, Item.builds, Item.changelog, Item.mainOffer, ItemCategory.path, ReleaseInfo.id, ReleaseInfo.appId, ReleaseInfo.platform, Sandbox._id, Sandbox.name, Sandbox.displayName, Sandbox.namespace, Sandbox.parent, Sandbox.store, Sandbox.status, Sandbox.ageGatings, Sandbox.created, Sandbox.updated, Sandbox.items, Sandbox.offers, Sandbox.assets, Sandbox.builds, Sandbox.baseGame, Sandbox.achievements, Sandbox.stats, Sandbox.changelog, SandboxHub.id, SandboxHub.namespace, SandboxHub.title, SandboxHub.description, SandboxHub.primaryKind, SandboxHub.primaryOffer, SandboxHub.primaryItem, SandboxHub.sandbox, SandboxHub.price, SandboxHub.seller, SandboxHub.developer, SandboxHub.publisher, SandboxHub.keyImages, SandboxHub.genres, SandboxHub.platforms, SandboxHub.stats, SandboxHub.featuredOffers, SandboxHub.recentBuilds, SandboxHub.recentChanges, SandboxHub.ageRating, SandboxHub.achievements, SandboxHub.created, SandboxHub.updated, SandboxAchievementSummary.sets, SandboxAchievementSummary.total, SandboxAchievementSummary.baseTotal, SandboxAchievementSummary.xp, AssetConnection.elements, AssetConnection.total, AssetConnection.page, AssetConnection.limit, AssetConnection.count, BuildConnection.elements, BuildConnection.total, BuildConnection.page, BuildConnection.limit, BuildConnection.count, SandboxStats.offers, SandboxStats.items, SandboxStats.assets, SandboxStats.builds, SandboxStats.achievements, AchievementSet._id, AchievementSet.sandboxId, AchievementSet.isBase, AchievementSet.achievements, Achievement.id, Achievement.name, Achievement.description, Achievement.unlockedIcon, Achievement.lockedIcon, Achievement.rarity, Achievement.score, Franchise._id, Franchise.id, Franchise.name, Franchise.offers, Franchise.allOffers, Giveaway._id, Giveaway.id, Giveaway.namespace, Giveaway.startDate, Giveaway.endDate, Poll._id, Poll.options, PollOption.id, PollOption.name, PollOption.votes, Rating._id, Rating.overallScore, Rating.recommendedPercentage, Rating.totalReviews, Hltb._id, Hltb.hltbId, Hltb.name, Hltb.main, Hltb.mainExtra, Hltb.completionist, Offer._id, Offer.id, Offer.namespace, Offer.title, Offer.description, Offer.longDescription, Offer.offerType, Offer.effectiveDate, Offer.creationDate, Offer.lastModifiedDate, Offer.isCodeRedemptionOnly, Offer.productSlug, Offer.urlSlug, Offer.url, Offer.developerDisplayName, Offer.publisherDisplayName, Offer.prePurchase, Offer.releaseDate, Offer.pcReleaseDate, Offer.expiryDate, Offer.viewableDate, Offer.countriesBlacklist, Offer.countriesWhitelist, Offer.refundType, Offer.offerMappings, Offer.categories, Offer.customAttributes, Offer.items, Offer.tags, Offer.seller, Offer.keyImages, Offer.price, Offer.changelog, Offer.franchises, Offer.giveaways, Offer.related, Offer.suggestions, Offer.ratings, Offer.polls, Offer.hltb, Offer.sandbox, Offer.positions, Offer.ageRating, Offer.features, Offer.locale, Offer.localeStatus, Offer.canonicalLocale, Offer.localization, OfferLocalizationMetadata.source, OfferLocalizationMetadata.fetchedAt, OfferLocalizationMetadata.sourceUpdatedAt, OfferFeatures.launcher, OfferFeatures.features, OfferFeatures.epicFeatures, ChangelogConnection.elements, ChangelogConnection.totalCount, ChangelogConnection.totalPages, ChangelogConnection.hasNextPage, ChangelogConnection.hasPreviousPage
- legacy GET /active-sales (listActiveSales; 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.
- legacy GET /builds/{id}/files (listBuildFiles; 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.
- legacy GET /builds/{id}/items (listBuildItems; 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.
- legacy GET /builds (listBuilds; 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.
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- legacy GET /changelist (listChangelist; 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.
- legacy GET /countries (listCountries; 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.
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; 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.
- legacy GET /featured (listFeaturedGames; 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.
- legacy GET /free-games/history (listFreeGamesHistory; 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.
- legacy GET /free-games/sellers (listFreeGamesSellers; 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.
- legacy GET /items (listItems; 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.
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; 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.
- legacy GET /latest-games (listLatestGames; 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.
- legacy GET /offers/latest-released (listLatestReleasedOffers; 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.
- legacy GET /free-games/mobile (listMobileFreeGames; 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.
- legacy GET /offers/{id}/achievements (listOfferAchievements; 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.
- legacy GET /offers/{id}/assets (listOfferAssets; 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.
- legacy GET /offers/{id}/builds (listOfferBuilds; 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.
- legacy GET /offers/{id}/changelog (listOfferChangelog; 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.
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; 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.
- legacy GET /offers/{id}/genres (listOfferDetailGenres; 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.
- legacy GET /offers/events (listOfferEvents; 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.
- legacy GET /offers/{id}/franchises (listOfferFranchises; 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.
- legacy GET /offers/genres (listOfferGenres; 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.
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; 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.
- legacy GET /offers/{id}/items (listOfferItems; 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.
- legacy GET /offers/{id}/reviews (listOfferReviews; 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.
- legacy GET /offers (listOffers; 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.
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; 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.
- legacy GET /offers/{id}/technologies (listOfferTechnologies; 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.
- legacy GET /regions (listRegions; 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.
- legacy GET /offers/{id}/related (listRelatedOffers; 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.
- legacy GET /sales (listSaleOffers; 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.
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; 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.
- legacy GET /sandboxes (listSandboxes; 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.
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; 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.
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- legacy GET /search/developers (listSearchDevelopers; 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.
- legacy GET /search/offer-types (listSearchOfferTypes; 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.
- legacy GET /search/publishers (listSearchPublishers; 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.
- legacy GET /search/tags (listSearchTags; 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.
- legacy GET /sellers/{id} (listSellerOffers; 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.
- legacy GET /sellers (listSellers; 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.
- legacy GET /offers/top-sellers (listTopSellersOffers; 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.
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; 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.
- legacy GET /offers/upcoming (listUpcomingOffers; 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.
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; 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.
- legacy POST /offers/slugs (resolveOfferSlugs; 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.
- legacy GET /search/changelog (searchChangelog; 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.
- legacy GET /free-games/search (searchFreeGames; 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.
- legacy POST /search (searchOffersLegacy; 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.
- legacy POST /search/v2/search (searchOffersV2; 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.
- legacy GET /search/v2/search (searchOffersV2Get; 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.
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; 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.
- v1 GET /v1/autocomplete (autocomplete; 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.
- v1 POST /v1/offers/exists (checkOfferExistence; 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.
- v1 POST /v1/offers/slugs (checkOfferSlugs; 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.
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- v1 GET /v1/assets/{id} (getAsset; 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.
- v1 GET /v1/base-game/{namespace} (getBaseGame; 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.
- v1 GET /v1/builds/{id} (getBuild; 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.
- v1 GET /v1/builds/{id}/history (getBuildHistory; 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.
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; 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.
- v1 GET /v1/builds/{id}/tree (getBuildTree; 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.
- v1 GET /v1/changelist/{id} (getChangelogEntry; 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.
- v1 GET /v1/collections/{slug} (getCollection; 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.
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; 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.
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; 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.
- v1 GET /v1/featured (getFeaturedGames; 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.
- v1 GET /v1/franchises/{slug} (getFranchise; 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.
- v1 GET /v1/free-games/og (getFreeGamesOg; 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.
- v1 GET /v1/free-games/stats (getFreeGamesStats; 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.
- v1 GET /v1/game-awards (getGameAwards; 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.
- v1 GET /v1/game-awards/og (getGameAwardsOg; 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.
- v1 GET /v1/stats/homepage (getHomepageStats; 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.
- v1 GET /v1/items/{id} (getItem; 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.
- v1 GET /v1/items/{id}/assets (getItemAssets; 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.
- v1 GET /v1/items/{id}/builds (getItemBuilds; 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.
- v1 GET /v1/items/{id}/changelog (getItemChangelog; 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.
- v1 GET /v1/items/{id}/offer (getItemOffer; 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.
- v1 POST /v1/items/bulk (getItemsBulk; 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.
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; 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.
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; 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.
- v1 GET /v1/latest-games (getLatestGames; 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.
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; 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.
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; 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.
- v1 GET /v1/offers/{id} (getOffer; 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.
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; 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.
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; 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.
- v1 GET /v1/offers/{id}/assets (getOfferAssets; 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.
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; 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.
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; 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.
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; 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.
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- v1 GET /v1/offers/{id}/collection (getOfferCollection; 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.
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; 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.
- v1 GET /v1/offers/events/{id} (getOfferEvent; 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.
- v1 GET /v1/offers/{id}/features (getOfferFeatures; 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.
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; 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.
- v1 GET /v1/offers/{id}/genres (getOfferGenres; 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.
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; 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.
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; 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.
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; 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.
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; 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.
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; 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.
- v1 GET /v1/offers/{id}/items (getOfferItems; 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.
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; 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.
- v1 GET /v1/offers/{id}/media (getOfferMedia; 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.
- v1 GET /v1/offers/{id}/og (getOfferOg; 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.
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; 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.
- v1 GET /v1/offers/{id}/overview (getOfferOverview; 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.
- v1 GET /v1/offers/{id}/polls (getOfferPolls; 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.
- v1 GET /v1/offers/{id}/price (getOfferPrice; 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.
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; 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.
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; 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.
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; 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.
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; 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.
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; 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.
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; 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.
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; 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.
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; 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.
- v1 GET /v1/offers/{id}/tops (getOfferTops; 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.
- v1 GET /v1/profiles/{id} (getProfile; 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.
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/information (getProfileInformation; 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.
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; 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.
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; 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.
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; 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.
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; 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.
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; 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.
- v1 GET /v1/region (getRegion; 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.
- v1 GET /v1/offers/{id}/related (getRelatedOffers; 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.
- v1 GET /v1/robots.txt (getRobots; 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.
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; 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.
- v1 GET /v1/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.
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; 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.
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- v1 GET /v1/search/{id} (getSearchQuery; 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.
- v1 GET /v1/search/{id}/count (getSearchQueryCount; 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.
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; 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.
- v1 GET /v1/sellers/{id}/stats (getSellerStats; 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.
- v1 GET /v1/sitemap.xml (getSitemap; 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.
- v1 GET /v1/stats (getStats; 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.
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; 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.
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; 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.
- v1 POST /v1/catalog/hydrate (hydrateCatalog; 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.
- v1 GET /v1/active-sales (listActiveSales; 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.
- v1 GET /v1/builds/{id}/files (listBuildFiles; 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.
- v1 GET /v1/builds/{id}/items (listBuildItems; 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.
- v1 GET /v1/builds (listBuilds; 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.
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- v1 GET /v1/changelist (listChangelist; 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.
- v1 GET /v1/changelog (listChangelog; 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.
- v1 GET /v1/countries (listCountries; 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.
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; 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.
- v1 GET /v1/free-games (listFreeGames; 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.
- v1 GET /v1/free-games/sellers (listFreeGameSellers; 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.
- v1 GET /v1/free-games/history (listFreeGamesHistory; 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.
- v1 GET /v1/items (listItems; 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.
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; 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.
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; 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.
- v1 GET /v1/offers/latest-released (listLatestReleased; 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.
- v1 GET /v1/free-games/mobile (listMobileFreeGames; 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.
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; 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.
- v1 GET /v1/offers/events (listOfferEvents; 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.
- v1 GET /v1/offers/genres (listOfferGenres; 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.
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; 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.
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; 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.
- v1 GET /v1/offers (listOffers; 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.
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/games (listProfileGames; 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.
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; 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.
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; 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.
- v1 GET /v1/promotions/{id} (listPromotionOffers; 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.
- v1 GET /v1/promotions (listPromotions; 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.
- v1 GET /v1/regions (listRegions; 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.
- v1 GET /v1/sales (listSales; 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.
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- v1 GET /v1/sandboxes (listSandboxes; 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.
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; 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.
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- v1 GET /v1/search/developers (listSearchDevelopers; 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.
- v1 GET /v1/search/offer-types (listSearchOfferTypes; 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.
- v1 GET /v1/search/publishers (listSearchPublishers; 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.
- v1 GET /v1/search/tags (listSearchTags; 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.
- v1 GET /v1/sellers/{id} (listSellerOffers; 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.
- v1 GET /v1/sellers (listSellers; 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.
- v1 GET /v1/tags (listTags; 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.
- v1 GET /v1/offers/top-sellers (listTopSellers; 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.
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; 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.
- v1 GET /v1/offers/upcoming (listUpcomingOffers; 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.
- v1 GET /v1/multisearch/items (multisearchItems; 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.
- v1 GET /v1/multisearch/offers (multisearchOffers; 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.
- v1 GET /v1/multisearch/sellers (multisearchSellers; 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.
- v1 POST /v1/search/natural-language (naturalLanguageSearch; 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.
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; 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.
- v1 GET /v1/search/changelog (searchChangelog; 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.
- v1 GET /v1/free-games/search (searchFreeGames; 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.
- v1 GET /v1/search (searchOffers; 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.
- v1 POST /v1/search (searchOffersRedirect; 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 — Report email verification before terms acceptance in dashboard and console onboarding
Record: developer-onboarding-error-order.
- v1 GET /v1/autocomplete (autocomplete; 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.
- v1 POST /v1/offers/exists (checkOfferExistence; 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.
- v1 POST /v1/offers/slugs (checkOfferSlugs; 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.
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- v1 GET /v1/assets/{id} (getAsset; 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.
- v1 GET /v1/base-game/{namespace} (getBaseGame; 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.
- v1 GET /v1/builds/{id} (getBuild; 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.
- v1 GET /v1/builds/{id}/history (getBuildHistory; 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.
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; 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.
- v1 GET /v1/builds/{id}/tree (getBuildTree; 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.
- v1 GET /v1/changelist/{id} (getChangelogEntry; 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.
- v1 GET /v1/collections/{slug} (getCollection; 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.
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; 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.
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; 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.
- v1 GET /v1/featured (getFeaturedGames; 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.
- v1 GET /v1/franchises/{slug} (getFranchise; 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.
- v1 GET /v1/free-games/og (getFreeGamesOg; 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.
- v1 GET /v1/free-games/stats (getFreeGamesStats; 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.
- v1 GET /v1/game-awards (getGameAwards; 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.
- v1 GET /v1/game-awards/og (getGameAwardsOg; 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.
- 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.
- v1 GET /v1/stats/homepage (getHomepageStats; 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.
- v1 GET /v1/items/{id} (getItem; 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.
- v1 GET /v1/items/{id}/assets (getItemAssets; 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.
- v1 GET /v1/items/{id}/builds (getItemBuilds; 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.
- v1 GET /v1/items/{id}/changelog (getItemChangelog; 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.
- v1 GET /v1/items/{id}/offer (getItemOffer; 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.
- v1 POST /v1/items/bulk (getItemsBulk; 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.
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; 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.
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; 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.
- v1 GET /v1/latest-games (getLatestGames; 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.
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; 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.
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; 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.
- v1 GET /v1/offers/{id} (getOffer; 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.
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; 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.
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; 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.
- v1 GET /v1/offers/{id}/assets (getOfferAssets; 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.
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; 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.
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; 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.
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; 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.
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- v1 GET /v1/offers/{id}/collection (getOfferCollection; 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.
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; 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.
- v1 GET /v1/offers/events/{id} (getOfferEvent; 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.
- v1 GET /v1/offers/{id}/features (getOfferFeatures; 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.
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; 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.
- v1 GET /v1/offers/{id}/genres (getOfferGenres; 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.
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; 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.
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; 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.
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; 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.
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; 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.
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; 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.
- v1 GET /v1/offers/{id}/items (getOfferItems; 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.
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; 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.
- v1 GET /v1/offers/{id}/media (getOfferMedia; 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.
- v1 GET /v1/offers/{id}/og (getOfferOg; 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.
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; 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.
- v1 GET /v1/offers/{id}/overview (getOfferOverview; 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.
- v1 GET /v1/offers/{id}/polls (getOfferPolls; 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.
- v1 GET /v1/offers/{id}/price (getOfferPrice; 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.
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; 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.
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; 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.
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; 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.
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; 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.
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; 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.
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; 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.
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; 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.
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; 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.
- v1 GET /v1/offers/{id}/tops (getOfferTops; 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.
- v1 GET /v1/profiles/{id} (getProfile; 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.
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/information (getProfileInformation; 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.
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; 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.
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; 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.
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; 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.
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; 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.
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; 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.
- v1 GET /v1/region (getRegion; 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.
- v1 GET /v1/offers/{id}/related (getRelatedOffers; 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.
- v1 GET /v1/robots.txt (getRobots; 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.
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; 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.
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; 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.
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; 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.
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- v1 GET /v1/search/{id} (getSearchQuery; 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.
- v1 GET /v1/search/{id}/count (getSearchQueryCount; 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.
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; 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.
- v1 GET /v1/sellers/{id}/stats (getSellerStats; 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.
- v1 GET /v1/sitemap.xml (getSitemap; 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.
- v1 GET /v1/stats (getStats; 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.
- v1 GET /v1/open-api.json (getV1OpenApi; 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.
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; 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.
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; 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.
- v1 POST /v1/catalog/hydrate (hydrateCatalog; 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.
- v1 GET /v1/active-sales (listActiveSales; 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.
- v1 GET /v1/builds/{id}/files (listBuildFiles; 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.
- v1 GET /v1/builds/{id}/items (listBuildItems; 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.
- v1 GET /v1/builds (listBuilds; 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.
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- v1 GET /v1/changelist (listChangelist; 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.
- v1 GET /v1/changelog (listChangelog; 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.
- v1 GET /v1/countries (listCountries; 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.
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; 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.
- v1 GET /v1/free-games (listFreeGames; 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.
- v1 GET /v1/free-games/sellers (listFreeGameSellers; 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.
- v1 GET /v1/free-games/history (listFreeGamesHistory; 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.
- v1 GET /v1/items (listItems; 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.
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; 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.
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; 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.
- v1 GET /v1/offers/latest-released (listLatestReleased; 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.
- v1 GET /v1/free-games/mobile (listMobileFreeGames; 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.
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; 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.
- v1 GET /v1/offers/events (listOfferEvents; 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.
- v1 GET /v1/offers/genres (listOfferGenres; 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.
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; 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.
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; 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.
- v1 GET /v1/offers (listOffers; 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.
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/games (listProfileGames; 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.
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; 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.
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; 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.
- v1 GET /v1/promotions/{id} (listPromotionOffers; 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.
- v1 GET /v1/promotions (listPromotions; 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.
- v1 GET /v1/regions (listRegions; 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.
- v1 GET /v1/sales (listSales; 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.
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- v1 GET /v1/sandboxes (listSandboxes; 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.
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; 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.
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- v1 GET /v1/search/developers (listSearchDevelopers; 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.
- v1 GET /v1/search/offer-types (listSearchOfferTypes; 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.
- v1 GET /v1/search/publishers (listSearchPublishers; 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.
- v1 GET /v1/search/tags (listSearchTags; 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.
- v1 GET /v1/sellers/{id} (listSellerOffers; 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.
- v1 GET /v1/sellers (listSellers; 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.
- v1 GET /v1/tags (listTags; 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.
- v1 GET /v1/offers/top-sellers (listTopSellers; 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.
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; 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.
- v1 GET /v1/offers/upcoming (listUpcomingOffers; 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.
- v1 GET /v1/multisearch/items (multisearchItems; 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.
- v1 GET /v1/multisearch/offers (multisearchOffers; 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.
- v1 GET /v1/multisearch/sellers (multisearchSellers; 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.
- v1 POST /v1/search/natural-language (naturalLanguageSearch; 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.
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; 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.
- v1 GET /v1/search/changelog (searchChangelog; 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.
- v1 GET /v1/free-games/search (searchFreeGames; 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.
- v1 GET /v1/search (searchOffers; 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.
- v1 POST /v1/search (searchOffersRedirect; 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 — Enforce shared 100,000 requests/month allowance across free account projects
Record: free-account-monthly-quota.
- legacy GET /autocomplete (autocompleteOffers; 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.
- legacy POST /offers/exists (checkOffersExist; 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.
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- legacy GET /search/{id}/count (countSavedSearchResults; 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.
- legacy GET /builds/{id} (getBuild; 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.
- legacy GET /builds/{id}/tree (getBuildFileTree; 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.
- legacy GET /builds/{id}/history (getBuildHistory; 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.
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; 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.
- legacy GET /changelist/{id} (getChangelistEntry; 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.
- legacy GET /free-games (getFreeGames; 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.
- legacy GET /free-games/stats (getFreeGamesStats; 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.
- legacy GET /stats/homepage (getHomepageStats; 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.
- legacy GET /items/{id} (getItem; 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.
- legacy GET /items/{id}/assets (getItemAssets; 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.
- legacy GET /items/{id}/builds (getItemBuilds; 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.
- legacy GET /items/{id}/changelog (getItemChangelog; 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.
- legacy GET /items/{id}/offer (getItemOffer; 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.
- legacy POST /items/bulk (getItemsBulk; 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.
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; 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.
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; 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.
- legacy GET /offers/{id} (getOffer; 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.
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; 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.
- legacy GET /offers/{id}/bundle (getOfferBundle; 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.
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; 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.
- legacy GET /offers/events/{id} (getOfferEvent; 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.
- legacy GET /offers/{id}/features (getOfferFeatures; 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.
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; 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.
- legacy GET /offers/{id}/igdb (getOfferIgdb; 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.
- legacy GET /offers/{id}/mappings (getOfferMappings; 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.
- legacy GET /offers/{id}/media (getOfferMedia; 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.
- legacy GET /offers/{id}/og (getOfferOgPng; 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.
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; 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.
- legacy GET /offers/{id}/overview (getOfferOverview; 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.
- legacy GET /offers/{id}/polls (getOfferPolls; 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.
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; 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.
- legacy GET /offers/{id}/price (getOfferPrice; 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.
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; 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.
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; 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.
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; 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.
- legacy GET /offers/{id}/ratings (getOfferRatings; 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.
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; 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.
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; 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.
- legacy GET /offers/{id}/requirements (getOfferRequirements; 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.
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- legacy POST /items/bulk/offers (getOffersForItemsBulk; 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.
- legacy GET /offers/{id}/tops (getOfferTopPositions; 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.
- legacy GET /region (getRegionForCountry; 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.
- legacy GET /sandboxes/{sandboxId} (getSandbox; 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.
- 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.
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; 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.
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- legacy GET /search/{id} (getSavedSearchQuery; 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.
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; 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.
- legacy GET /sellers/{id}/stats (getSellerStats; 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.
- legacy GET /stats (getStats; 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.
- legacy GET /stats/creations/yearly (getYearlyCreationStats; 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.
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; 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.
- legacy POST /catalog/hydrate (hydrateCatalogGraph; 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.
- legacy GET / (legacyGet__c767025d; 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.
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; 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.
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; 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.
- legacy GET /changelog (legacyGet_changelog_038722cc; 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.
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; 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.
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; 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.
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; 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.
- legacy GET /doc (legacyGet_doc_f5f543a0; 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.
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; 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.
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; 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.
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; 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.
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; 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.
- legacy GET /graphql (legacyGet_graphql_220e6fb1; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; 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.
- legacy GET /multisearch (legacyGet_multisearch_229582ca; 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.
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; 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.
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; 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.
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; 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.
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; 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.
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; 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.
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; 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.
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; 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.
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; 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.
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; 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.
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; 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.
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; 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.
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; 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.
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; 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.
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; 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.
- legacy GET /promotions (legacyGet_promotions_83dd267d; 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.
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; 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.
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; 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.
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; 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.
- legacy GET /search (legacyGet_search_82dab022; 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.
- legacy GET /tags (legacyGet_tags_803dea8c; 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.
- legacy POST /graphql (legacyPost_graphql_fac042a8; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- legacy GET /active-sales (listActiveSales; 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.
- legacy GET /builds/{id}/files (listBuildFiles; 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.
- legacy GET /builds/{id}/items (listBuildItems; 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.
- legacy GET /builds (listBuilds; 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.
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- legacy GET /changelist (listChangelist; 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.
- legacy GET /countries (listCountries; 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.
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; 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.
- legacy GET /featured (listFeaturedGames; 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.
- legacy GET /free-games/history (listFreeGamesHistory; 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.
- legacy GET /free-games/sellers (listFreeGamesSellers; 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.
- legacy GET /items (listItems; 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.
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; 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.
- legacy GET /latest-games (listLatestGames; 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.
- legacy GET /offers/latest-released (listLatestReleasedOffers; 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.
- legacy GET /free-games/mobile (listMobileFreeGames; 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.
- legacy GET /offers/{id}/achievements (listOfferAchievements; 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.
- legacy GET /offers/{id}/assets (listOfferAssets; 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.
- legacy GET /offers/{id}/builds (listOfferBuilds; 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.
- legacy GET /offers/{id}/changelog (listOfferChangelog; 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.
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; 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.
- legacy GET /offers/{id}/genres (listOfferDetailGenres; 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.
- legacy GET /offers/events (listOfferEvents; 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.
- legacy GET /offers/{id}/franchises (listOfferFranchises; 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.
- legacy GET /offers/genres (listOfferGenres; 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.
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; 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.
- legacy GET /offers/{id}/items (listOfferItems; 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.
- legacy GET /offers/{id}/reviews (listOfferReviews; 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.
- legacy GET /offers (listOffers; 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.
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; 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.
- legacy GET /offers/{id}/technologies (listOfferTechnologies; 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.
- legacy GET /regions (listRegions; 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.
- legacy GET /offers/{id}/related (listRelatedOffers; 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.
- legacy GET /sales (listSaleOffers; 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.
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; 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.
- legacy GET /sandboxes (listSandboxes; 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.
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; 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.
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- legacy GET /search/developers (listSearchDevelopers; 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.
- legacy GET /search/offer-types (listSearchOfferTypes; 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.
- legacy GET /search/publishers (listSearchPublishers; 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.
- legacy GET /search/tags (listSearchTags; 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.
- legacy GET /sellers/{id} (listSellerOffers; 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.
- legacy GET /sellers (listSellers; 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.
- legacy GET /offers/top-sellers (listTopSellersOffers; 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.
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; 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.
- legacy GET /offers/upcoming (listUpcomingOffers; 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.
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; 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.
- legacy POST /offers/slugs (resolveOfferSlugs; 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.
- legacy GET /search/changelog (searchChangelog; 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.
- legacy GET /free-games/search (searchFreeGames; 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.
- legacy POST /search (searchOffersLegacy; 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.
- legacy POST /search/v2/search (searchOffersV2; 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.
- legacy GET /search/v2/search (searchOffersV2Get; 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.
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; 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.
- v1 GET /v1/autocomplete (autocomplete; 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.
- v1 POST /v1/offers/exists (checkOfferExistence; 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.
- v1 POST /v1/offers/slugs (checkOfferSlugs; 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.
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- v1 GET /v1/assets/{id} (getAsset; 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.
- v1 GET /v1/base-game/{namespace} (getBaseGame; 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.
- v1 GET /v1/builds/{id} (getBuild; 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.
- v1 GET /v1/builds/{id}/history (getBuildHistory; 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.
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; 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.
- v1 GET /v1/builds/{id}/tree (getBuildTree; 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.
- v1 GET /v1/changelist/{id} (getChangelogEntry; 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.
- v1 GET /v1/collections/{slug} (getCollection; 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.
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; 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.
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; 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.
- v1 GET /v1/featured (getFeaturedGames; 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.
- v1 GET /v1/franchises/{slug} (getFranchise; 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.
- v1 GET /v1/free-games/og (getFreeGamesOg; 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.
- v1 GET /v1/free-games/stats (getFreeGamesStats; 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.
- v1 GET /v1/game-awards (getGameAwards; 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.
- v1 GET /v1/game-awards/og (getGameAwardsOg; 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.
- v1 GET /v1/stats/homepage (getHomepageStats; 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.
- v1 GET /v1/items/{id} (getItem; 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.
- v1 GET /v1/items/{id}/assets (getItemAssets; 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.
- v1 GET /v1/items/{id}/builds (getItemBuilds; 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.
- v1 GET /v1/items/{id}/changelog (getItemChangelog; 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.
- v1 GET /v1/items/{id}/offer (getItemOffer; 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.
- v1 POST /v1/items/bulk (getItemsBulk; 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.
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; 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.
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; 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.
- v1 GET /v1/latest-games (getLatestGames; 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.
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; 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.
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; 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.
- v1 GET /v1/offers/{id} (getOffer; 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.
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; 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.
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; 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.
- v1 GET /v1/offers/{id}/assets (getOfferAssets; 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.
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; 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.
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; 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.
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; 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.
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- v1 GET /v1/offers/{id}/collection (getOfferCollection; 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.
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; 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.
- v1 GET /v1/offers/events/{id} (getOfferEvent; 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.
- v1 GET /v1/offers/{id}/features (getOfferFeatures; 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.
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; 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.
- v1 GET /v1/offers/{id}/genres (getOfferGenres; 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.
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; 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.
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; 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.
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; 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.
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; 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.
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; 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.
- v1 GET /v1/offers/{id}/items (getOfferItems; 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.
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; 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.
- v1 GET /v1/offers/{id}/media (getOfferMedia; 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.
- v1 GET /v1/offers/{id}/og (getOfferOg; 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.
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; 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.
- v1 GET /v1/offers/{id}/overview (getOfferOverview; 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.
- v1 GET /v1/offers/{id}/polls (getOfferPolls; 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.
- v1 GET /v1/offers/{id}/price (getOfferPrice; 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.
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; 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.
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; 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.
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; 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.
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; 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.
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; 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.
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; 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.
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; 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.
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; 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.
- v1 GET /v1/offers/{id}/tops (getOfferTops; 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.
- v1 GET /v1/profiles/{id} (getProfile; 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.
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/information (getProfileInformation; 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.
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; 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.
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; 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.
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; 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.
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; 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.
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; 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.
- v1 GET /v1/region (getRegion; 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.
- v1 GET /v1/offers/{id}/related (getRelatedOffers; 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.
- v1 GET /v1/robots.txt (getRobots; 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.
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; 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.
- v1 GET /v1/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.
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; 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.
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- v1 GET /v1/search/{id} (getSearchQuery; 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.
- v1 GET /v1/search/{id}/count (getSearchQueryCount; 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.
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; 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.
- v1 GET /v1/sellers/{id}/stats (getSellerStats; 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.
- v1 GET /v1/sitemap.xml (getSitemap; 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.
- v1 GET /v1/stats (getStats; 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.
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; 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.
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; 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.
- v1 POST /v1/catalog/hydrate (hydrateCatalog; 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.
- v1 GET /v1/active-sales (listActiveSales; 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.
- v1 GET /v1/builds/{id}/files (listBuildFiles; 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.
- v1 GET /v1/builds/{id}/items (listBuildItems; 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.
- v1 GET /v1/builds (listBuilds; 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.
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- v1 GET /v1/changelist (listChangelist; 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.
- v1 GET /v1/changelog (listChangelog; 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.
- v1 GET /v1/countries (listCountries; 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.
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; 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.
- v1 GET /v1/free-games (listFreeGames; 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.
- v1 GET /v1/free-games/sellers (listFreeGameSellers; 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.
- v1 GET /v1/free-games/history (listFreeGamesHistory; 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.
- v1 GET /v1/items (listItems; 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.
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; 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.
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; 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.
- v1 GET /v1/offers/latest-released (listLatestReleased; 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.
- v1 GET /v1/free-games/mobile (listMobileFreeGames; 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.
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; 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.
- v1 GET /v1/offers/events (listOfferEvents; 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.
- v1 GET /v1/offers/genres (listOfferGenres; 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.
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; 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.
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; 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.
- v1 GET /v1/offers (listOffers; 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.
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/games (listProfileGames; 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.
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; 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.
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; 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.
- v1 GET /v1/promotions/{id} (listPromotionOffers; 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.
- v1 GET /v1/promotions (listPromotions; 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.
- v1 GET /v1/regions (listRegions; 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.
- v1 GET /v1/sales (listSales; 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.
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- v1 GET /v1/sandboxes (listSandboxes; 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.
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; 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.
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- v1 GET /v1/search/developers (listSearchDevelopers; 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.
- v1 GET /v1/search/offer-types (listSearchOfferTypes; 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.
- v1 GET /v1/search/publishers (listSearchPublishers; 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.
- v1 GET /v1/search/tags (listSearchTags; 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.
- v1 GET /v1/sellers/{id} (listSellerOffers; 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.
- v1 GET /v1/sellers (listSellers; 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.
- v1 GET /v1/tags (listTags; 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.
- v1 GET /v1/offers/top-sellers (listTopSellers; 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.
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; 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.
- v1 GET /v1/offers/upcoming (listUpcomingOffers; 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.
- v1 GET /v1/multisearch/items (multisearchItems; 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.
- v1 GET /v1/multisearch/offers (multisearchOffers; 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.
- v1 GET /v1/multisearch/sellers (multisearchSellers; 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.
- v1 POST /v1/search/natural-language (naturalLanguageSearch; 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.
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; 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.
- v1 GET /v1/search/changelog (searchChangelog; 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.
- v1 GET /v1/free-games/search (searchFreeGames; 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.
- v1 GET /v1/search (searchOffers; 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.
- v1 POST /v1/search (searchOffersRedirect; 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 /autocomplete (autocompleteOffers; 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.
- legacy POST /offers/exists (checkOffersExist; 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.
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- legacy GET /search/{id}/count (countSavedSearchResults; 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.
- legacy GET /builds/{id} (getBuild; 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.
- legacy GET /builds/{id}/tree (getBuildFileTree; 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.
- legacy GET /builds/{id}/history (getBuildHistory; 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.
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; 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.
- legacy GET /changelist/{id} (getChangelistEntry; 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.
- legacy GET /free-games (getFreeGames; 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.
- legacy GET /free-games/stats (getFreeGamesStats; 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.
- legacy GET /stats/homepage (getHomepageStats; 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.
- legacy GET /items/{id} (getItem; 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.
- legacy GET /items/{id}/assets (getItemAssets; 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.
- legacy GET /items/{id}/builds (getItemBuilds; 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.
- legacy GET /items/{id}/changelog (getItemChangelog; 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.
- legacy GET /items/{id}/offer (getItemOffer; 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.
- legacy POST /items/bulk (getItemsBulk; 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.
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; 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.
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; 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.
- legacy GET /offers/{id} (getOffer; 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.
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; 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.
- legacy GET /offers/{id}/bundle (getOfferBundle; 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.
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; 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.
- legacy GET /offers/events/{id} (getOfferEvent; 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.
- legacy GET /offers/{id}/features (getOfferFeatures; 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.
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; 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.
- legacy GET /offers/{id}/igdb (getOfferIgdb; 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.
- legacy GET /offers/{id}/mappings (getOfferMappings; 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.
- legacy GET /offers/{id}/media (getOfferMedia; 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.
- legacy GET /offers/{id}/og (getOfferOgPng; 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.
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; 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.
- legacy GET /offers/{id}/overview (getOfferOverview; 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.
- legacy GET /offers/{id}/polls (getOfferPolls; 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.
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; 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.
- legacy GET /offers/{id}/price (getOfferPrice; 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.
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; 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.
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; 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.
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; 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.
- legacy GET /offers/{id}/ratings (getOfferRatings; 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.
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; 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.
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; 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.
- legacy GET /offers/{id}/requirements (getOfferRequirements; 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.
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- legacy POST /items/bulk/offers (getOffersForItemsBulk; 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.
- legacy GET /offers/{id}/tops (getOfferTopPositions; 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.
- legacy GET /region (getRegionForCountry; 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.
- legacy GET /sandboxes/{sandboxId} (getSandbox; 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.
- 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.
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; 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.
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- legacy GET /search/{id} (getSavedSearchQuery; 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.
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; 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.
- legacy GET /sellers/{id}/stats (getSellerStats; 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.
- legacy GET /stats (getStats; 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.
- legacy GET /stats/creations/yearly (getYearlyCreationStats; 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.
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; 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.
- legacy POST /catalog/hydrate (hydrateCatalogGraph; 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.
- legacy GET / (legacyGet__c767025d; 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.
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; 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.
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; 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.
- legacy GET /changelog (legacyGet_changelog_038722cc; 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.
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; 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.
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; 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.
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; 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.
- legacy GET /doc (legacyGet_doc_f5f543a0; 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.
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; 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.
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; 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.
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; 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.
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; 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.
- legacy GET /graphql (legacyGet_graphql_220e6fb1; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; 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.
- legacy GET /multisearch (legacyGet_multisearch_229582ca; 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.
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; 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.
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; 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.
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; 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.
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; 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.
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; 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.
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; 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.
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; 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.
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; 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.
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; 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.
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; 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.
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; 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.
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; 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.
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; 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.
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; 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.
- legacy GET /promotions (legacyGet_promotions_83dd267d; 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.
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; 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.
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; 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.
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; 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.
- legacy GET /search (legacyGet_search_82dab022; 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.
- legacy GET /tags (legacyGet_tags_803dea8c; 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.
- legacy POST /graphql (legacyPost_graphql_fac042a8; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- legacy GET /active-sales (listActiveSales; 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.
- legacy GET /builds/{id}/files (listBuildFiles; 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.
- legacy GET /builds/{id}/items (listBuildItems; 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.
- legacy GET /builds (listBuilds; 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.
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- legacy GET /changelist (listChangelist; 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.
- legacy GET /countries (listCountries; 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.
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; 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.
- legacy GET /featured (listFeaturedGames; 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.
- legacy GET /free-games/history (listFreeGamesHistory; 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.
- legacy GET /free-games/sellers (listFreeGamesSellers; 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.
- legacy GET /items (listItems; 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.
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; 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.
- legacy GET /latest-games (listLatestGames; 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.
- legacy GET /offers/latest-released (listLatestReleasedOffers; 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.
- legacy GET /free-games/mobile (listMobileFreeGames; 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.
- legacy GET /offers/{id}/achievements (listOfferAchievements; 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.
- legacy GET /offers/{id}/assets (listOfferAssets; 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.
- legacy GET /offers/{id}/builds (listOfferBuilds; 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.
- legacy GET /offers/{id}/changelog (listOfferChangelog; 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.
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; 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.
- legacy GET /offers/{id}/genres (listOfferDetailGenres; 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.
- legacy GET /offers/events (listOfferEvents; 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.
- legacy GET /offers/{id}/franchises (listOfferFranchises; 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.
- legacy GET /offers/genres (listOfferGenres; 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.
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; 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.
- legacy GET /offers/{id}/items (listOfferItems; 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.
- legacy GET /offers/{id}/reviews (listOfferReviews; 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.
- legacy GET /offers (listOffers; 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.
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; 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.
- legacy GET /offers/{id}/technologies (listOfferTechnologies; 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.
- legacy GET /regions (listRegions; 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.
- legacy GET /offers/{id}/related (listRelatedOffers; 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.
- legacy GET /sales (listSaleOffers; 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.
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; 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.
- legacy GET /sandboxes (listSandboxes; 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.
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; 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.
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- legacy GET /search/developers (listSearchDevelopers; 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.
- legacy GET /search/offer-types (listSearchOfferTypes; 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.
- legacy GET /search/publishers (listSearchPublishers; 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.
- legacy GET /search/tags (listSearchTags; 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.
- legacy GET /sellers/{id} (listSellerOffers; 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.
- legacy GET /sellers (listSellers; 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.
- legacy GET /offers/top-sellers (listTopSellersOffers; 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.
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; 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.
- legacy GET /offers/upcoming (listUpcomingOffers; 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.
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; 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.
- legacy POST /offers/slugs (resolveOfferSlugs; 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.
- legacy GET /search/changelog (searchChangelog; 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.
- legacy GET /free-games/search (searchFreeGames; 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.
- legacy POST /search (searchOffersLegacy; 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.
- legacy POST /search/v2/search (searchOffersV2; 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.
- legacy GET /search/v2/search (searchOffersV2Get; 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.
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; 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.
- v1 GET /v1/autocomplete (autocomplete; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/offers/exists (checkOfferExistence; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/offers/slugs (checkOfferSlugs; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/assets/{id} (getAsset; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/base-game/{namespace} (getBaseGame; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds/{id} (getBuild; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds/{id}/history (getBuildHistory; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds/{id}/tree (getBuildTree; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/changelist/{id} (getChangelogEntry; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/collections/{slug} (getCollection; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/featured (getFeaturedGames; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/franchises/{slug} (getFranchise; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/free-games/og (getFreeGamesOg; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/free-games/stats (getFreeGamesStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/game-awards (getGameAwards; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/game-awards/og (getGameAwardsOg; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/stats/homepage (getHomepageStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items/{id} (getItem; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items/{id}/assets (getItemAssets; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items/{id}/builds (getItemBuilds; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items/{id}/changelog (getItemChangelog; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items/{id}/offer (getItemOffer; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/items/bulk (getItemsBulk; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/latest-games (getLatestGames; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id} (getOffer; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/assets (getOfferAssets; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/collection (getOfferCollection; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/events/{id} (getOfferEvent; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/features (getOfferFeatures; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/genres (getOfferGenres; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/items (getOfferItems; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/media (getOfferMedia; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/og (getOfferOg; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/overview (getOfferOverview; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/polls (getOfferPolls; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/price (getOfferPrice; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/tops (getOfferTops; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id} (getProfile; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id}/information (getProfileInformation; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/region (getRegion; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/related (getRelatedOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/robots.txt (getRobots; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search/{id} (getSearchQuery; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search/{id}/count (getSearchQueryCount; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sellers/{id}/stats (getSellerStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sitemap.xml (getSitemap; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/stats (getStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/catalog/hydrate (hydrateCatalog; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/active-sales (listActiveSales; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds/{id}/files (listBuildFiles; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds/{id}/items (listBuildItems; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/builds (listBuilds; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/changelist (listChangelist; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/changelog (listChangelog; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/countries (listCountries; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/free-games (listFreeGames; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/free-games/sellers (listFreeGameSellers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/free-games/history (listFreeGamesHistory; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items (listItems; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/latest-released (listLatestReleased; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/free-games/mobile (listMobileFreeGames; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/events (listOfferEvents; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/genres (listOfferGenres; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers (listOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id}/games (listProfileGames; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/promotions/{id} (listPromotionOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/promotions (listPromotions; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/regions (listRegions; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sales (listSales; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes (listSandboxes; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search/developers (listSearchDevelopers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search/offer-types (listSearchOfferTypes; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search/publishers (listSearchPublishers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search/tags (listSearchTags; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sellers/{id} (listSellerOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/sellers (listSellers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/tags (listTags; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/top-sellers (listTopSellers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/offers/upcoming (listUpcomingOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/multisearch/items (multisearchItems; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/multisearch/offers (multisearchOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/multisearch/sellers (multisearchSellers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/search/natural-language (naturalLanguageSearch; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search/changelog (searchChangelog; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/free-games/search (searchFreeGames; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 GET /v1/search (searchOffers; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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.
- v1 POST /v1/search (searchOffersRedirect; changed; breaking)
- Before: Each API key had its own exact minute quota and expensive-operation counters; console sessions had a separate project-console counter. 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 /autocomplete (autocompleteOffers; 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.
- legacy POST /offers/exists (checkOffersExist; 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.
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- legacy GET /search/{id}/count (countSavedSearchResults; 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.
- legacy POST /auth/challenge (createAbuseChallenge; 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.
- legacy GET /builds/{id} (getBuild; 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.
- legacy GET /builds/{id}/tree (getBuildFileTree; 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.
- legacy GET /builds/{id}/history (getBuildHistory; 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.
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; 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.
- legacy GET /changelist/{id} (getChangelistEntry; 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.
- legacy GET /free-games (getFreeGames; 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.
- legacy GET /free-games/stats (getFreeGamesStats; 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.
- legacy GET /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.
- legacy GET /stats/homepage (getHomepageStats; 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.
- legacy GET /items/{id} (getItem; 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.
- legacy GET /items/{id}/assets (getItemAssets; 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.
- legacy GET /items/{id}/builds (getItemBuilds; 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.
- legacy GET /items/{id}/changelog (getItemChangelog; 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.
- legacy GET /items/{id}/offer (getItemOffer; 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.
- legacy POST /items/bulk (getItemsBulk; 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.
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; 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.
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; 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.
- legacy GET /offers/{id} (getOffer; 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.
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; 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.
- legacy GET /offers/{id}/bundle (getOfferBundle; 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.
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; 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.
- legacy GET /offers/events/{id} (getOfferEvent; 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.
- legacy GET /offers/{id}/features (getOfferFeatures; 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.
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; 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.
- legacy GET /offers/{id}/igdb (getOfferIgdb; 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.
- legacy GET /offers/{id}/mappings (getOfferMappings; 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.
- legacy GET /offers/{id}/media (getOfferMedia; 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.
- legacy GET /offers/{id}/og (getOfferOgPng; 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.
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; 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.
- legacy GET /offers/{id}/overview (getOfferOverview; 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.
- legacy GET /offers/{id}/polls (getOfferPolls; 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.
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; 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.
- legacy GET /offers/{id}/price (getOfferPrice; 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.
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; 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.
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; 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.
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; 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.
- legacy GET /offers/{id}/ratings (getOfferRatings; 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.
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; 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.
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; 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.
- legacy GET /offers/{id}/requirements (getOfferRequirements; 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.
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- legacy POST /items/bulk/offers (getOffersForItemsBulk; 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.
- legacy GET /offers/{id}/tops (getOfferTopPositions; 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.
- legacy GET /region (getRegionForCountry; 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.
- legacy GET /sandboxes/{sandboxId} (getSandbox; 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.
- 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.
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; 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.
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- legacy GET /search/{id} (getSavedSearchQuery; 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.
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; 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.
- legacy GET /sellers/{id}/stats (getSellerStats; 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.
- legacy GET /stats (getStats; 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.
- legacy GET /stats/creations/yearly (getYearlyCreationStats; 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.
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; 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.
- legacy POST /catalog/hydrate (hydrateCatalogGraph; 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.
- legacy GET / (legacyGet__c767025d; 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.
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; 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.
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; 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.
- legacy GET /changelog (legacyGet_changelog_038722cc; 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.
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; 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.
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; 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.
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; 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.
- legacy GET /doc (legacyGet_doc_f5f543a0; 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.
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; 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.
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; 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.
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; 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.
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; 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.
- legacy GET /graphql (legacyGet_graphql_220e6fb1; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements, GenreResult.genre, GenreResult.offers, GenreOffer.id, GenreOffer.title, GenreOffer.image, OfferConnection.elements, OfferConnection.total, OfferConnection.page, OfferConnection.limit, OfferConnection.count, ItemConnection.elements, ItemConnection.total, ItemConnection.page, ItemConnection.limit, SandboxConnection.elements, SandboxConnection.total, SandboxConnection.page, SandboxConnection.limit, Profile.accountId, Profile.displayName, Profile.avatar, Profile.linkedAccounts, Profile.creationDate, Profile.reviewsCount, Profile.highlights, Profile.heroGame, Profile.featuredAchievements, Profile.featuredGames, Profile.recentActivity, Profile.games, Profile.achievements, ProfileAvatar.small, ProfileAvatar.medium, ProfileAvatar.large, ProfileHighlights.level, ProfileHighlights.totalXP, ProfileHighlights.totalGames, ProfileHighlights.totalAchievements, ProfileHighlights.totalPlatinums, ProfileHighlights.reviewsCount, ProfileHeroGame.sandboxId, ProfileHeroGame.title, ProfileHeroGame.imageUrl, ProfileHeroGame.completionPercent, ProfileGame.sandboxId, ProfileGame.title, ProfileGame.imageUrl, ProfileGame.completionPercent, ProfileGame.unlocked, ProfileGame.total, ProfileGame.earnedXP, ProfileGame.totalXP, ProfileGame.hasPlatinum, ProfileGame.rarestAchievements, ProfileAchievement.name, ProfileAchievement.displayName, ProfileAchievement.description, ProfileAchievement.iconUrl, ProfileAchievement.rarityPercent, ProfileAchievement.xp, ProfileAchievement.sandboxId, ProfileAchievement.gameTitle, ProfileAchievement.unlockedAt, ProfileActivityItem.type, ProfileActivityItem.sandboxId, ProfileActivityItem.gameTitle, ProfileActivityItem.achievementName, ProfileActivityItem.achievementIconUrl, ProfileActivityItem.occurredAt, ProfileGameConnection.elements, ProfileGameConnection.total, ProfileGameConnection.page, ProfileGameConnection.limit, ProfileAchievementConnection.elements, ProfileAchievementConnection.total, ProfileAchievementConnection.page, ProfileAchievementConnection.limit, OfferMappings.pageSlug, OfferMappings.pageType, OfferMappings._id, CustomAttribute.key, CustomAttribute.value, CustomAttribute.type, CustomAttribute._id, Tag.id, Tag.name, Tag.groupName, Seller.id, Seller.name, KeyImage.type, KeyImage.url, KeyImage.md5, Price.country, Price.region, Price.namespace, Price.offerId, Price.price, Price.appliedRules, Price.updatedAt, SinglePrice.currencyCode, SinglePrice.discount, SinglePrice.discountPrice, SinglePrice.originalPrice, SinglePrice.basePayoutCurrencyCode, SinglePrice.basePayoutPrice, SinglePrice.payoutCurrencyExchangeRate, AppliedRule.id, AppliedRule.name, AppliedRule.namespace, AppliedRule.promotionStatus, AppliedRule.startDate, AppliedRule.endDate, AppliedRule.saleType, AppliedRule.regionIds, Asset._id, Asset.artifactId, Asset.downloadSizeBytes, Asset.installedSizeBytes, Asset.itemId, Asset.namespace, Asset.platform, Asset.title, Asset.updatedAt, Build._id, Build.appName, Build.labelName, Build.buildVersion, Build.hash, Build.metadata, Build.downloadSizeBytes, Build.installedSizeBytes, Build.createdAt, Build.updatedAt, Build.technologies, Build.items, Build.files, Build.installOptions, FileConnection.elements, FileConnection.total, FileConnection.page, FileConnection.limit, File.fileName, File.fileSize, File.fileHash, File.manifestHash, File.depth, File.installTags, BuildMetadata.installationPoolId, Technology.section, Technology.technology, Changelog._id, Changelog.metadata, Changelog.timestamp, Changelog.document, ChangelogMetadata.contextId, ChangelogMetadata.contextType, ChangelogMetadata.changes, ChangelogChange.changeType, ChangelogChange.field, ChangelogChange.before, ChangelogChange.after, Item._id, Item.id, Item.namespace, Item.title, Item.description, Item.keyImages, Item.categories, Item.status, Item.creationDate, Item.lastModifiedDate, Item.customAttributes, Item.entitlementName, Item.entitlementType, Item.itemType, Item.releaseInfo, Item.developer, Item.developerId, Item.eulaIds, Item.endOfSupport, Item.applicationId, Item.unsearchable, Item.requiresSecureAccount, Item.offers, Item.assets, Item.builds, Item.changelog, Item.mainOffer, ItemCategory.path, ReleaseInfo.id, ReleaseInfo.appId, ReleaseInfo.platform, Sandbox._id, Sandbox.name, Sandbox.displayName, Sandbox.namespace, Sandbox.parent, Sandbox.store, Sandbox.status, Sandbox.ageGatings, Sandbox.created, Sandbox.updated, Sandbox.items, Sandbox.offers, Sandbox.assets, Sandbox.builds, Sandbox.baseGame, Sandbox.achievements, Sandbox.stats, Sandbox.changelog, SandboxHub.id, SandboxHub.namespace, SandboxHub.title, SandboxHub.description, SandboxHub.primaryKind, SandboxHub.primaryOffer, SandboxHub.primaryItem, SandboxHub.sandbox, SandboxHub.price, SandboxHub.seller, SandboxHub.developer, SandboxHub.publisher, SandboxHub.keyImages, SandboxHub.genres, SandboxHub.platforms, SandboxHub.stats, SandboxHub.featuredOffers, SandboxHub.recentBuilds, SandboxHub.recentChanges, SandboxHub.ageRating, SandboxHub.achievements, SandboxHub.created, SandboxHub.updated, SandboxAchievementSummary.sets, SandboxAchievementSummary.total, SandboxAchievementSummary.baseTotal, SandboxAchievementSummary.xp, AssetConnection.elements, AssetConnection.total, AssetConnection.page, AssetConnection.limit, AssetConnection.count, BuildConnection.elements, BuildConnection.total, BuildConnection.page, BuildConnection.limit, BuildConnection.count, SandboxStats.offers, SandboxStats.items, SandboxStats.assets, SandboxStats.builds, SandboxStats.achievements, AchievementSet._id, AchievementSet.sandboxId, AchievementSet.isBase, AchievementSet.achievements, Achievement.id, Achievement.name, Achievement.description, Achievement.unlockedIcon, Achievement.lockedIcon, Achievement.rarity, Achievement.score, Franchise._id, Franchise.id, Franchise.name, Franchise.offers, Franchise.allOffers, Giveaway._id, Giveaway.id, Giveaway.namespace, Giveaway.startDate, Giveaway.endDate, Poll._id, Poll.options, PollOption.id, PollOption.name, PollOption.votes, Rating._id, Rating.overallScore, Rating.recommendedPercentage, Rating.totalReviews, Hltb._id, Hltb.hltbId, Hltb.name, Hltb.main, Hltb.mainExtra, Hltb.completionist, Offer._id, Offer.id, Offer.namespace, Offer.title, Offer.description, Offer.longDescription, Offer.offerType, Offer.effectiveDate, Offer.creationDate, Offer.lastModifiedDate, Offer.isCodeRedemptionOnly, Offer.productSlug, Offer.urlSlug, Offer.url, Offer.developerDisplayName, Offer.publisherDisplayName, Offer.prePurchase, Offer.releaseDate, Offer.pcReleaseDate, Offer.expiryDate, Offer.viewableDate, Offer.countriesBlacklist, Offer.countriesWhitelist, Offer.refundType, Offer.offerMappings, Offer.categories, Offer.customAttributes, Offer.items, Offer.tags, Offer.seller, Offer.keyImages, Offer.price, Offer.changelog, Offer.franchises, Offer.giveaways, Offer.related, Offer.suggestions, Offer.ratings, Offer.polls, Offer.hltb, Offer.sandbox, Offer.positions, Offer.ageRating, Offer.features, Offer.locale, Offer.localeStatus, Offer.canonicalLocale, Offer.localization, OfferLocalizationMetadata.source, OfferLocalizationMetadata.fetchedAt, OfferLocalizationMetadata.sourceUpdatedAt, OfferFeatures.launcher, OfferFeatures.features, OfferFeatures.epicFeatures, ChangelogConnection.elements, ChangelogConnection.totalCount, ChangelogConnection.totalPages, ChangelogConnection.hasNextPage, ChangelogConnection.hasPreviousPage
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; 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.
- legacy GET /items/sitemap.xml (legacyGet_items_sitemap_xml_57b8dd19; 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.
- legacy GET /items-sitemap.xml (legacyGet_items_sitemap_xml_e6f8185b; 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.
- legacy GET /multisearch (legacyGet_multisearch_229582ca; 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.
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; 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.
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; 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.
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; 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.
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; 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.
- 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.
- legacy GET /ping (legacyGet_ping_f7c2b7c6; 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.
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; 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.
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; 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.
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; 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.
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; 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.
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; 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.
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; 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.
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; 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.
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; 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.
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; 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.
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; 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.
- legacy GET /profiles/sitemap.xml (legacyGet_profiles_sitemap_xml_0e16a159; 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.
- legacy GET /promotions (legacyGet_promotions_83dd267d; 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.
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; 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.
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; 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.
- legacy GET /promotions-sitemap.xml (legacyGet_promotions_sitemap_xml_3578dc8e; 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.
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; 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.
- legacy GET /robots.txt (legacyGet_robots_txt_deae90bd; 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.
- legacy GET /sandboxes/sitemap.xml (legacyGet_sandboxes_sitemap_xml_5773ff84; 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.
- legacy GET /search (legacyGet_search_82dab022; 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.
- legacy GET /sitemap.xml (legacyGet_sitemap_xml_efe3322f; 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.
- legacy GET /tags (legacyGet_tags_803dea8c; 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.
- legacy GET /ui (legacyGet_ui_64976efd; 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.
- legacy OPTIONS /ping (legacyOptions_ping_9143aa8e; 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.
- legacy POST /graphql (legacyPost_graphql_fac042a8; 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.
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements, GenreResult.genre, GenreResult.offers, GenreOffer.id, GenreOffer.title, GenreOffer.image, OfferConnection.elements, OfferConnection.total, OfferConnection.page, OfferConnection.limit, OfferConnection.count, ItemConnection.elements, ItemConnection.total, ItemConnection.page, ItemConnection.limit, SandboxConnection.elements, SandboxConnection.total, SandboxConnection.page, SandboxConnection.limit, Profile.accountId, Profile.displayName, Profile.avatar, Profile.linkedAccounts, Profile.creationDate, Profile.reviewsCount, Profile.highlights, Profile.heroGame, Profile.featuredAchievements, Profile.featuredGames, Profile.recentActivity, Profile.games, Profile.achievements, ProfileAvatar.small, ProfileAvatar.medium, ProfileAvatar.large, ProfileHighlights.level, ProfileHighlights.totalXP, ProfileHighlights.totalGames, ProfileHighlights.totalAchievements, ProfileHighlights.totalPlatinums, ProfileHighlights.reviewsCount, ProfileHeroGame.sandboxId, ProfileHeroGame.title, ProfileHeroGame.imageUrl, ProfileHeroGame.completionPercent, ProfileGame.sandboxId, ProfileGame.title, ProfileGame.imageUrl, ProfileGame.completionPercent, ProfileGame.unlocked, ProfileGame.total, ProfileGame.earnedXP, ProfileGame.totalXP, ProfileGame.hasPlatinum, ProfileGame.rarestAchievements, ProfileAchievement.name, ProfileAchievement.displayName, ProfileAchievement.description, ProfileAchievement.iconUrl, ProfileAchievement.rarityPercent, ProfileAchievement.xp, ProfileAchievement.sandboxId, ProfileAchievement.gameTitle, ProfileAchievement.unlockedAt, ProfileActivityItem.type, ProfileActivityItem.sandboxId, ProfileActivityItem.gameTitle, ProfileActivityItem.achievementName, ProfileActivityItem.achievementIconUrl, ProfileActivityItem.occurredAt, ProfileGameConnection.elements, ProfileGameConnection.total, ProfileGameConnection.page, ProfileGameConnection.limit, ProfileAchievementConnection.elements, ProfileAchievementConnection.total, ProfileAchievementConnection.page, ProfileAchievementConnection.limit, OfferMappings.pageSlug, OfferMappings.pageType, OfferMappings._id, CustomAttribute.key, CustomAttribute.value, CustomAttribute.type, CustomAttribute._id, Tag.id, Tag.name, Tag.groupName, Seller.id, Seller.name, KeyImage.type, KeyImage.url, KeyImage.md5, Price.country, Price.region, Price.namespace, Price.offerId, Price.price, Price.appliedRules, Price.updatedAt, SinglePrice.currencyCode, SinglePrice.discount, SinglePrice.discountPrice, SinglePrice.originalPrice, SinglePrice.basePayoutCurrencyCode, SinglePrice.basePayoutPrice, SinglePrice.payoutCurrencyExchangeRate, AppliedRule.id, AppliedRule.name, AppliedRule.namespace, AppliedRule.promotionStatus, AppliedRule.startDate, AppliedRule.endDate, AppliedRule.saleType, AppliedRule.regionIds, Asset._id, Asset.artifactId, Asset.downloadSizeBytes, Asset.installedSizeBytes, Asset.itemId, Asset.namespace, Asset.platform, Asset.title, Asset.updatedAt, Build._id, Build.appName, Build.labelName, Build.buildVersion, Build.hash, Build.metadata, Build.downloadSizeBytes, Build.installedSizeBytes, Build.createdAt, Build.updatedAt, Build.technologies, Build.items, Build.files, Build.installOptions, FileConnection.elements, FileConnection.total, FileConnection.page, FileConnection.limit, File.fileName, File.fileSize, File.fileHash, File.manifestHash, File.depth, File.installTags, BuildMetadata.installationPoolId, Technology.section, Technology.technology, Changelog._id, Changelog.metadata, Changelog.timestamp, Changelog.document, ChangelogMetadata.contextId, ChangelogMetadata.contextType, ChangelogMetadata.changes, ChangelogChange.changeType, ChangelogChange.field, ChangelogChange.before, ChangelogChange.after, Item._id, Item.id, Item.namespace, Item.title, Item.description, Item.keyImages, Item.categories, Item.status, Item.creationDate, Item.lastModifiedDate, Item.customAttributes, Item.entitlementName, Item.entitlementType, Item.itemType, Item.releaseInfo, Item.developer, Item.developerId, Item.eulaIds, Item.endOfSupport, Item.applicationId, Item.unsearchable, Item.requiresSecureAccount, Item.offers, Item.assets, Item.builds, Item.changelog, Item.mainOffer, ItemCategory.path, ReleaseInfo.id, ReleaseInfo.appId, ReleaseInfo.platform, Sandbox._id, Sandbox.name, Sandbox.displayName, Sandbox.namespace, Sandbox.parent, Sandbox.store, Sandbox.status, Sandbox.ageGatings, Sandbox.created, Sandbox.updated, Sandbox.items, Sandbox.offers, Sandbox.assets, Sandbox.builds, Sandbox.baseGame, Sandbox.achievements, Sandbox.stats, Sandbox.changelog, SandboxHub.id, SandboxHub.namespace, SandboxHub.title, SandboxHub.description, SandboxHub.primaryKind, SandboxHub.primaryOffer, SandboxHub.primaryItem, SandboxHub.sandbox, SandboxHub.price, SandboxHub.seller, SandboxHub.developer, SandboxHub.publisher, SandboxHub.keyImages, SandboxHub.genres, SandboxHub.platforms, SandboxHub.stats, SandboxHub.featuredOffers, SandboxHub.recentBuilds, SandboxHub.recentChanges, SandboxHub.ageRating, SandboxHub.achievements, SandboxHub.created, SandboxHub.updated, SandboxAchievementSummary.sets, SandboxAchievementSummary.total, SandboxAchievementSummary.baseTotal, SandboxAchievementSummary.xp, AssetConnection.elements, AssetConnection.total, AssetConnection.page, AssetConnection.limit, AssetConnection.count, BuildConnection.elements, BuildConnection.total, BuildConnection.page, BuildConnection.limit, BuildConnection.count, SandboxStats.offers, SandboxStats.items, SandboxStats.assets, SandboxStats.builds, SandboxStats.achievements, AchievementSet._id, AchievementSet.sandboxId, AchievementSet.isBase, AchievementSet.achievements, Achievement.id, Achievement.name, Achievement.description, Achievement.unlockedIcon, Achievement.lockedIcon, Achievement.rarity, Achievement.score, Franchise._id, Franchise.id, Franchise.name, Franchise.offers, Franchise.allOffers, Giveaway._id, Giveaway.id, Giveaway.namespace, Giveaway.startDate, Giveaway.endDate, Poll._id, Poll.options, PollOption.id, PollOption.name, PollOption.votes, Rating._id, Rating.overallScore, Rating.recommendedPercentage, Rating.totalReviews, Hltb._id, Hltb.hltbId, Hltb.name, Hltb.main, Hltb.mainExtra, Hltb.completionist, Offer._id, Offer.id, Offer.namespace, Offer.title, Offer.description, Offer.longDescription, Offer.offerType, Offer.effectiveDate, Offer.creationDate, Offer.lastModifiedDate, Offer.isCodeRedemptionOnly, Offer.productSlug, Offer.urlSlug, Offer.url, Offer.developerDisplayName, Offer.publisherDisplayName, Offer.prePurchase, Offer.releaseDate, Offer.pcReleaseDate, Offer.expiryDate, Offer.viewableDate, Offer.countriesBlacklist, Offer.countriesWhitelist, Offer.refundType, Offer.offerMappings, Offer.categories, Offer.customAttributes, Offer.items, Offer.tags, Offer.seller, Offer.keyImages, Offer.price, Offer.changelog, Offer.franchises, Offer.giveaways, Offer.related, Offer.suggestions, Offer.ratings, Offer.polls, Offer.hltb, Offer.sandbox, Offer.positions, Offer.ageRating, Offer.features, Offer.locale, Offer.localeStatus, Offer.canonicalLocale, Offer.localization, OfferLocalizationMetadata.source, OfferLocalizationMetadata.fetchedAt, OfferLocalizationMetadata.sourceUpdatedAt, OfferFeatures.launcher, OfferFeatures.features, OfferFeatures.epicFeatures, ChangelogConnection.elements, ChangelogConnection.totalCount, ChangelogConnection.totalPages, ChangelogConnection.hasNextPage, ChangelogConnection.hasPreviousPage
- legacy POST /ping (legacyPost_ping_4242a078; 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.
- legacy GET /active-sales (listActiveSales; 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.
- legacy GET /builds/{id}/files (listBuildFiles; 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.
- legacy GET /builds/{id}/items (listBuildItems; 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.
- legacy GET /builds (listBuilds; 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.
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- legacy GET /changelist (listChangelist; 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.
- legacy GET /countries (listCountries; 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.
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; 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.
- legacy GET /featured (listFeaturedGames; 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.
- legacy GET /free-games/history (listFreeGamesHistory; 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.
- legacy GET /free-games/sellers (listFreeGamesSellers; 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.
- legacy GET /items (listItems; 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.
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; 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.
- legacy GET /latest-games (listLatestGames; 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.
- legacy GET /offers/latest-released (listLatestReleasedOffers; 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.
- legacy GET /free-games/mobile (listMobileFreeGames; 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.
- legacy GET /offers/{id}/achievements (listOfferAchievements; 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.
- legacy GET /offers/{id}/assets (listOfferAssets; 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.
- legacy GET /offers/{id}/builds (listOfferBuilds; 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.
- legacy GET /offers/{id}/changelog (listOfferChangelog; 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.
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; 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.
- legacy GET /offers/{id}/genres (listOfferDetailGenres; 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.
- legacy GET /offers/events (listOfferEvents; 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.
- legacy GET /offers/{id}/franchises (listOfferFranchises; 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.
- legacy GET /offers/genres (listOfferGenres; 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.
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; 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.
- legacy GET /offers/{id}/items (listOfferItems; 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.
- legacy GET /offers/{id}/reviews (listOfferReviews; 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.
- legacy GET /offers (listOffers; 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.
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; 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.
- legacy GET /offers/{id}/technologies (listOfferTechnologies; 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.
- legacy GET /regions (listRegions; 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.
- legacy GET /offers/{id}/related (listRelatedOffers; 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.
- legacy GET /sales (listSaleOffers; 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.
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; 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.
- legacy GET /sandboxes (listSandboxes; 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.
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; 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.
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- legacy GET /search/developers (listSearchDevelopers; 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.
- legacy GET /search/offer-types (listSearchOfferTypes; 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.
- legacy GET /search/publishers (listSearchPublishers; 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.
- legacy GET /search/tags (listSearchTags; 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.
- legacy GET /sellers/{id} (listSellerOffers; 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.
- legacy GET /sellers (listSellers; 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.
- legacy GET /offers/top-sellers (listTopSellersOffers; 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.
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; 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.
- legacy GET /offers/upcoming (listUpcomingOffers; 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.
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; 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.
- legacy POST /offers/slugs (resolveOfferSlugs; 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.
- legacy GET /search/changelog (searchChangelog; 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.
- legacy GET /free-games/search (searchFreeGames; 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.
- legacy POST /search (searchOffersLegacy; 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.
- legacy POST /search/v2/search (searchOffersV2; 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.
- legacy GET /search/v2/search (searchOffersV2Get; 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.
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; 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.
- v1 GET /v1/autocomplete (autocomplete; 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.
- v1 POST /v1/offers/exists (checkOfferExistence; 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.
- v1 POST /v1/offers/slugs (checkOfferSlugs; 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.
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; 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.
- v1 GET /v1/assets/{id} (getAsset; 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.
- v1 GET /v1/base-game/{namespace} (getBaseGame; 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.
- v1 GET /v1/builds/{id} (getBuild; 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.
- v1 GET /v1/builds/{id}/history (getBuildHistory; 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.
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; 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.
- v1 GET /v1/builds/{id}/tree (getBuildTree; 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.
- v1 GET /v1/changelist/{id} (getChangelogEntry; 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.
- v1 GET /v1/collections/{slug} (getCollection; 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.
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; 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.
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; 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.
- v1 GET /v1/featured (getFeaturedGames; 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.
- v1 GET /v1/franchises/{slug} (getFranchise; 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.
- v1 GET /v1/free-games/og (getFreeGamesOg; 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.
- v1 GET /v1/free-games/stats (getFreeGamesStats; 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.
- v1 GET /v1/game-awards (getGameAwards; 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.
- v1 GET /v1/game-awards/og (getGameAwardsOg; 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.
- 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.
- v1 GET /v1/stats/homepage (getHomepageStats; 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.
- v1 GET /v1/items/{id} (getItem; 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.
- v1 GET /v1/items/{id}/assets (getItemAssets; 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.
- v1 GET /v1/items/{id}/builds (getItemBuilds; 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.
- v1 GET /v1/items/{id}/changelog (getItemChangelog; 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.
- v1 GET /v1/items/{id}/offer (getItemOffer; 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.
- v1 POST /v1/items/bulk (getItemsBulk; 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.
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; 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.
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; 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.
- v1 GET /v1/latest-games (getLatestGames; 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.
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; 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.
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; 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.
- v1 GET /v1/offers/{id} (getOffer; 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.
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; 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.
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; 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.
- v1 GET /v1/offers/{id}/assets (getOfferAssets; 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.
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; 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.
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; 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.
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; 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.
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; 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.
- v1 GET /v1/offers/{id}/collection (getOfferCollection; 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.
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; 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.
- v1 GET /v1/offers/events/{id} (getOfferEvent; 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.
- v1 GET /v1/offers/{id}/features (getOfferFeatures; 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.
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; 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.
- v1 GET /v1/offers/{id}/genres (getOfferGenres; 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.
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; 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.
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; 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.
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; 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.
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; 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.
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; 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.
- v1 GET /v1/offers/{id}/items (getOfferItems; 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.
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; 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.
- v1 GET /v1/offers/{id}/media (getOfferMedia; 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.
- v1 GET /v1/offers/{id}/og (getOfferOg; 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.
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; 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.
- v1 GET /v1/offers/{id}/overview (getOfferOverview; 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.
- v1 GET /v1/offers/{id}/polls (getOfferPolls; 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.
- v1 GET /v1/offers/{id}/price (getOfferPrice; 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.
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; 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.
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; 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.
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; 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.
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; 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.
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; 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.
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; 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.
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; 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.
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; 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.
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; 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.
- v1 GET /v1/offers/{id}/tops (getOfferTops; 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.
- v1 GET /v1/profiles/{id} (getProfile; 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.
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/information (getProfileInformation; 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.
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; 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.
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; 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.
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; 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.
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; 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.
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; 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.
- v1 GET /v1/region (getRegion; 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.
- v1 GET /v1/offers/{id}/related (getRelatedOffers; 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.
- v1 GET /v1/robots.txt (getRobots; 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.
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; 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.
- v1 GET /v1/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.
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; 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.
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; 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.
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; 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.
- v1 GET /v1/search/{id} (getSearchQuery; 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.
- v1 GET /v1/search/{id}/count (getSearchQueryCount; 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.
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; 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.
- v1 GET /v1/sellers/{id}/stats (getSellerStats; 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.
- v1 GET /v1/sitemap.xml (getSitemap; 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.
- v1 GET /v1/stats (getStats; 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.
- v1 GET /v1/open-api.json (getV1OpenApi; 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.
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; 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.
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; 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.
- v1 POST /v1/catalog/hydrate (hydrateCatalog; 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.
- v1 GET /v1/active-sales (listActiveSales; 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.
- v1 GET /v1/builds/{id}/files (listBuildFiles; 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.
- v1 GET /v1/builds/{id}/items (listBuildItems; 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.
- v1 GET /v1/builds (listBuilds; 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.
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; 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.
- v1 GET /v1/changelist (listChangelist; 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.
- v1 GET /v1/changelog (listChangelog; 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.
- v1 GET /v1/countries (listCountries; 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.
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; 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.
- v1 GET /v1/free-games (listFreeGames; 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.
- v1 GET /v1/free-games/sellers (listFreeGameSellers; 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.
- v1 GET /v1/free-games/history (listFreeGamesHistory; 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.
- v1 GET /v1/items (listItems; 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.
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; 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.
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; 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.
- v1 GET /v1/offers/latest-released (listLatestReleased; 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.
- v1 GET /v1/free-games/mobile (listMobileFreeGames; 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.
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; 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.
- v1 GET /v1/offers/events (listOfferEvents; 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.
- v1 GET /v1/offers/genres (listOfferGenres; 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.
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; 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.
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; 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.
- v1 GET /v1/offers (listOffers; 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.
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; 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.
- v1 GET /v1/profiles/{id}/games (listProfileGames; 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.
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; 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.
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; 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.
- v1 GET /v1/promotions/{id} (listPromotionOffers; 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.
- v1 GET /v1/promotions (listPromotions; 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.
- v1 GET /v1/regions (listRegions; 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.
- v1 GET /v1/sales (listSales; 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.
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; 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.
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.
- v1 GET /v1/sandboxes (listSandboxes; 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.
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; 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.
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; 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.
- v1 GET /v1/search/developers (listSearchDevelopers; 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.
- v1 GET /v1/search/offer-types (listSearchOfferTypes; 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.
- v1 GET /v1/search/publishers (listSearchPublishers; 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.
- v1 GET /v1/search/tags (listSearchTags; 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.
- v1 GET /v1/sellers/{id} (listSellerOffers; 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.
- v1 GET /v1/sellers (listSellers; 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.
- v1 GET /v1/tags (listTags; 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.
- v1 GET /v1/offers/top-sellers (listTopSellers; 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.
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; 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.
- v1 GET /v1/offers/upcoming (listUpcomingOffers; 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.
- v1 GET /v1/multisearch/items (multisearchItems; 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.
- v1 GET /v1/multisearch/offers (multisearchOffers; 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.
- v1 GET /v1/multisearch/sellers (multisearchSellers; 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.
- v1 POST /v1/search/natural-language (naturalLanguageSearch; 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.
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; 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.
- v1 GET /v1/search/changelog (searchChangelog; 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.
- v1 GET /v1/free-games/search (searchFreeGames; 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.
- v1 GET /v1/search (searchOffers; 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.
- v1 POST /v1/search (searchOffersRedirect; 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 /autocomplete (autocompleteOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /offers/exists (checkOffersExist; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/{id}/count (countSavedSearchResults; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /auth/challenge (createAbuseChallenge; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds/{id} (getBuild; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds/{id}/tree (getBuildFileTree; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds/{id}/history (getBuildHistory; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /changelist/{id} (getChangelistEntry; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /free-games (getFreeGames; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /free-games/stats (getFreeGamesStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /health (getHealth; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /stats/homepage (getHomepageStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items/{id} (getItem; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items/{id}/assets (getItemAssets; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items/{id}/builds (getItemBuilds; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items/{id}/changelog (getItemChangelog; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items/{id}/offer (getItemOffer; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /items/bulk (getItemsBulk; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id} (getOffer; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/bundle (getOfferBundle; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/events/{id} (getOfferEvent; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/features (getOfferFeatures; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/igdb (getOfferIgdb; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/mappings (getOfferMappings; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/media (getOfferMedia; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/og (getOfferOgPng; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/overview (getOfferOverview; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/polls (getOfferPolls; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/price (getOfferPrice; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/ratings (getOfferRatings; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/requirements (getOfferRequirements; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/tops (getOfferTopPositions; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /items/bulk/offers (getOffersForItemsBulk; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /region (getRegionForCountry; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId} (getSandbox; 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.appfor 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
- Before: The API gateway Worker was not bound to
- 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/{id} (getSavedSearchQuery; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sellers/{id}/stats (getSellerStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /stats (getStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /stats/creations/yearly (getYearlyCreationStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /catalog/hydrate (hydrateCatalogGraph; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET / (legacyGet__c767025d; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /changelog (legacyGet_changelog_038722cc; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /doc (legacyGet_doc_f5f543a0; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /graphql (legacyGet_graphql_220e6fb1; 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.appfor 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
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- Before: The API gateway Worker was not bound to
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items/sitemap.xml (legacyGet_items_sitemap_xml_57b8dd19; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items-sitemap.xml (legacyGet_items_sitemap_xml_e6f8185b; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /multisearch (legacyGet_multisearch_229582ca; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; 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.appfor 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
- Before: The API gateway Worker was not bound to
- 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /ping (legacyGet_ping_f7c2b7c6; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /profiles/sitemap.xml (legacyGet_profiles_sitemap_xml_0e16a159; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /promotions (legacyGet_promotions_83dd267d; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /promotions-sitemap.xml (legacyGet_promotions_sitemap_xml_3578dc8e; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /robots.txt (legacyGet_robots_txt_deae90bd; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/sitemap.xml (legacyGet_sandboxes_sitemap_xml_5773ff84; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search (legacyGet_search_82dab022; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sitemap.xml (legacyGet_sitemap_xml_efe3322f; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /tags (legacyGet_tags_803dea8c; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /ui (legacyGet_ui_64976efd; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy OPTIONS /ping (legacyOptions_ping_9143aa8e; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /graphql (legacyPost_graphql_fac042a8; 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.appfor 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
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- Before: The API gateway Worker was not bound to
- legacy POST /ping (legacyPost_ping_4242a078; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /active-sales (listActiveSales; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds/{id}/files (listBuildFiles; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds/{id}/items (listBuildItems; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /builds (listBuilds; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /changelist (listChangelist; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /countries (listCountries; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /featured (listFeaturedGames; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /free-games/history (listFreeGamesHistory; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /free-games/sellers (listFreeGamesSellers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /items (listItems; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /latest-games (listLatestGames; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/latest-released (listLatestReleasedOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /free-games/mobile (listMobileFreeGames; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/achievements (listOfferAchievements; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/assets (listOfferAssets; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/builds (listOfferBuilds; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/changelog (listOfferChangelog; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/genres (listOfferDetailGenres; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/events (listOfferEvents; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/franchises (listOfferFranchises; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/genres (listOfferGenres; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/items (listOfferItems; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/reviews (listOfferReviews; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/technologies (listOfferTechnologies; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers (listOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /regions (listRegions; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/{id}/related (listRelatedOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sales (listSaleOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sandboxes (listSandboxes; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/developers (listSearchDevelopers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/offer-types (listSearchOfferTypes; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/publishers (listSearchPublishers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/tags (listSearchTags; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sellers/{id} (listSellerOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /sellers (listSellers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/top-sellers (listTopSellersOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /offers/upcoming (listUpcomingOffers; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /offers/slugs (resolveOfferSlugs; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/changelog (searchChangelog; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /free-games/search (searchFreeGames; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /search (searchOffersLegacy; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /search/v2/search (searchOffersV2; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy GET /search/v2/search (searchOffersV2Get; 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.appfor 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
- Before: The API gateway Worker was not bound to
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; 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.appfor 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
- Before: The API gateway Worker was not bound to
- v1 GET /v1/autocomplete (autocomplete; 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
- v1 POST /v1/offers/exists (checkOfferExistence; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
- v1 POST /v1/offers/slugs (checkOfferSlugs; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; 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
- v1 GET /v1/assets/{id} (getAsset; 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
- v1 GET /v1/base-game/{namespace} (getBaseGame; 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
- v1 GET /v1/builds/{id} (getBuild; 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
- v1 GET /v1/builds/{id}/history (getBuildHistory; 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
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; 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
- v1 GET /v1/builds/{id}/tree (getBuildTree; 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
- v1 GET /v1/changelist/{id} (getChangelogEntry; 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
- v1 GET /v1/collections/{slug} (getCollection; 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
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; 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
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; 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
- v1 GET /v1/featured (getFeaturedGames; 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
- v1 GET /v1/franchises/{slug} (getFranchise; 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
- v1 GET /v1/free-games/og (getFreeGamesOg; 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
- v1 GET /v1/free-games/stats (getFreeGamesStats; 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
- v1 GET /v1/game-awards (getGameAwards; 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
- v1 GET /v1/game-awards/og (getGameAwardsOg; 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
- 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
- v1 GET /v1/stats/homepage (getHomepageStats; 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
- v1 GET /v1/items/{id} (getItem; 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
- v1 GET /v1/items/{id}/assets (getItemAssets; 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
- v1 GET /v1/items/{id}/builds (getItemBuilds; 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
- v1 GET /v1/items/{id}/changelog (getItemChangelog; 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
- v1 GET /v1/items/{id}/offer (getItemOffer; 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
- v1 POST /v1/items/bulk (getItemsBulk; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; 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
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; 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
- v1 GET /v1/latest-games (getLatestGames; 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
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; 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
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; 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
- v1 GET /v1/offers/{id} (getOffer; 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
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; 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
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; 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
- v1 GET /v1/offers/{id}/assets (getOfferAssets; 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
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; 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
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; 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
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; 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
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; 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
- v1 GET /v1/offers/{id}/collection (getOfferCollection; 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
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; 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
- v1 GET /v1/offers/events/{id} (getOfferEvent; 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
- v1 GET /v1/offers/{id}/features (getOfferFeatures; 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
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; 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
- v1 GET /v1/offers/{id}/genres (getOfferGenres; 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
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; 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
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; 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
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; 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
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; 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
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; 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
- v1 GET /v1/offers/{id}/items (getOfferItems; 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
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; 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
- v1 GET /v1/offers/{id}/media (getOfferMedia; 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
- v1 GET /v1/offers/{id}/og (getOfferOg; 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
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; 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
- v1 GET /v1/offers/{id}/overview (getOfferOverview; 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
- v1 GET /v1/offers/{id}/polls (getOfferPolls; 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
- v1 GET /v1/offers/{id}/price (getOfferPrice; 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
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; 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
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; 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
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; 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
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; 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
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; 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
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; 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
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; 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
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; 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
- v1 GET /v1/offers/{id}/tops (getOfferTops; 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
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
- v1 GET /v1/profiles/{id} (getProfile; 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
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; 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
- v1 GET /v1/profiles/{id}/information (getProfileInformation; 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
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; 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
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; 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
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; 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
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; 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
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; 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
- v1 GET /v1/region (getRegion; 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
- v1 GET /v1/offers/{id}/related (getRelatedOffers; 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
- v1 GET /v1/robots.txt (getRobots; 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
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; 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
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; 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
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; 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
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; 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
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; 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
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; 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
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; 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
- v1 GET /v1/search/{id} (getSearchQuery; 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
- v1 GET /v1/search/{id}/count (getSearchQueryCount; 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
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; 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
- v1 GET /v1/sellers/{id}/stats (getSellerStats; 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
- v1 GET /v1/sitemap.xml (getSitemap; 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
- v1 GET /v1/stats (getStats; 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
- v1 GET /v1/open-api.json (getV1OpenApi; 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
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; 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
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; 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
- v1 POST /v1/catalog/hydrate (hydrateCatalog; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
- v1 GET /v1/active-sales (listActiveSales; 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
- v1 GET /v1/builds/{id}/files (listBuildFiles; 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
- v1 GET /v1/builds/{id}/items (listBuildItems; 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
- v1 GET /v1/builds (listBuilds; 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
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; 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
- v1 GET /v1/changelist (listChangelist; 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
- v1 GET /v1/changelog (listChangelog; 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
- v1 GET /v1/countries (listCountries; 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
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; 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
- v1 GET /v1/free-games/sellers (listFreeGameSellers; 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
- v1 GET /v1/free-games (listFreeGames; 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
- v1 GET /v1/free-games/history (listFreeGamesHistory; 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
- v1 GET /v1/items (listItems; 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
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; 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
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; 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
- v1 GET /v1/offers/latest-released (listLatestReleased; 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
- v1 GET /v1/free-games/mobile (listMobileFreeGames; 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
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; 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
- v1 GET /v1/offers/events (listOfferEvents; 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
- v1 GET /v1/offers/genres (listOfferGenres; 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
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; 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
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; 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
- v1 GET /v1/offers (listOffers; 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
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; 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
- v1 GET /v1/profiles/{id}/games (listProfileGames; 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
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; 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
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; 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
- v1 GET /v1/promotions/{id} (listPromotionOffers; 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
- v1 GET /v1/promotions (listPromotions; 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
- v1 GET /v1/regions (listRegions; 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
- v1 GET /v1/sales (listSales; 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
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; 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
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; 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
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; 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
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; 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
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; 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
- v1 GET /v1/sandboxes (listSandboxes; 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
- v1 GET /v1/search/developers (listSearchDevelopers; 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
- v1 GET /v1/search/offer-types (listSearchOfferTypes; 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
- v1 GET /v1/search/publishers (listSearchPublishers; 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
- v1 GET /v1/search/tags (listSearchTags; 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
- v1 GET /v1/sellers/{id} (listSellerOffers; 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
- v1 GET /v1/sellers (listSellers; 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
- v1 GET /v1/tags (listTags; 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
- v1 GET /v1/offers/top-sellers (listTopSellers; 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
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; 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
- v1 GET /v1/offers/upcoming (listUpcomingOffers; 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
- v1 GET /v1/multisearch/items (multisearchItems; 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
- v1 GET /v1/multisearch/offers (multisearchOffers; 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
- v1 GET /v1/multisearch/sellers (multisearchSellers; 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
- v1 POST /v1/search/natural-language (naturalLanguageSearch; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules are unchanged. - Client action: None
- Before: The API gateway Worker was not bound to
- v1 GET /v1/search/changelog (searchChangelog; 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
- v1 GET /v1/free-games/search (searchFreeGames; 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
- v1 GET /v1/search (searchOffers; 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
- v1 POST /v1/search (searchOffersRedirect; changed; compatible)
- Before: The API gateway Worker was not bound to
api.egdata.app, so this v1 operation was not served through that public API hostname. - After: The Worker is now bound to
api.egdata.app, making this v1 operation available through the public API hostname. Its method, path, authentication requirements, request validation, response contract, and quota rules 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 — Apply administrator-approved project limits to API keys and console sessions
Record: admin-reviewed-project-limits.
- v1 GET /v1/autocomplete (autocomplete; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/offers/exists (checkOfferExistence; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/offers/slugs (checkOfferSlugs; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/assets/{id} (getAsset; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/base-game/{namespace} (getBaseGame; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds/{id} (getBuild; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds/{id}/history (getBuildHistory; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds/{id}/tree (getBuildTree; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/changelist/{id} (getChangelogEntry; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/collections/{slug} (getCollection; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/featured (getFeaturedGames; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/franchises/{slug} (getFranchise; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/free-games/og (getFreeGamesOg; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/free-games/stats (getFreeGamesStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/game-awards (getGameAwards; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/game-awards/og (getGameAwardsOg; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/stats/homepage (getHomepageStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items/{id} (getItem; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items/{id}/assets (getItemAssets; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items/{id}/builds (getItemBuilds; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items/{id}/changelog (getItemChangelog; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items/{id}/offer (getItemOffer; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/items/bulk (getItemsBulk; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/latest-games (getLatestGames; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id} (getOffer; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/assets (getOfferAssets; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/collection (getOfferCollection; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/events/{id} (getOfferEvent; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/features (getOfferFeatures; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/genres (getOfferGenres; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/items (getOfferItems; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/media (getOfferMedia; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/og (getOfferOg; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/overview (getOfferOverview; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/polls (getOfferPolls; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/price (getOfferPrice; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/tops (getOfferTops; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id} (getProfile; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id}/information (getProfileInformation; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/region (getRegion; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/related (getRelatedOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/robots.txt (getRobots; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search/{id} (getSearchQuery; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search/{id}/count (getSearchQueryCount; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sellers/{id}/stats (getSellerStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sitemap.xml (getSitemap; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/stats (getStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/open-api.json (getV1OpenApi; changed; compatible)
- Before: The v1 API description did not describe administrator review and inheritance of approved project quotas.
- After: The API description documents administrator-reviewed project limits, inheritance by keys and console sessions, and bounded cache propagation.
- Client action: None
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/catalog/hydrate (hydrateCatalog; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/active-sales (listActiveSales; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds/{id}/files (listBuildFiles; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds/{id}/items (listBuildItems; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/builds (listBuilds; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/changelist (listChangelist; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/changelog (listChangelog; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/countries (listCountries; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/free-games (listFreeGames; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/free-games/sellers (listFreeGameSellers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/free-games/history (listFreeGamesHistory; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items (listItems; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/latest-released (listLatestReleased; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/free-games/mobile (listMobileFreeGames; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/events (listOfferEvents; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/genres (listOfferGenres; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers (listOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id}/games (listProfileGames; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/promotions/{id} (listPromotionOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/promotions (listPromotions; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/regions (listRegions; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sales (listSales; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes (listSandboxes; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search/developers (listSearchDevelopers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search/offer-types (listSearchOfferTypes; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search/publishers (listSearchPublishers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search/tags (listSearchTags; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sellers/{id} (listSellerOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/sellers (listSellers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/tags (listTags; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/top-sellers (listTopSellers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/offers/upcoming (listUpcomingOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/multisearch/items (multisearchItems; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/multisearch/offers (multisearchOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/multisearch/sellers (multisearchSellers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/search/natural-language (naturalLanguageSearch; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search/changelog (searchChangelog; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/free-games/search (searchFreeGames; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 GET /v1/search (searchOffers; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
- v1 POST /v1/search (searchOffersRedirect; changed; compatible)
- Before: Limit requests were saved without a dashboard approval action; new keys inherited only the project tier and console sessions ignored custom project RPM.
- After: After explicit administrator approval, existing and future project keys inherit the approved RPM. Console sessions use the current project custom RPM on each request. Key caches refresh within five minutes; operation caps and quota counters are unchanged. Projects without an approved change retain their existing limits.
- Client action: None
Verification: dashboard/tests/limit-reviews.test.ts; dashboard/tests/console-sessions.test.ts; pnpm docs:check.
2026-11-11 — Match static v1 operations before parameter routes
Record: exact-v1-static-operation-matching.
- v1 GET /v1/offers/{id} (getOffer; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/latest-released.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/{id} use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/events (listOfferEvents; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/events.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/events use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/upcoming (listUpcomingOffers; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/upcoming.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/upcoming use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/genres (listOfferGenres; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/genres.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/genres use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/top-wishlisted.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/top-wishlisted use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/top-sellers (listTopSellers; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/top-sellers.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/top-sellers use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/featured-discounts.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/featured-discounts use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/latest-achievements.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/latest-achievements use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
- v1 GET /v1/offers/latest-released (listLatestReleased; fixed; compatible)
- Before: The gateway could attribute requests for a static path overlapping /v1/offers/{id} to getOffer before examining /v1/offers/latest-released.
- After: Static registry paths take precedence over parameter paths. Requests to /v1/offers/latest-released use their actual registered operation for permission scopes, expensive-operation limits, analytics and durable endpoint history matching; the origin URL and response contract are unchanged.
- Client action: None
Verification: dashboard/tests/console-sessions.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 /autocomplete (autocompleteOffers; fixed; compatible)
- Before: GET /autocomplete was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /autocomplete 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
- legacy POST /offers/exists (checkOffersExist; fixed; compatible)
- Before: POST /offers/exists was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /offers/exists 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
- legacy GET /builds/{targetId}/compare/{baseId} (compareBuilds; fixed; compatible)
- Before: GET /builds/{targetId}/compare/{baseId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds/{targetId}/compare/{baseId} 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
- legacy GET /search/{id}/count (countSavedSearchResults; fixed; compatible)
- Before: GET /search/{id}/count was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/{id}/count 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
- legacy POST /auth/challenge (createAbuseChallenge; fixed; compatible)
- Before: POST /auth/challenge was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /auth/challenge 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
- legacy GET /builds/{id} (getBuild; fixed; compatible)
- Before: GET /builds/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds/{id} 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
- legacy GET /builds/{id}/tree (getBuildFileTree; fixed; compatible)
- Before: GET /builds/{id}/tree was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds/{id}/tree 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
- legacy GET /builds/{id}/history (getBuildHistory; fixed; compatible)
- Before: GET /builds/{id}/history was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds/{id}/history 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
- legacy GET /builds/{id}/install-options (getBuildInstallOptions; fixed; compatible)
- Before: GET /builds/{id}/install-options was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds/{id}/install-options 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
- legacy GET /changelist/{id} (getChangelistEntry; fixed; compatible)
- Before: GET /changelist/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /changelist/{id} 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
- legacy GET /free-games (getFreeGames; fixed; compatible)
- Before: GET /free-games was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /free-games 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
- legacy GET /free-games/stats (getFreeGamesStats; fixed; compatible)
- Before: GET /free-games/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /free-games/stats 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
- legacy GET /health (getHealth; fixed; compatible)
- Before: GET /health was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /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
- legacy GET /stats/homepage (getHomepageStats; fixed; compatible)
- Before: GET /stats/homepage was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /stats/homepage 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
- legacy GET /items/{id} (getItem; fixed; compatible)
- Before: GET /items/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items/{id} 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
- legacy GET /items/{id}/assets (getItemAssets; fixed; compatible)
- Before: GET /items/{id}/assets was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items/{id}/assets 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
- legacy GET /items/{id}/builds (getItemBuilds; fixed; compatible)
- Before: GET /items/{id}/builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items/{id}/builds 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
- legacy GET /items/{id}/changelog (getItemChangelog; fixed; compatible)
- Before: GET /items/{id}/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items/{id}/changelog 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
- legacy GET /items/{id}/offer (getItemOffer; fixed; compatible)
- Before: GET /items/{id}/offer was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items/{id}/offer 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
- legacy POST /items/bulk (getItemsBulk; fixed; compatible)
- Before: POST /items/bulk was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /items/bulk 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
- legacy GET /stats/creations/monthly (getMonthlyCreationStats; fixed; compatible)
- Before: GET /stats/creations/monthly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /stats/creations/monthly 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
- legacy GET /stats/releases/monthly (getMonthlyReleaseStats; fixed; compatible)
- Before: GET /stats/releases/monthly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /stats/releases/monthly 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
- legacy GET /offers/{id} (getOffer; fixed; compatible)
- Before: GET /offers/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id} 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
- legacy GET /offers/{id}/age-rating (getOfferAgeRating; fixed; compatible)
- Before: GET /offers/{id}/age-rating was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/age-rating 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
- legacy GET /offers/{id}/bundle (getOfferBundle; fixed; compatible)
- Before: GET /offers/{id}/bundle was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/bundle 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
- legacy GET /offers/{id}/changelog/stats (getOfferChangelogStats; fixed; compatible)
- Before: GET /offers/{id}/changelog/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/changelog/stats 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
- legacy GET /offers/{id}/collections/{collection} (getOfferCollectionPosition; fixed; compatible)
- Before: GET /offers/{id}/collections/{collection} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/collections/{collection} 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
- legacy GET /offers/events/{id} (getOfferEvent; fixed; compatible)
- Before: GET /offers/events/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/events/{id} 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
- legacy GET /offers/{id}/features (getOfferFeatures; fixed; compatible)
- Before: GET /offers/{id}/features was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/features 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
- legacy GET /offers/{id}/hltb (getOfferHowLongToBeat; fixed; compatible)
- Before: GET /offers/{id}/hltb was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/hltb 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
- legacy GET /offers/{id}/igdb (getOfferIgdb; fixed; compatible)
- Before: GET /offers/{id}/igdb was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/igdb 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
- legacy GET /offers/{id}/mappings (getOfferMappings; fixed; compatible)
- Before: GET /offers/{id}/mappings was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/mappings 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
- legacy GET /offers/{id}/media (getOfferMedia; fixed; compatible)
- Before: GET /offers/{id}/media was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/media 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
- legacy GET /offers/{id}/og (getOfferOgPng; fixed; compatible)
- Before: GET /offers/{id}/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/og 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
- legacy GET /offers/{id}/og.webp (getOfferOgWebp; fixed; compatible)
- Before: GET /offers/{id}/og.webp was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/og.webp 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
- legacy GET /offers/{id}/overview (getOfferOverview; fixed; compatible)
- Before: GET /offers/{id}/overview was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/overview 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
- legacy GET /offers/{id}/polls (getOfferPolls; fixed; compatible)
- Before: GET /offers/{id}/polls was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/polls 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
- legacy GET /offers/{id}/has-prepurchase (getOfferPrepurchaseAlternative; fixed; compatible)
- Before: GET /offers/{id}/has-prepurchase was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/has-prepurchase 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
- legacy GET /offers/{id}/price (getOfferPrice; fixed; compatible)
- Before: GET /offers/{id}/price was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/price 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
- legacy GET /offers/{id}/price/fairness (getOfferPriceFairness; fixed; compatible)
- Before: GET /offers/{id}/price/fairness was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/price/fairness 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
- legacy GET /offers/{id}/price-history (getOfferPriceHistory; fixed; compatible)
- Before: GET /offers/{id}/price-history was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/price-history 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
- legacy GET /offers/{id}/price-stats (getOfferPriceStats; fixed; compatible)
- Before: GET /offers/{id}/price-stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/price-stats 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
- legacy GET /offers/{id}/ratings (getOfferRatings; fixed; compatible)
- Before: GET /offers/{id}/ratings was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/ratings 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
- legacy GET /offers/{id}/regional-price (getOfferRegionalPrices; fixed; compatible)
- Before: GET /offers/{id}/regional-price was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/regional-price 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
- legacy GET /offers/{id}/has-regular (getOfferRegularAlternative; fixed; compatible)
- Before: GET /offers/{id}/has-regular was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/has-regular 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
- legacy GET /offers/{id}/requirements (getOfferRequirements; fixed; compatible)
- Before: GET /offers/{id}/requirements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/requirements 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
- legacy GET /offers/{id}/reviews-summary (getOfferReviewsSummary; fixed; compatible)
- Before: GET /offers/{id}/reviews-summary was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/reviews-summary 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
- legacy POST /items/bulk/offers (getOffersForItemsBulk; fixed; compatible)
- Before: POST /items/bulk/offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /items/bulk/offers 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
- legacy GET /offers/{id}/tops (getOfferTopPositions; fixed; compatible)
- Before: GET /offers/{id}/tops was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/tops 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
- legacy GET /region (getRegionForCountry; fixed; compatible)
- Before: GET /region was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /region 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
- legacy GET /sandboxes/{sandboxId} (getSandbox; fixed; compatible)
- Before: GET /sandboxes/{sandboxId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId} 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
- 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
- legacy GET /sandboxes/{sandboxId}/og (getSandboxOgPng; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/og 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
- legacy GET /sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/og.webp was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/og.webp 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
- legacy GET /sandboxes/{sandboxId}/stats (getSandboxStats; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/stats 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
- legacy GET /search/{id} (getSavedSearchQuery; fixed; compatible)
- Before: GET /search/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/{id} 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
- legacy GET /sellers/{id}/cover (getSellerCoverOffers; fixed; compatible)
- Before: GET /sellers/{id}/cover was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sellers/{id}/cover 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
- legacy GET /sellers/{id}/stats (getSellerStats; fixed; compatible)
- Before: GET /sellers/{id}/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sellers/{id}/stats 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
- legacy GET /stats (getStats; fixed; compatible)
- Before: GET /stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /stats 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
- legacy GET /stats/creations/yearly (getYearlyCreationStats; fixed; compatible)
- Before: GET /stats/creations/yearly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /stats/creations/yearly 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
- legacy GET /stats/releases/yearly (getYearlyReleaseStats; fixed; compatible)
- Before: GET /stats/releases/yearly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /stats/releases/yearly 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
- legacy POST /catalog/hydrate (hydrateCatalogGraph; fixed; compatible)
- Before: POST /catalog/hydrate was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /catalog/hydrate 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
- legacy GET / (legacyGet__c767025d; fixed; compatible)
- Before: GET / was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET / 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
- legacy GET /assets/{id} (legacyGet_assets_id__fe67ede6; fixed; compatible)
- Before: GET /assets/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /assets/{id} 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
- legacy GET /base-game/{namespace} (legacyGet_base_game_namespace__43947330; fixed; compatible)
- Before: GET /base-game/{namespace} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /base-game/{namespace} 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
- legacy GET /changelog (legacyGet_changelog_038722cc; fixed; compatible)
- Before: GET /changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /changelog 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
- legacy GET /collections/{slug} (legacyGet_collections_slug__c9e20bbf; fixed; compatible)
- Before: GET /collections/{slug} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /collections/{slug} 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
- legacy GET /collections/{slug}/{week} (legacyGet_collections_slug_week__e7c64eb1; fixed; compatible)
- Before: GET /collections/{slug}/{week} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /collections/{slug}/{week} 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
- legacy GET /collections/{slug}/{week}/og (legacyGet_collections_slug_week_og_abb2fde5; fixed; compatible)
- Before: GET /collections/{slug}/{week}/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /collections/{slug}/{week}/og 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
- legacy GET /doc (legacyGet_doc_f5f543a0; fixed; compatible)
- Before: GET /doc was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /doc 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
- legacy GET /franchises/{slug} (legacyGet_franchises_slug__468d5cca; fixed; compatible)
- Before: GET /franchises/{slug} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /franchises/{slug} 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
- legacy GET /free-games/og (legacyGet_free_games_og_656b6e88; fixed; compatible)
- Before: GET /free-games/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /free-games/og 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
- legacy GET /game-awards (legacyGet_game_awards_5a8ac742; fixed; compatible)
- Before: GET /game-awards was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /game-awards 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
- legacy GET /game-awards/og (legacyGet_game_awards_og_aa6a5f28; fixed; compatible)
- Before: GET /game-awards/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /game-awards/og 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
- legacy GET /graphql (legacyGet_graphql_220e6fb1; fixed; compatible)
- Before: GET /graphql was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /graphql 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
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- legacy GET /items-from-offer/{id} (legacyGet_items_from_offer_id__f652bc56; fixed; compatible)
- Before: GET /items-from-offer/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items-from-offer/{id} 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
- legacy GET /items/sitemap.xml (legacyGet_items_sitemap_xml_57b8dd19; fixed; compatible)
- Before: GET /items/sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items/sitemap.xml 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
- legacy GET /items-sitemap.xml (legacyGet_items_sitemap_xml_e6f8185b; fixed; compatible)
- Before: GET /items-sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items-sitemap.xml 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
- legacy GET /multisearch (legacyGet_multisearch_229582ca; fixed; compatible)
- Before: GET /multisearch was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /multisearch 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
- legacy GET /multisearch/items (legacyGet_multisearch_items_6adf1480; fixed; compatible)
- Before: GET /multisearch/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /multisearch/items 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
- legacy GET /multisearch/offers (legacyGet_multisearch_offers_f0c29182; fixed; compatible)
- Before: GET /multisearch/offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /multisearch/offers 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
- legacy GET /multisearch/sellers (legacyGet_multisearch_sellers_c239406a; fixed; compatible)
- Before: GET /multisearch/sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /multisearch/sellers 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
- legacy GET /offer-by-slug/{slug} (legacyGet_offer_by_slug_slug__5aadfed6; fixed; compatible)
- Before: GET /offer-by-slug/{slug} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offer-by-slug/{slug} 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
- 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
- legacy GET /ping (legacyGet_ping_f7c2b7c6; fixed; compatible)
- Before: GET /ping was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /ping 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
- legacy GET /profiles/{id} (legacyGet_profiles_id__f0000a67; fixed; compatible)
- Before: GET /profiles/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id} 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
- legacy GET /profiles/{id}/achievements (legacyGet_profiles_id_achievements_e2c38dc7; fixed; compatible)
- Before: GET /profiles/{id}/achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/achievements 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
- legacy GET /profiles/{id}/achievements/{sandboxId} (legacyGet_profiles_id_achievements_sandboxId__3f40ec52; fixed; compatible)
- Before: GET /profiles/{id}/achievements/{sandboxId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/achievements/{sandboxId} 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
- legacy GET /profiles/{id}/games (legacyGet_profiles_id_games_35bd6af2; fixed; compatible)
- Before: GET /profiles/{id}/games was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/games 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
- legacy GET /profiles/{id}/information (legacyGet_profiles_id_information_1a333c76; fixed; compatible)
- Before: GET /profiles/{id}/information was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/information 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
- legacy GET /profiles/{id}/random-game (legacyGet_profiles_id_random_game_bdccf825; fixed; compatible)
- Before: GET /profiles/{id}/random-game was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/random-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
- legacy GET /profiles/{id}/rare-achievements (legacyGet_profiles_id_rare_achievements_0a3d8b68; fixed; compatible)
- Before: GET /profiles/{id}/rare-achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/rare-achievements 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
- legacy GET /profiles/{id}/rare-achievements/{sandboxId} (legacyGet_profiles_id_rare_achievements_sandboxId__c761732b; fixed; compatible)
- Before: GET /profiles/{id}/rare-achievements/{sandboxId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/rare-achievements/{sandboxId} 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
- legacy GET /profiles/{id}/refresh-status (legacyGet_profiles_id_refresh_status_ee9656f7; fixed; compatible)
- Before: GET /profiles/{id}/refresh-status was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/{id}/refresh-status 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
- legacy GET /profiles/leaderboard (legacyGet_profiles_leaderboard_7a07d3bc; fixed; compatible)
- Before: GET /profiles/leaderboard was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/leaderboard 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
- legacy GET /profiles/sitemap.xml (legacyGet_profiles_sitemap_xml_0e16a159; fixed; compatible)
- Before: GET /profiles/sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /profiles/sitemap.xml 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
- legacy GET /promotions (legacyGet_promotions_83dd267d; fixed; compatible)
- Before: GET /promotions was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /promotions 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
- legacy GET /promotions/{id} (legacyGet_promotions_id__ca5d27b1; fixed; compatible)
- Before: GET /promotions/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /promotions/{id} 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
- legacy GET /promotions/{id}/cover (legacyGet_promotions_id_cover_2c62e571; fixed; compatible)
- Before: GET /promotions/{id}/cover was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /promotions/{id}/cover 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
- legacy GET /promotions-sitemap.xml (legacyGet_promotions_sitemap_xml_3578dc8e; fixed; compatible)
- Before: GET /promotions-sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /promotions-sitemap.xml 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
- legacy GET /push/vapid-public-key (legacyGet_push_vapid_public_key_472be0da; fixed; compatible)
- Before: GET /push/vapid-public-key was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /push/vapid-public-key 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
- legacy GET /robots.txt (legacyGet_robots_txt_deae90bd; fixed; compatible)
- Before: GET /robots.txt was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /robots.txt 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
- legacy GET /sandboxes/sitemap.xml (legacyGet_sandboxes_sitemap_xml_5773ff84; fixed; compatible)
- Before: GET /sandboxes/sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/sitemap.xml 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
- legacy GET /search (legacyGet_search_82dab022; fixed; compatible)
- Before: GET /search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search 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
- legacy GET /sitemap.xml (legacyGet_sitemap_xml_efe3322f; fixed; compatible)
- Before: GET /sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sitemap.xml 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
- legacy GET /tags (legacyGet_tags_803dea8c; fixed; compatible)
- Before: GET /tags was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /tags 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
- legacy GET /ui (legacyGet_ui_64976efd; fixed; compatible)
- Before: GET /ui was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /ui 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
- legacy OPTIONS /ping (legacyOptions_ping_9143aa8e; fixed; compatible)
- Before: OPTIONS /ping was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: OPTIONS /ping 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
- legacy POST /graphql (legacyPost_graphql_fac042a8; fixed; compatible)
- Before: POST /graphql was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /graphql 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
- Schema fields: Query.offer, Query.offers, Query.upcoming, Query.latestReleased, Query.topSellers, Query.topWishlisted, Query.featuredDiscounts, Query.item, Query.items, Query.sandbox, Query.sandboxHub, Query.sandboxes, Query.profile, Query.build, Query.builds, Query.changelog, Query.events, Query.event, Query.genres, Query.latestAchievements
- legacy POST /ping (legacyPost_ping_4242a078; fixed; compatible)
- Before: POST /ping was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /ping 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
- legacy GET /active-sales (listActiveSales; fixed; compatible)
- Before: GET /active-sales was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /active-sales 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
- legacy GET /builds/{id}/files (listBuildFiles; fixed; compatible)
- Before: GET /builds/{id}/files was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds/{id}/files 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
- legacy GET /builds/{id}/items (listBuildItems; fixed; compatible)
- Before: GET /builds/{id}/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds/{id}/items 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
- legacy GET /builds (listBuilds; fixed; compatible)
- Before: GET /builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /builds 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
- legacy GET /offers/{id}/in-bundle (listBundlesContainingOffer; fixed; compatible)
- Before: GET /offers/{id}/in-bundle was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/in-bundle 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
- legacy GET /changelist (listChangelist; fixed; compatible)
- Before: GET /changelist was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /changelist 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
- legacy GET /countries (listCountries; fixed; compatible)
- Before: GET /countries was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /countries 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
- legacy GET /offers/featured-discounts (listFeaturedDiscounts; fixed; compatible)
- Before: GET /offers/featured-discounts was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/featured-discounts 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
- legacy GET /featured (listFeaturedGames; fixed; compatible)
- Before: GET /featured was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /featured 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
- legacy GET /free-games/history (listFreeGamesHistory; fixed; compatible)
- Before: GET /free-games/history was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /free-games/history 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
- legacy GET /free-games/sellers (listFreeGamesSellers; fixed; compatible)
- Before: GET /free-games/sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /free-games/sellers 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
- legacy GET /items (listItems; fixed; compatible)
- Before: GET /items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /items 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
- legacy GET /offers/latest-achievements (listLatestAchievementOffers; fixed; compatible)
- Before: GET /offers/latest-achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/latest-achievements 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
- legacy GET /latest-games (listLatestGames; fixed; compatible)
- Before: GET /latest-games was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /latest-games 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
- legacy GET /offers/latest-released (listLatestReleasedOffers; fixed; compatible)
- Before: GET /offers/latest-released was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/latest-released 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
- legacy GET /free-games/mobile (listMobileFreeGames; fixed; compatible)
- Before: GET /free-games/mobile was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /free-games/mobile 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
- legacy GET /offers/{id}/achievements (listOfferAchievements; fixed; compatible)
- Before: GET /offers/{id}/achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/achievements 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
- legacy GET /offers/{id}/assets (listOfferAssets; fixed; compatible)
- Before: GET /offers/{id}/assets was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/assets 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
- legacy GET /offers/{id}/builds (listOfferBuilds; fixed; compatible)
- Before: GET /offers/{id}/builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/builds 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
- legacy GET /offers/{id}/changelog (listOfferChangelog; fixed; compatible)
- Before: GET /offers/{id}/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/changelog 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
- legacy GET /offers/{id}/collection (listOfferCollectionOffers; fixed; compatible)
- Before: GET /offers/{id}/collection was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/collection 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
- legacy GET /offers/{id}/genres (listOfferDetailGenres; fixed; compatible)
- Before: GET /offers/{id}/genres was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/genres 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
- legacy GET /offers/events (listOfferEvents; fixed; compatible)
- Before: GET /offers/events was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/events 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
- legacy GET /offers/{id}/franchises (listOfferFranchises; fixed; compatible)
- Before: GET /offers/{id}/franchises was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/franchises 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
- legacy GET /offers/genres (listOfferGenres; fixed; compatible)
- Before: GET /offers/genres was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/genres 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
- legacy GET /offers/{id}/giveaways (listOfferGiveaways; fixed; compatible)
- Before: GET /offers/{id}/giveaways was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/giveaways 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
- legacy GET /offers/{id}/items (listOfferItems; fixed; compatible)
- Before: GET /offers/{id}/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/items 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
- legacy GET /offers/{id}/reviews (listOfferReviews; fixed; compatible)
- Before: GET /offers/{id}/reviews was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/reviews 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
- legacy GET /offers (listOffers; fixed; compatible)
- Before: GET /offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers 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
- legacy GET /offers/{id}/suggestions (listOfferSuggestions; fixed; compatible)
- Before: GET /offers/{id}/suggestions was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/suggestions 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
- legacy GET /offers/{id}/technologies (listOfferTechnologies; fixed; compatible)
- Before: GET /offers/{id}/technologies was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/technologies 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
- legacy GET /regions (listRegions; fixed; compatible)
- Before: GET /regions was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /regions 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
- legacy GET /offers/{id}/related (listRelatedOffers; fixed; compatible)
- Before: GET /offers/{id}/related was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/{id}/related 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
- legacy GET /sales (listSaleOffers; fixed; compatible)
- Before: GET /sales was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sales 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
- legacy GET /sandboxes/{sandboxId}/achievements (listSandboxAchievements; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/achievements 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
- legacy GET /sandboxes/{sandboxId}/assets (listSandboxAssets; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/assets was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/assets 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
- legacy GET /sandboxes/{sandboxId}/builds (listSandboxBuilds; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/builds 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
- legacy GET /sandboxes/{sandboxId}/changelog (listSandboxChangelog; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/changelog 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
- legacy GET /sandboxes (listSandboxes; fixed; compatible)
- Before: GET /sandboxes was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes 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
- legacy GET /sandboxes/{sandboxId}/items (listSandboxItems; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/items 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
- legacy GET /sandboxes/{sandboxId}/offers (listSandboxOffers; fixed; compatible)
- Before: GET /sandboxes/{sandboxId}/offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sandboxes/{sandboxId}/offers 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
- legacy GET /search/developers (listSearchDevelopers; fixed; compatible)
- Before: GET /search/developers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/developers 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
- legacy GET /search/offer-types (listSearchOfferTypes; fixed; compatible)
- Before: GET /search/offer-types was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/offer-types 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
- legacy GET /search/publishers (listSearchPublishers; fixed; compatible)
- Before: GET /search/publishers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/publishers 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
- legacy GET /search/tags (listSearchTags; fixed; compatible)
- Before: GET /search/tags was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/tags 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
- legacy GET /sellers/{id} (listSellerOffers; fixed; compatible)
- Before: GET /sellers/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sellers/{id} 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
- legacy GET /sellers (listSellers; fixed; compatible)
- Before: GET /sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /sellers 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
- legacy GET /offers/top-sellers (listTopSellersOffers; fixed; compatible)
- Before: GET /offers/top-sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/top-sellers 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
- legacy GET /offers/top-wishlisted (listTopWishlistedOffers; fixed; compatible)
- Before: GET /offers/top-wishlisted was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/top-wishlisted 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
- legacy GET /offers/upcoming (listUpcomingOffers; fixed; compatible)
- Before: GET /offers/upcoming was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /offers/upcoming 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
- legacy POST /builds/resolve-launcher-records (resolveLauncherRecords; fixed; compatible)
- Before: POST /builds/resolve-launcher-records was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /builds/resolve-launcher-records 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
- legacy POST /offers/slugs (resolveOfferSlugs; fixed; compatible)
- Before: POST /offers/slugs was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /offers/slugs 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
- legacy GET /search/changelog (searchChangelog; fixed; compatible)
- Before: GET /search/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/changelog 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
- legacy GET /free-games/search (searchFreeGames; fixed; compatible)
- Before: GET /free-games/search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /free-games/search 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
- legacy POST /search (searchOffersLegacy; fixed; compatible)
- Before: POST /search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /search 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
- legacy POST /search/v2/search (searchOffersV2; fixed; compatible)
- Before: POST /search/v2/search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /search/v2/search 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
- legacy GET /search/v2/search (searchOffersV2Get; fixed; compatible)
- Before: GET /search/v2/search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /search/v2/search 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
- legacy POST /search/natural-language (searchOffersWithNaturalLanguage; fixed; compatible)
- Before: POST /search/natural-language was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /search/natural-language 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
- v1 GET /v1/autocomplete (autocomplete; fixed; compatible)
- Before: GET /v1/autocomplete was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/autocomplete 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
- v1 POST /v1/offers/exists (checkOfferExistence; fixed; compatible)
- Before: POST /v1/offers/exists was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/offers/exists 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
- v1 POST /v1/offers/slugs (checkOfferSlugs; fixed; compatible)
- Before: POST /v1/offers/slugs was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/offers/slugs 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
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; fixed; compatible)
- Before: GET /v1/builds/{targetId}/compare/{baseId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds/{targetId}/compare/{baseId} 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
- v1 GET /v1/assets/{id} (getAsset; fixed; compatible)
- Before: GET /v1/assets/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/assets/{id} 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
- v1 GET /v1/base-game/{namespace} (getBaseGame; fixed; compatible)
- Before: GET /v1/base-game/{namespace} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/base-game/{namespace} 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
- v1 GET /v1/builds/{id} (getBuild; fixed; compatible)
- Before: GET /v1/builds/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds/{id} 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
- v1 GET /v1/builds/{id}/history (getBuildHistory; fixed; compatible)
- Before: GET /v1/builds/{id}/history was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds/{id}/history 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
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; fixed; compatible)
- Before: GET /v1/builds/{id}/install-options was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds/{id}/install-options 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
- v1 GET /v1/builds/{id}/tree (getBuildTree; fixed; compatible)
- Before: GET /v1/builds/{id}/tree was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds/{id}/tree 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
- v1 GET /v1/changelist/{id} (getChangelogEntry; fixed; compatible)
- Before: GET /v1/changelist/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/changelist/{id} 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
- v1 GET /v1/collections/{slug} (getCollection; fixed; compatible)
- Before: GET /v1/collections/{slug} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/collections/{slug} 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
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; fixed; compatible)
- Before: GET /v1/collections/{slug}/{week} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/collections/{slug}/{week} 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
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; fixed; compatible)
- Before: GET /v1/collections/{slug}/{week}/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/collections/{slug}/{week}/og 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
- v1 GET /v1/featured (getFeaturedGames; fixed; compatible)
- Before: GET /v1/featured was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/featured 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
- v1 GET /v1/franchises/{slug} (getFranchise; fixed; compatible)
- Before: GET /v1/franchises/{slug} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/franchises/{slug} 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
- v1 GET /v1/free-games/og (getFreeGamesOg; fixed; compatible)
- Before: GET /v1/free-games/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/free-games/og 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
- v1 GET /v1/free-games/stats (getFreeGamesStats; fixed; compatible)
- Before: GET /v1/free-games/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/free-games/stats 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
- v1 GET /v1/game-awards (getGameAwards; fixed; compatible)
- Before: GET /v1/game-awards was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/game-awards 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
- v1 GET /v1/game-awards/og (getGameAwardsOg; fixed; compatible)
- Before: GET /v1/game-awards/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/game-awards/og 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
- 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
- v1 GET /v1/stats/homepage (getHomepageStats; fixed; compatible)
- Before: GET /v1/stats/homepage was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/stats/homepage 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
- v1 GET /v1/items/{id} (getItem; fixed; compatible)
- Before: GET /v1/items/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items/{id} 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
- v1 GET /v1/items/{id}/assets (getItemAssets; fixed; compatible)
- Before: GET /v1/items/{id}/assets was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items/{id}/assets 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
- v1 GET /v1/items/{id}/builds (getItemBuilds; fixed; compatible)
- Before: GET /v1/items/{id}/builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items/{id}/builds 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
- v1 GET /v1/items/{id}/changelog (getItemChangelog; fixed; compatible)
- Before: GET /v1/items/{id}/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items/{id}/changelog 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
- v1 GET /v1/items/{id}/offer (getItemOffer; fixed; compatible)
- Before: GET /v1/items/{id}/offer was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items/{id}/offer 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
- v1 POST /v1/items/bulk (getItemsBulk; fixed; compatible)
- Before: POST /v1/items/bulk was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/items/bulk 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
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; fixed; compatible)
- Before: GET /v1/items-sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items-sitemap.xml 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
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; fixed; compatible)
- Before: GET /v1/items/sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items/sitemap.xml 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
- v1 GET /v1/latest-games (getLatestGames; fixed; compatible)
- Before: GET /v1/latest-games was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/latest-games 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
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; fixed; compatible)
- Before: GET /v1/stats/creations/monthly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/stats/creations/monthly 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
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; fixed; compatible)
- Before: GET /v1/stats/releases/monthly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/stats/releases/monthly 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
- v1 GET /v1/offers/{id} (getOffer; fixed; compatible)
- Before: GET /v1/offers/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id} 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
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; fixed; compatible)
- Before: GET /v1/offers/{id}/achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/achievements 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
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; fixed; compatible)
- Before: GET /v1/offers/{id}/age-rating was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/age-rating 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
- v1 GET /v1/offers/{id}/assets (getOfferAssets; fixed; compatible)
- Before: GET /v1/offers/{id}/assets was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/assets 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
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; fixed; compatible)
- Before: GET /v1/offers/{id}/builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/builds 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
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; fixed; compatible)
- Before: GET /v1/offers/{id}/bundle was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/bundle 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
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; fixed; compatible)
- Before: GET /v1/offer-by-slug/{slug} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offer-by-slug/{slug} 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
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; fixed; compatible)
- Before: GET /v1/offers/{id}/changelog/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/changelog/stats 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
- v1 GET /v1/offers/{id}/collection (getOfferCollection; fixed; compatible)
- Before: GET /v1/offers/{id}/collection was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/collection 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
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; fixed; compatible)
- Before: GET /v1/offers/{id}/collections/{collection} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/collections/{collection} 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
- v1 GET /v1/offers/events/{id} (getOfferEvent; fixed; compatible)
- Before: GET /v1/offers/events/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/events/{id} 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
- v1 GET /v1/offers/{id}/features (getOfferFeatures; fixed; compatible)
- Before: GET /v1/offers/{id}/features was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/features 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
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; fixed; compatible)
- Before: GET /v1/offers/{id}/franchises was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/franchises 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
- v1 GET /v1/offers/{id}/genres (getOfferGenres; fixed; compatible)
- Before: GET /v1/offers/{id}/genres was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/genres 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
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; fixed; compatible)
- Before: GET /v1/offers/{id}/giveaways was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/giveaways 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
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; fixed; compatible)
- Before: GET /v1/offers/{id}/has-prepurchase was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/has-prepurchase 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
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; fixed; compatible)
- Before: GET /v1/offers/{id}/has-regular was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/has-regular 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
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; fixed; compatible)
- Before: GET /v1/offers/{id}/hltb was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/hltb 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
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; fixed; compatible)
- Before: GET /v1/offers/{id}/igdb was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/igdb 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
- v1 GET /v1/offers/{id}/items (getOfferItems; fixed; compatible)
- Before: GET /v1/offers/{id}/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/items 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
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; fixed; compatible)
- Before: GET /v1/offers/{id}/mappings was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/mappings 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
- v1 GET /v1/offers/{id}/media (getOfferMedia; fixed; compatible)
- Before: GET /v1/offers/{id}/media was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/media 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
- v1 GET /v1/offers/{id}/og (getOfferOg; fixed; compatible)
- Before: GET /v1/offers/{id}/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/og 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
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; fixed; compatible)
- Before: GET /v1/offers/{id}/og.webp was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/og.webp 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
- v1 GET /v1/offers/{id}/overview (getOfferOverview; fixed; compatible)
- Before: GET /v1/offers/{id}/overview was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/overview 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
- v1 GET /v1/offers/{id}/polls (getOfferPolls; fixed; compatible)
- Before: GET /v1/offers/{id}/polls was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/polls 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
- v1 GET /v1/offers/{id}/price (getOfferPrice; fixed; compatible)
- Before: GET /v1/offers/{id}/price was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/price 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
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; fixed; compatible)
- Before: GET /v1/offers/{id}/price/fairness was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/price/fairness 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
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; fixed; compatible)
- Before: GET /v1/offers/{id}/price-stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/price-stats 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
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; fixed; compatible)
- Before: GET /v1/offers/{id}/ratings was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/ratings 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
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; fixed; compatible)
- Before: GET /v1/offers/{id}/regional-price was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/regional-price 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
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; fixed; compatible)
- Before: GET /v1/offers/{id}/requirements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/requirements 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
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; fixed; compatible)
- Before: GET /v1/offers/{id}/reviews-summary was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/reviews-summary 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
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; fixed; compatible)
- Before: POST /v1/items/bulk/offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/items/bulk/offers 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
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; fixed; compatible)
- Before: GET /v1/offers/{id}/suggestions was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/suggestions 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
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; fixed; compatible)
- Before: GET /v1/offers/{id}/technologies was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/technologies 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
- v1 GET /v1/offers/{id}/tops (getOfferTops; fixed; compatible)
- Before: GET /v1/offers/{id}/tops was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/tops 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
- v1 GET /v1/profiles/{id} (getProfile; fixed; compatible)
- Before: GET /v1/profiles/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id} 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
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; fixed; compatible)
- Before: GET /v1/profiles/{id}/achievements/{sandboxId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id}/achievements/{sandboxId} 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
- v1 GET /v1/profiles/{id}/information (getProfileInformation; fixed; compatible)
- Before: GET /v1/profiles/{id}/information was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id}/information 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
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; fixed; compatible)
- Before: GET /v1/profiles/{id}/random-game was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id}/random-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
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; fixed; compatible)
- Before: GET /v1/profiles/{id}/rare-achievements/{sandboxId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id}/rare-achievements/{sandboxId} 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
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; fixed; compatible)
- Before: GET /v1/profiles/sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/sitemap.xml 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
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; fixed; compatible)
- Before: GET /v1/promotions/{id}/cover was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/promotions/{id}/cover 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
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; fixed; compatible)
- Before: GET /v1/promotions-sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/promotions-sitemap.xml 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
- v1 GET /v1/region (getRegion; fixed; compatible)
- Before: GET /v1/region was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/region 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
- v1 GET /v1/offers/{id}/related (getRelatedOffers; fixed; compatible)
- Before: GET /v1/offers/{id}/related was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/related 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
- v1 GET /v1/robots.txt (getRobots; fixed; compatible)
- Before: GET /v1/robots.txt was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/robots.txt 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
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId} 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
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; fixed; compatible)
- Before: GET /v1/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 /v1/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
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/changelog 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
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; fixed; compatible)
- Before: GET /v1/sandboxes/sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/sitemap.xml 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
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/og was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/og 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
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/og.webp was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/og.webp 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
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/stats 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
- v1 GET /v1/search/{id} (getSearchQuery; fixed; compatible)
- Before: GET /v1/search/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search/{id} 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
- v1 GET /v1/search/{id}/count (getSearchQueryCount; fixed; compatible)
- Before: GET /v1/search/{id}/count was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search/{id}/count 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
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; fixed; compatible)
- Before: GET /v1/sellers/{id}/cover was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sellers/{id}/cover 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
- v1 GET /v1/sellers/{id}/stats (getSellerStats; fixed; compatible)
- Before: GET /v1/sellers/{id}/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sellers/{id}/stats 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
- v1 GET /v1/sitemap.xml (getSitemap; fixed; compatible)
- Before: GET /v1/sitemap.xml was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sitemap.xml 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
- v1 GET /v1/stats (getStats; fixed; compatible)
- Before: GET /v1/stats was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/stats 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
- v1 GET /v1/open-api.json (getV1OpenApi; fixed; compatible)
- Before: GET /v1/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 /v1/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
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; fixed; compatible)
- Before: GET /v1/stats/creations/yearly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/stats/creations/yearly 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
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; fixed; compatible)
- Before: GET /v1/stats/releases/yearly was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/stats/releases/yearly 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
- v1 POST /v1/catalog/hydrate (hydrateCatalog; fixed; compatible)
- Before: POST /v1/catalog/hydrate was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/catalog/hydrate 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
- v1 GET /v1/active-sales (listActiveSales; fixed; compatible)
- Before: GET /v1/active-sales was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/active-sales 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
- v1 GET /v1/builds/{id}/files (listBuildFiles; fixed; compatible)
- Before: GET /v1/builds/{id}/files was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds/{id}/files 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
- v1 GET /v1/builds/{id}/items (listBuildItems; fixed; compatible)
- Before: GET /v1/builds/{id}/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds/{id}/items 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
- v1 GET /v1/builds (listBuilds; fixed; compatible)
- Before: GET /v1/builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/builds 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
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; fixed; compatible)
- Before: GET /v1/offers/{id}/in-bundle was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/in-bundle 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
- v1 GET /v1/changelist (listChangelist; fixed; compatible)
- Before: GET /v1/changelist was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/changelist 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
- v1 GET /v1/changelog (listChangelog; fixed; compatible)
- Before: GET /v1/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/changelog 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
- v1 GET /v1/countries (listCountries; fixed; compatible)
- Before: GET /v1/countries was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/countries 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
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; fixed; compatible)
- Before: GET /v1/offers/featured-discounts was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/featured-discounts 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
- v1 GET /v1/free-games (listFreeGames; fixed; compatible)
- Before: GET /v1/free-games was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/free-games 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
- v1 GET /v1/free-games/sellers (listFreeGameSellers; fixed; compatible)
- Before: GET /v1/free-games/sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/free-games/sellers 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
- v1 GET /v1/free-games/history (listFreeGamesHistory; fixed; compatible)
- Before: GET /v1/free-games/history was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/free-games/history 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
- v1 GET /v1/items (listItems; fixed; compatible)
- Before: GET /v1/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items 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
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; fixed; compatible)
- Before: GET /v1/items-from-offer/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/items-from-offer/{id} 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
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; fixed; compatible)
- Before: GET /v1/offers/latest-achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/latest-achievements 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
- v1 GET /v1/offers/latest-released (listLatestReleased; fixed; compatible)
- Before: GET /v1/offers/latest-released was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/latest-released 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
- v1 GET /v1/free-games/mobile (listMobileFreeGames; fixed; compatible)
- Before: GET /v1/free-games/mobile was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/free-games/mobile 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
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; fixed; compatible)
- Before: GET /v1/offers/{id}/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/changelog 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
- v1 GET /v1/offers/events (listOfferEvents; fixed; compatible)
- Before: GET /v1/offers/events was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/events 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
- v1 GET /v1/offers/genres (listOfferGenres; fixed; compatible)
- Before: GET /v1/offers/genres was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/genres 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
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; fixed; compatible)
- Before: GET /v1/offers/{id}/price-history was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/price-history 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
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; fixed; compatible)
- Before: GET /v1/offers/{id}/reviews was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/{id}/reviews 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
- v1 GET /v1/offers (listOffers; fixed; compatible)
- Before: GET /v1/offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers 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
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; fixed; compatible)
- Before: GET /v1/profiles/{id}/achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id}/achievements 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
- v1 GET /v1/profiles/{id}/games (listProfileGames; fixed; compatible)
- Before: GET /v1/profiles/{id}/games was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id}/games 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
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; fixed; compatible)
- Before: GET /v1/profiles/leaderboard was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/leaderboard 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
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; fixed; compatible)
- Before: GET /v1/profiles/{id}/rare-achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/profiles/{id}/rare-achievements 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
- v1 GET /v1/promotions/{id} (listPromotionOffers; fixed; compatible)
- Before: GET /v1/promotions/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/promotions/{id} 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
- v1 GET /v1/promotions (listPromotions; fixed; compatible)
- Before: GET /v1/promotions was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/promotions 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
- v1 GET /v1/regions (listRegions; fixed; compatible)
- Before: GET /v1/regions was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/regions 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
- v1 GET /v1/sales (listSales; fixed; compatible)
- Before: GET /v1/sales was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sales 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
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/achievements was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/achievements 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
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/assets was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/assets 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
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/builds was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/builds 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
- v1 GET /v1/sandboxes (listSandboxes; fixed; compatible)
- Before: GET /v1/sandboxes was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes 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
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/items 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
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; fixed; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sandboxes/{sandboxId}/offers 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
- v1 GET /v1/search/developers (listSearchDevelopers; fixed; compatible)
- Before: GET /v1/search/developers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search/developers 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
- v1 GET /v1/search/offer-types (listSearchOfferTypes; fixed; compatible)
- Before: GET /v1/search/offer-types was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search/offer-types 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
- v1 GET /v1/search/publishers (listSearchPublishers; fixed; compatible)
- Before: GET /v1/search/publishers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search/publishers 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
- v1 GET /v1/search/tags (listSearchTags; fixed; compatible)
- Before: GET /v1/search/tags was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search/tags 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
- v1 GET /v1/sellers/{id} (listSellerOffers; fixed; compatible)
- Before: GET /v1/sellers/{id} was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sellers/{id} 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
- v1 GET /v1/sellers (listSellers; fixed; compatible)
- Before: GET /v1/sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/sellers 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
- v1 GET /v1/tags (listTags; fixed; compatible)
- Before: GET /v1/tags was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/tags 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
- v1 GET /v1/offers/top-sellers (listTopSellers; fixed; compatible)
- Before: GET /v1/offers/top-sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/top-sellers 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
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; fixed; compatible)
- Before: GET /v1/offers/top-wishlisted was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/top-wishlisted 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
- v1 GET /v1/offers/upcoming (listUpcomingOffers; fixed; compatible)
- Before: GET /v1/offers/upcoming was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/offers/upcoming 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
- v1 GET /v1/multisearch/items (multisearchItems; fixed; compatible)
- Before: GET /v1/multisearch/items was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/multisearch/items 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
- v1 GET /v1/multisearch/offers (multisearchOffers; fixed; compatible)
- Before: GET /v1/multisearch/offers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/multisearch/offers 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
- v1 GET /v1/multisearch/sellers (multisearchSellers; fixed; compatible)
- Before: GET /v1/multisearch/sellers was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/multisearch/sellers 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
- v1 POST /v1/search/natural-language (naturalLanguageSearch; fixed; compatible)
- Before: POST /v1/search/natural-language was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/search/natural-language 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
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; fixed; compatible)
- Before: POST /v1/builds/resolve-launcher-records was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/builds/resolve-launcher-records 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
- v1 GET /v1/search/changelog (searchChangelog; fixed; compatible)
- Before: GET /v1/search/changelog was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search/changelog 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
- v1 GET /v1/free-games/search (searchFreeGames; fixed; compatible)
- Before: GET /v1/free-games/search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/free-games/search 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
- v1 GET /v1/search (searchOffers; fixed; compatible)
- Before: GET /v1/search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: GET /v1/search 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
- v1 POST /v1/search (searchOffersRedirect; fixed; compatible)
- Before: POST /v1/search was unavailable during API startup while v1 MongoDB index creation was pending; the proxy returned 502 before HTTP began listening.
- After: POST /v1/search 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 — Try v1 operations with ten-minute project console sessions
Record: project-console-sessions.
- v1 GET /v1/autocomplete (autocomplete; added; compatible)
- Before: Trying GET /v1/autocomplete in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/autocomplete with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/offers/exists (checkOfferExistence; added; compatible)
- Before: Trying POST /v1/offers/exists in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/offers/exists with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/offers/slugs (checkOfferSlugs; added; compatible)
- Before: Trying POST /v1/offers/slugs in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/offers/slugs with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; added; compatible)
- Before: Trying GET /v1/builds/{targetId}/compare/{baseId} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds/{targetId}/compare/{baseId} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/assets/{id} (getAsset; added; compatible)
- Before: Trying GET /v1/assets/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/assets/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/base-game/{namespace} (getBaseGame; added; compatible)
- Before: Trying GET /v1/base-game/{namespace} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/base-game/{namespace} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds/{id} (getBuild; added; compatible)
- Before: Trying GET /v1/builds/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds/{id}/history (getBuildHistory; added; compatible)
- Before: Trying GET /v1/builds/{id}/history in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds/{id}/history with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; added; compatible)
- Before: Trying GET /v1/builds/{id}/install-options in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds/{id}/install-options with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds/{id}/tree (getBuildTree; added; compatible)
- Before: Trying GET /v1/builds/{id}/tree in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds/{id}/tree with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/changelist/{id} (getChangelogEntry; added; compatible)
- Before: Trying GET /v1/changelist/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/changelist/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/collections/{slug} (getCollection; added; compatible)
- Before: Trying GET /v1/collections/{slug} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/collections/{slug} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; added; compatible)
- Before: Trying GET /v1/collections/{slug}/{week} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/collections/{slug}/{week} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; added; compatible)
- Before: Trying GET /v1/collections/{slug}/{week}/og in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/collections/{slug}/{week}/og with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/featured (getFeaturedGames; added; compatible)
- Before: Trying GET /v1/featured in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/featured with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/franchises/{slug} (getFranchise; added; compatible)
- Before: Trying GET /v1/franchises/{slug} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/franchises/{slug} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/free-games/og (getFreeGamesOg; added; compatible)
- Before: Trying GET /v1/free-games/og in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/free-games/og with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/free-games/stats (getFreeGamesStats; added; compatible)
- Before: Trying GET /v1/free-games/stats in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/free-games/stats with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/game-awards (getGameAwards; added; compatible)
- Before: Trying GET /v1/game-awards in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/game-awards with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/game-awards/og (getGameAwardsOg; added; compatible)
- Before: Trying GET /v1/game-awards/og in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/game-awards/og with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/stats/homepage (getHomepageStats; added; compatible)
- Before: Trying GET /v1/stats/homepage in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/stats/homepage with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items/{id} (getItem; added; compatible)
- Before: Trying GET /v1/items/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items/{id}/assets (getItemAssets; added; compatible)
- Before: Trying GET /v1/items/{id}/assets in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items/{id}/assets with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items/{id}/builds (getItemBuilds; added; compatible)
- Before: Trying GET /v1/items/{id}/builds in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items/{id}/builds with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items/{id}/changelog (getItemChangelog; added; compatible)
- Before: Trying GET /v1/items/{id}/changelog in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items/{id}/changelog with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items/{id}/offer (getItemOffer; added; compatible)
- Before: Trying GET /v1/items/{id}/offer in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items/{id}/offer with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/items/bulk (getItemsBulk; added; compatible)
- Before: Trying POST /v1/items/bulk in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/items/bulk with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; added; compatible)
- Before: Trying GET /v1/items-sitemap.xml in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items-sitemap.xml with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; added; compatible)
- Before: Trying GET /v1/items/sitemap.xml in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items/sitemap.xml with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/latest-games (getLatestGames; added; compatible)
- Before: Trying GET /v1/latest-games in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/latest-games with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; added; compatible)
- Before: Trying GET /v1/stats/creations/monthly in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/stats/creations/monthly with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; added; compatible)
- Before: Trying GET /v1/stats/releases/monthly in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/stats/releases/monthly with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id} (getOffer; added; compatible)
- Before: Trying GET /v1/offers/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; added; compatible)
- Before: Trying GET /v1/offers/{id}/achievements in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/achievements with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; added; compatible)
- Before: Trying GET /v1/offers/{id}/age-rating in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/age-rating with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/assets (getOfferAssets; added; compatible)
- Before: Trying GET /v1/offers/{id}/assets in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/assets with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; added; compatible)
- Before: Trying GET /v1/offers/{id}/builds in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/builds with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; added; compatible)
- Before: Trying GET /v1/offers/{id}/bundle in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/bundle with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; added; compatible)
- Before: Trying GET /v1/offer-by-slug/{slug} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offer-by-slug/{slug} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; added; compatible)
- Before: Trying GET /v1/offers/{id}/changelog/stats in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/changelog/stats with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/collection (getOfferCollection; added; compatible)
- Before: Trying GET /v1/offers/{id}/collection in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/collection with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; added; compatible)
- Before: Trying GET /v1/offers/{id}/collections/{collection} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/collections/{collection} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/events/{id} (getOfferEvent; added; compatible)
- Before: Trying GET /v1/offers/events/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/events/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/features (getOfferFeatures; added; compatible)
- Before: Trying GET /v1/offers/{id}/features in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/features with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; added; compatible)
- Before: Trying GET /v1/offers/{id}/franchises in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/franchises with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/genres (getOfferGenres; added; compatible)
- Before: Trying GET /v1/offers/{id}/genres in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/genres with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; added; compatible)
- Before: Trying GET /v1/offers/{id}/giveaways in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/giveaways with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; added; compatible)
- Before: Trying GET /v1/offers/{id}/has-prepurchase in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/has-prepurchase with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; added; compatible)
- Before: Trying GET /v1/offers/{id}/has-regular in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/has-regular with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; added; compatible)
- Before: Trying GET /v1/offers/{id}/hltb in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/hltb with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; added; compatible)
- Before: Trying GET /v1/offers/{id}/igdb in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/igdb with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/items (getOfferItems; added; compatible)
- Before: Trying GET /v1/offers/{id}/items in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/items with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; added; compatible)
- Before: Trying GET /v1/offers/{id}/mappings in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/mappings with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/media (getOfferMedia; added; compatible)
- Before: Trying GET /v1/offers/{id}/media in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/media with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/og (getOfferOg; added; compatible)
- Before: Trying GET /v1/offers/{id}/og in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/og with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; added; compatible)
- Before: Trying GET /v1/offers/{id}/og.webp in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/og.webp with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/overview (getOfferOverview; added; compatible)
- Before: Trying GET /v1/offers/{id}/overview in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/overview with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/polls (getOfferPolls; added; compatible)
- Before: Trying GET /v1/offers/{id}/polls in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/polls with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/price (getOfferPrice; added; compatible)
- Before: Trying GET /v1/offers/{id}/price in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/price with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; added; compatible)
- Before: Trying GET /v1/offers/{id}/price/fairness in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/price/fairness with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; added; compatible)
- Before: Trying GET /v1/offers/{id}/price-stats in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/price-stats with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; added; compatible)
- Before: Trying GET /v1/offers/{id}/ratings in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/ratings with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; added; compatible)
- Before: Trying GET /v1/offers/{id}/regional-price in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/regional-price with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; added; compatible)
- Before: Trying GET /v1/offers/{id}/requirements in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/requirements with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; added; compatible)
- Before: Trying GET /v1/offers/{id}/reviews-summary in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/reviews-summary with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; added; compatible)
- Before: Trying POST /v1/items/bulk/offers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/items/bulk/offers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; added; compatible)
- Before: Trying GET /v1/offers/{id}/suggestions in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/suggestions with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; added; compatible)
- Before: Trying GET /v1/offers/{id}/technologies in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/technologies with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/tops (getOfferTops; added; compatible)
- Before: Trying GET /v1/offers/{id}/tops in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/tops with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id} (getProfile; added; compatible)
- Before: Trying GET /v1/profiles/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; added; compatible)
- Before: Trying GET /v1/profiles/{id}/achievements/{sandboxId} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id}/achievements/{sandboxId} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id}/information (getProfileInformation; added; compatible)
- Before: Trying GET /v1/profiles/{id}/information in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id}/information with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; added; compatible)
- Before: Trying GET /v1/profiles/{id}/random-game in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id}/random-game with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; added; compatible)
- Before: Trying GET /v1/profiles/{id}/rare-achievements/{sandboxId} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id}/rare-achievements/{sandboxId} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; added; compatible)
- Before: Trying GET /v1/profiles/sitemap.xml in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/sitemap.xml with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; added; compatible)
- Before: Trying GET /v1/promotions/{id}/cover in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/promotions/{id}/cover with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; added; compatible)
- Before: Trying GET /v1/promotions-sitemap.xml in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/promotions-sitemap.xml with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/region (getRegion; added; compatible)
- Before: Trying GET /v1/region in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/region with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/related (getRelatedOffers; added; compatible)
- Before: Trying GET /v1/offers/{id}/related in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/related with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/robots.txt (getRobots; added; compatible)
- Before: Trying GET /v1/robots.txt in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/robots.txt with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/base-game in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/base-game with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/changelog in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/changelog with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; added; compatible)
- Before: Trying GET /v1/sandboxes/sitemap.xml in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/sitemap.xml with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/og in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/og with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/og.webp in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/og.webp with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/stats in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/stats with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search/{id} (getSearchQuery; added; compatible)
- Before: Trying GET /v1/search/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search/{id}/count (getSearchQueryCount; added; compatible)
- Before: Trying GET /v1/search/{id}/count in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search/{id}/count with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; added; compatible)
- Before: Trying GET /v1/sellers/{id}/cover in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sellers/{id}/cover with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sellers/{id}/stats (getSellerStats; added; compatible)
- Before: Trying GET /v1/sellers/{id}/stats in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sellers/{id}/stats with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sitemap.xml (getSitemap; added; compatible)
- Before: Trying GET /v1/sitemap.xml in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sitemap.xml with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/stats (getStats; added; compatible)
- Before: Trying GET /v1/stats in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/stats with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; added; compatible)
- Before: Trying GET /v1/stats/creations/yearly in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/stats/creations/yearly with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; added; compatible)
- Before: Trying GET /v1/stats/releases/yearly in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/stats/releases/yearly with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/catalog/hydrate (hydrateCatalog; added; compatible)
- Before: Trying POST /v1/catalog/hydrate in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/catalog/hydrate with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/active-sales (listActiveSales; added; compatible)
- Before: Trying GET /v1/active-sales in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/active-sales with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds/{id}/files (listBuildFiles; added; compatible)
- Before: Trying GET /v1/builds/{id}/files in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds/{id}/files with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds/{id}/items (listBuildItems; added; compatible)
- Before: Trying GET /v1/builds/{id}/items in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds/{id}/items with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/builds (listBuilds; added; compatible)
- Before: Trying GET /v1/builds in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/builds with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; added; compatible)
- Before: Trying GET /v1/offers/{id}/in-bundle in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/in-bundle with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/changelist (listChangelist; added; compatible)
- Before: Trying GET /v1/changelist in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/changelist with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/changelog (listChangelog; added; compatible)
- Before: Trying GET /v1/changelog in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/changelog with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/countries (listCountries; added; compatible)
- Before: Trying GET /v1/countries in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/countries with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; added; compatible)
- Before: Trying GET /v1/offers/featured-discounts in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/featured-discounts with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/free-games (listFreeGames; added; compatible)
- Before: Trying GET /v1/free-games in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/free-games with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/free-games/sellers (listFreeGameSellers; added; compatible)
- Before: Trying GET /v1/free-games/sellers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/free-games/sellers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/free-games/history (listFreeGamesHistory; added; compatible)
- Before: Trying GET /v1/free-games/history in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/free-games/history with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items (listItems; added; compatible)
- Before: Trying GET /v1/items in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; added; compatible)
- Before: Trying GET /v1/items-from-offer/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/items-from-offer/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; added; compatible)
- Before: Trying GET /v1/offers/latest-achievements in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/latest-achievements with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/latest-released (listLatestReleased; added; compatible)
- Before: Trying GET /v1/offers/latest-released in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/latest-released with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/free-games/mobile (listMobileFreeGames; added; compatible)
- Before: Trying GET /v1/free-games/mobile in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/free-games/mobile with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; added; compatible)
- Before: Trying GET /v1/offers/{id}/changelog in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/changelog with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/events (listOfferEvents; added; compatible)
- Before: Trying GET /v1/offers/events in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/events with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/genres (listOfferGenres; added; compatible)
- Before: Trying GET /v1/offers/genres in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/genres with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; added; compatible)
- Before: Trying GET /v1/offers/{id}/price-history in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/price-history with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; added; compatible)
- Before: Trying GET /v1/offers/{id}/reviews in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/{id}/reviews with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers (listOffers; added; compatible)
- Before: Trying GET /v1/offers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; added; compatible)
- Before: Trying GET /v1/profiles/{id}/achievements in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id}/achievements with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id}/games (listProfileGames; added; compatible)
- Before: Trying GET /v1/profiles/{id}/games in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id}/games with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; added; compatible)
- Before: Trying GET /v1/profiles/leaderboard in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/leaderboard with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; added; compatible)
- Before: Trying GET /v1/profiles/{id}/rare-achievements in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/profiles/{id}/rare-achievements with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/promotions/{id} (listPromotionOffers; added; compatible)
- Before: Trying GET /v1/promotions/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/promotions/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/promotions (listPromotions; added; compatible)
- Before: Trying GET /v1/promotions in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/promotions with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/regions (listRegions; added; compatible)
- Before: Trying GET /v1/regions in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/regions with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sales (listSales; added; compatible)
- Before: Trying GET /v1/sales in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sales with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/achievements in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/achievements with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/assets in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/assets with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/builds in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/builds with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes (listSandboxes; added; compatible)
- Before: Trying GET /v1/sandboxes in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/items in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/items with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; added; compatible)
- Before: Trying GET /v1/sandboxes/{sandboxId}/offers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sandboxes/{sandboxId}/offers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search/developers (listSearchDevelopers; added; compatible)
- Before: Trying GET /v1/search/developers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search/developers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search/offer-types (listSearchOfferTypes; added; compatible)
- Before: Trying GET /v1/search/offer-types in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search/offer-types with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search/publishers (listSearchPublishers; added; compatible)
- Before: Trying GET /v1/search/publishers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search/publishers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search/tags (listSearchTags; added; compatible)
- Before: Trying GET /v1/search/tags in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search/tags with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sellers/{id} (listSellerOffers; added; compatible)
- Before: Trying GET /v1/sellers/{id} in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sellers/{id} with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/sellers (listSellers; added; compatible)
- Before: Trying GET /v1/sellers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/sellers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/tags (listTags; added; compatible)
- Before: Trying GET /v1/tags in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/tags with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/top-sellers (listTopSellers; added; compatible)
- Before: Trying GET /v1/offers/top-sellers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/top-sellers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; added; compatible)
- Before: Trying GET /v1/offers/top-wishlisted in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/top-wishlisted with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/offers/upcoming (listUpcomingOffers; added; compatible)
- Before: Trying GET /v1/offers/upcoming in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/offers/upcoming with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/multisearch/items (multisearchItems; added; compatible)
- Before: Trying GET /v1/multisearch/items in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/multisearch/items with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/multisearch/offers (multisearchOffers; added; compatible)
- Before: Trying GET /v1/multisearch/offers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/multisearch/offers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/multisearch/sellers (multisearchSellers; added; compatible)
- Before: Trying GET /v1/multisearch/sellers in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/multisearch/sellers with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/search/natural-language (naturalLanguageSearch; added; compatible)
- Before: Trying POST /v1/search/natural-language in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/search/natural-language with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; added; compatible)
- Before: Trying POST /v1/builds/resolve-launcher-records in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/builds/resolve-launcher-records with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search/changelog (searchChangelog; added; compatible)
- Before: Trying GET /v1/search/changelog in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search/changelog with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/free-games/search (searchFreeGames; added; compatible)
- Before: Trying GET /v1/free-games/search in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/free-games/search with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/search (searchOffers; added; compatible)
- Before: Trying GET /v1/search in the API Reference required pasting an existing API key secret.
- After: The project owner can also try GET /v1/search with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 POST /v1/search (searchOffersRedirect; added; compatible)
- Before: Trying POST /v1/search in the API Reference required pasting an existing API key secret.
- After: The project owner can also try POST /v1/search with a console-only credential lasting at most ten minutes, bound to the same dashboard login. Requests share a stable per-project console quota and count toward project analytics and endpoint alerts. Public API key behavior is preserved.
- Client action: None
- v1 GET /v1/open-api.json (getV1OpenApi; changed; compatible)
- Before: The v1 description documented only public API key authentication for data operations.
- After: The v1 description also documents optional ten-minute console sessions bound to the signed-in dashboard. Public application security schemes and operation schemas remain unchanged.
- Client action: None
Verification: dashboard/tests/console-sessions.test.ts; dashboard/tests/explorer.test.ts.
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
- v1 GET /v1/open-api.json (getV1OpenApi; fixed; compatible)
- Before: The Worker could throw while modifying immutable upstream response headers, returning HTTP 500 and preventing the explorer from loading the deployed contract.
- After: The Worker clones the response before applying its existing headers, preserving the deployed OpenAPI response status and streaming body. The API contract and routing 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/autocomplete (autocomplete; added; compatible)
- Before: GET /v1/autocomplete was not available in the versioned API.
- After: Offer title autocomplete. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 POST /v1/offers/exists (checkOfferExistence; added; compatible)
- Before: POST /v1/offers/exists was not available in the versioned API.
- After: Check multiple offer IDs. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 POST /v1/offers/slugs (checkOfferSlugs; added; compatible)
- Before: POST /v1/offers/slugs was not available in the versioned API.
- After: Resolve multiple offer slugs. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/builds/{targetId}/compare/{baseId} (compareBuilds; added; compatible)
- Before: GET /v1/builds/{targetId}/compare/{baseId} was not available in the versioned API.
- After: Compare two stored build snapshots. Compares immutable file snapshots by full path, ordered by
fileNamein the requested direction with an opaquefileNamecursor. Responding requires streaming both stored snapshots so the summary, top files, and top directories are complete; the page size is bounded, the scan is not. Full-download deltas are not patch-download estimates. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/assets/{id} (getAsset; added; compatible)
- Before: GET /v1/assets/{id} was not available in the versioned API.
- After: Get an asset. Looks up a single catalog asset by its Epic Games artifact ID and returns the serialized asset document. Returns
404when no asset matches. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/base-game/{namespace} (getBaseGame; added; compatible)
- Before: GET /v1/base-game/{namespace} was not available in the versioned API.
- After: Resolve a namespace's base game. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/builds/{id} (getBuild; added; compatible)
- Before: GET /v1/builds/{id} was not available in the versioned API.
- After: Get a sanitized build snapshot. Returns one build summary with manifest status, sizes, technologies, and stored size fallbacks from the matching platform asset. Raw manifest locations are never returned. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/builds/{id}/history (getBuildHistory; added; compatible)
- Before: GET /v1/builds/{id}/history was not available in the versioned API.
- After: List comparison candidates for a build. Returns chronological observations for the same label stream or platform as the build, ordered by
firstSeenAtdescending,createdAtdescending, and_iddescending. Each entry reports whether it has a comparable stored snapshot and whether it belongs to the same stream;meta.previousComparableBuildIdidentifies the previous comparable snapshot. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/builds/{id}/install-options (getBuildInstallOptions; added; compatible)
- Before: GET /v1/builds/{id}/install-options was not available in the versioned API.
- After: Summarize install tags in a build. Returns a bounded map keyed by install tag, with file counts and total bytes. The map is not paginated;
meta.truncatedreports whether the safety cap was reached. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/builds/{id}/tree (getBuildTree; added; compatible)
- Before: GET /v1/builds/{id}/tree was not available in the versioned API.
- After: Expand one directory of a build file tree. Returns only the immediate child files and directories of the requested manifest directory, ordered by node type and then name. Expand a directory by passing the
pathreturned for that node. Passmeta.pagination.nextCursorascursorto fetch the next page. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/changelist/{id} (getChangelogEntry; added; compatible)
- Before: GET /v1/changelist/{id} was not available in the versioned API.
- After: Get a catalog change. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/collections/{slug} (getCollection; added; compatible)
- Before: GET /v1/collections/{slug} was not available in the versioned API.
- After: Get a collection. Cursor-paginated collection positions ordered by
positionascending with the offer ID as a unique tie-breaker. Positions with a non-positive position are excluded.countryselects the pricing region andlocalelocalizes offer text; cookies are never used. Cursors are bound to the collection, ordering, country, locale, and page size. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/collections/{slug}/{week} (getCollectionWeek; added; compatible)
- Before: GET /v1/collections/{slug}/{week} was not available in the versioned API.
- After: Get a collection for one ISO week. Cursor-paginated positions for one ISO week. Each offer is represented by its most recent in-week position; only entries with a positive position are included. The
weekpath parameter must matchYYYYWNNand name a real ISO week, otherwise the endpoint returns a 400 problem instead of the legacy 500. Cursors are bound to the collection, week, ordering, country, locale, and page size. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/collections/{slug}/{week}/og (getCollectionWeekOg; added; compatible)
- Before: GET /v1/collections/{slug}/{week}/og was not available in the versioned API.
- After: Weekly collection share image. Compatibility redirect to the canonical native weekly collection image. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/featured (getFeaturedGames; added; compatible)
- Before: GET /v1/featured was not available in the versioned API.
- After: Featured storefront games. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/franchises/{slug} (getFranchise; added; compatible)
- Before: GET /v1/franchises/{slug} was not available in the versioned API.
- After: Get a franchise. Returns a franchise and a cursor-paginated page of its offers, ordered by
releaseDatedescending with the offeridascending as tie-breaker. Offers are localized withlocaleand priced for the Epic pricing region that containscountry. Thestatsobject aggregates achievements and time-to-beat data over every offer in the franchise, not only the returned page. Cookies are never used. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/free-games/og (getFreeGamesOg; added; compatible)
- Before: GET /v1/free-games/og was not available in the versioned API.
- After: Free games share image. Compatibility redirect to the canonical native free-games image. Existing image URLs remain available for embeds and crawlers. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/free-games/stats (getFreeGamesStats; added; compatible)
- Before: GET /v1/free-games/stats was not available in the versioned API.
- After: Free game statistics. Returns giveaway totals, distinct seller counts, repeated giveaways, and the summed value of all recorded giveaways for the selected pricing region. When no price rows exist the value object is still returned with zero amounts and nullable currency codes instead of failing. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/game-awards (getGameAwards; added; compatible)
- Before: GET /v1/game-awards was not available in the versioned API.
- After: The Game Awards modules. Returns the storefront modules for The Game Awards event, each with its localized and expanded offers and current regional price. Modules are ordered by
moduleIndex; modules without referenced offers are omitted. OG image generation remains outside v1. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/game-awards/og (getGameAwardsOg; added; compatible)
- Before: GET /v1/game-awards/og was not available in the versioned API.
- After: The Game Awards share image. Compatibility redirect to the canonical native Game Awards image. Requires an API key with stats:read permission; the gateway enforces per-key quotas.
- Client action: None
- 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
- v1 GET /v1/stats/homepage (getHomepageStats; added; compatible)
- Before: GET /v1/stats/homepage was not available in the versioned API.
- After: Homepage counters. Returns the counters shown on the egdata homepage: tracked offers, price changes observed in the last 72 hours, active discounts, and current giveaways. Counts are resolved for the Epic pricing region that contains
country. Cookies are never used;countrydefaults to US. Response media: application/json. Requires an API key with stats:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/items/{id} (getItem; added; compatible)
- Before: GET /v1/items/{id} was not available in the versioned API.
- After: Get an item. Returns one catalog item. The catalog
idis preferred; legacy_idvalues also resolve. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/items/{id}/assets (getItemAssets; added; compatible)
- Before: GET /v1/items/{id}/assets was not available in the versioned API.
- After: List item assets. Returns the asset records whose
itemIdmatches the item identifier. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/items/{id}/builds (getItemBuilds; added; compatible)
- Before: GET /v1/items/{id}/builds was not available in the versioned API.
- After: List item builds. Returns build summaries for every app referenced by the item's release info, including manifest status, platform, and size metadata. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/items/{id}/changelog (getItemChangelog; added; compatible)
- Before: GET /v1/items/{id}/changelog was not available in the versioned API.
- After: List item changelog entries. Returns changelog entries for the item, its assets, and its builds as
{ metadata, timestamp, document }rows ordered bytimestampdescending with_iddescending as a stable tie-breaker. Passmeta.pagination.nextCursorascursorto fetch the next page. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/items/{id}/offer (getItemOffer; added; compatible)
- Before: GET /v1/items/{id}/offer was not available in the versioned API.
- After: Get the current base-game offer for an item. Selects the current base-game offer for the item, preferring offers that are not pre-purchases, and returns it with the current regional price. Offers are filtered by country eligibility before selection. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 POST /v1/items/bulk (getItemsBulk; added; compatible)
- Before: POST /v1/items/bulk was not available in the versioned API.
- After: Get multiple items. Resolves up to 100 item identifiers in one request. Found items are returned in input order, and identifiers that do not resolve are listed in
meta.missing. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/items-sitemap.xml (getItemsSitemap; added; compatible)
- Before: GET /v1/items-sitemap.xml was not available in the versioned API.
- After: Item sitemap. Native XML sitemap for website item pages. Response media: application/xml. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/items/sitemap.xml (getItemsSitemapAlias; added; compatible)
- Before: GET /v1/items/sitemap.xml was not available in the versioned API.
- After: Item sitemap (legacy alias). Response media: application/xml. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/latest-games (getLatestGames; added; compatible)
- Before: GET /v1/latest-games was not available in the versioned API.
- After: Latest catalog additions. Returns the 25 most recently created base games, DLC, and add-ons with current regional prices. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/stats/creations/monthly (getMonthlyCreationStats; added; compatible)
- Before: GET /v1/stats/creations/monthly was not available in the versioned API.
- After: Monthly base-game creations. Returns the number of base-game offers created per month since December 2018. Pre-purchases and code-redemption-only offers are excluded. Results are cached for one day. Response media: application/json. Requires an API key with stats:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/stats/releases/monthly (getMonthlyReleaseStats; added; compatible)
- Before: GET /v1/stats/releases/monthly was not available in the versioned API.
- After: Monthly base-game releases. Returns the number of base-game releases per month since the Epic Games Store launch in December 2018. Pre-purchases and code-redemption-only offers are excluded. Results are cached for one day. Response media: application/json. Requires an API key with stats:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id} (getOffer; added; compatible)
- Before: GET /v1/offers/{id} was not available in the versioned API.
- After: Get an offer. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/achievements (getOfferAchievements; added; compatible)
- Before: GET /v1/offers/{id}/achievements was not available in the versioned API.
- After: Offer achievements. Returns the achievement sets tracked for the offer's sandbox. Base games and add-ons use different achievement sets. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/age-rating (getOfferAgeRating; added; compatible)
- Before: GET /v1/offers/{id}/age-rating was not available in the versioned API.
- After: Offer age rating. Returns every age rating stored for the offer's sandbox, or only the rating system that applies to the requested country when
single=true. Missing rating data returns 404. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers/{id}/assets (getOfferAssets; added; compatible)
- Before: GET /v1/offers/{id}/assets was not available in the versioned API.
- After: Offer assets. Returns the assets belonging to the items of this offer, including sub-items and items linked by offer ID. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/builds (getOfferBuilds; added; compatible)
- Before: GET /v1/offers/{id}/builds was not available in the versioned API.
- After: Offer builds. Returns up to 50 recently updated builds for the offer's assets, including manifest and size summaries. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/bundle (getOfferBundle; added; compatible)
- Before: GET /v1/offers/{id}/bundle was not available in the versioned API.
- After: Bundle contents. Returns the offers inside a bundle with their regional prices, the bundle price, and the summed contents price. Non-bundle offers return 404. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offer-by-slug/{slug} (getOfferBySlug; added; compatible)
- Before: GET /v1/offer-by-slug/{slug} was not available in the versioned API.
- After: Resolve an offer slug. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/changelog/stats (getOfferChangelogStats; added; compatible)
- Before: GET /v1/offers/{id}/changelog/stats was not available in the versioned API.
- After: Offer change log statistics. Aggregates the offer's change log between two ISO 8601 timestamps into daily counts, weekday counts, change-type counts, and changed-field counts. Invalid or missing timestamps return 400. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/collection (getOfferCollection; added; compatible)
- Before: GET /v1/offers/{id}/collection was not available in the versioned API.
- After: Offers in the offer's collection. Returns the offers referenced by this offer's collection attributes with current regional prices. Offers that are not part of a collection return 404. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/collections/{collection} (getOfferCollectionEntry; added; compatible)
- Before: GET /v1/offers/{id}/collections/{collection} was not available in the versioned API.
- After: Offer position in a collection. Returns the offer's chart entry in one collection, including the collection name. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/events/{id} (getOfferEvent; added; compatible)
- Before: GET /v1/offers/events/{id} was not available in the versioned API.
- After: Get offers in an event. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/features (getOfferFeatures; added; compatible)
- Before: GET /v1/offers/{id}/features was not available in the versioned API.
- After: Offer gameplay features. Derives launcher, gameplay features, and Epic feature flags from the offer's tags and the custom attributes of its items. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/franchises (getOfferFranchises; added; compatible)
- Before: GET /v1/offers/{id}/franchises was not available in the versioned API.
- After: Franchises containing an offer. Returns the franchises whose offer list includes this offer. Franchises whose offers all belong to the same namespace are omitted. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/genres (getOfferGenres; added; compatible)
- Before: GET /v1/offers/{id}/genres was not available in the versioned API.
- After: Offer genres. Returns the active storefront genre tags attached to the offer. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/giveaways (getOfferGiveaways; added; compatible)
- Before: GET /v1/offers/{id}/giveaways was not available in the versioned API.
- After: Offer giveaways. Returns every giveaway promotion recorded for this offer, most recent first. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/has-prepurchase (getOfferHasPrepurchase; added; compatible)
- Before: GET /v1/offers/{id}/has-prepurchase was not available in the versioned API.
- After: Offer has a prepurchase edition. Reports whether another base game in the same namespace is available for prepurchase. Always returns an object with
hasPrepurchase, plus the prepurchaseofferwhen one exists. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers/{id}/has-regular (getOfferHasRegular; added; compatible)
- Before: GET /v1/offers/{id}/has-regular was not available in the versioned API.
- After: Offer has a regular edition. For a prepurchase base game, reports whether a regular (non-prepurchase) base game exists in the same namespace. Always returns an object with
isPrepurchase, plus the regularofferwhen one exists. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers/{id}/hltb (getOfferHltb; added; compatible)
- Before: GET /v1/offers/{id}/hltb was not available in the versioned API.
- After: Offer HowLongToBeat data. Returns HowLongToBeat estimates for the offer. Offers without a matched HowLongToBeat entry return 404. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/igdb (getOfferIgdb; added; compatible)
- Before: GET /v1/offers/{id}/igdb was not available in the versioned API.
- After: Offer IGDB data. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/items (getOfferItems; added; compatible)
- Before: GET /v1/offers/{id}/items was not available in the versioned API.
- After: Offer items. Returns the items referenced by the offer, its sub-items, and any item that links back to the offer. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/mappings (getOfferMappings; added; compatible)
- Before: GET /v1/offers/{id}/mappings was not available in the versioned API.
- After: Offer store mappings. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/media (getOfferMedia; added; compatible)
- Before: GET /v1/offers/{id}/media was not available in the versioned API.
- After: Offer media. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/og (getOfferOg; added; compatible)
- Before: GET /v1/offers/{id}/og was not available in the versioned API.
- After: Offer share image (PNG). Native 1200×630 PNG share image. The response is not JSON-wrapped. Response media: image/png, image/webp. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/og.webp (getOfferOgWebp; added; compatible)
- Before: GET /v1/offers/{id}/og.webp was not available in the versioned API.
- After: Offer share image (WebP). Response media: image/png, image/webp. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/overview (getOfferOverview; added; compatible)
- Before: GET /v1/offers/{id}/overview was not available in the versioned API.
- After: Offer overview. Combines the localized offer, current price, media, IGDB data, features, age rating, giveaways, poll, genres, and technologies in a single response. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/polls (getOfferPolls; added; compatible)
- Before: GET /v1/offers/{id}/polls was not available in the versioned API.
- After: Offer rating poll. Returns the rating poll for the offer's sandbox as
{ poll }. When no poll exists,pollis null instead of an empty body. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers/{id}/price (getOfferPrice; added; compatible)
- Before: GET /v1/offers/{id}/price was not available in the versioned API.
- After: Current offer price. Returns the latest regional price for the offer. Offers that are not priced in the requested country return 404. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/price/fairness (getOfferPriceFairness; added; compatible)
- Before: GET /v1/offers/{id}/price/fairness was not available in the versioned API.
- After: Offer price fairness score. Returns the regional pricing fairness score computed for the offer in the requested country. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/price-stats (getOfferPriceStats; added; compatible)
- Before: GET /v1/offers/{id}/price-stats was not available in the versioned API.
- After: Offer price statistics. Returns the current price, the lowest discounted price ever recorded, and the most recent discounted price for the requested region. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/ratings (getOfferRatings; added; compatible)
- Before: GET /v1/offers/{id}/ratings was not available in the versioned API.
- After: Offer player ratings. Returns the Epic player-rating document for the offer's product. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/regional-price (getOfferRegionalPrice; added; compatible)
- Before: GET /v1/offers/{id}/regional-price was not available in the versioned API.
- After: Regional price comparison. Returns the current price, historical minimum and maximum, and USD equivalents. With
countrythe response is a single object; without it the response is a map keyed by pricing region. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers/{id}/requirements (getOfferRequirements; added; compatible)
- Before: GET /v1/offers/{id}/requirements was not available in the versioned API.
- After: Offer system requirements. Returns the normalized Windows and macOS minimum and recommended requirements, following a validated DLC parent when applicable. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/reviews-summary (getOfferReviewsSummary; added; compatible)
- Before: GET /v1/offers/{id}/reviews-summary was not available in the versioned API.
- After: Offer review summary. Aggregates the offer's public reviews into an average score and recommendation percentages. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/suggestions (getOfferSuggestions; added; compatible)
- Before: GET /v1/offers/{id}/suggestions was not available in the versioned API.
- After: Suggested offers. Returns up to 25 offers sharing genres with this offer, excluding the same namespace, with current regional prices. Bounded and not paginated. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/technologies (getOfferTechnologies; added; compatible)
- Before: GET /v1/offers/{id}/technologies was not available in the versioned API.
- After: Offer technologies. Returns the deduplicated technologies reported by the latest build of each asset belonging to the offer. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/tops (getOfferTops; added; compatible)
- Before: GET /v1/offers/{id}/tops was not available in the versioned API.
- After: Offer chart positions. Returns a map of collection ID to the offer's current position in that chart. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 POST /v1/items/bulk/offers (getOffersForItemsBulk; added; compatible)
- Before: POST /v1/items/bulk/offers was not available in the versioned API.
- After: Get the best current offer for multiple items. Resolves up to 100 item identifiers and returns one offer per item, combining direct item links with
offersubitemsmappings and ranking base games ahead of other offer types and released offers ahead of pre-purchases. Country-ineligible offers are skipped. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/profiles/{id} (getProfile; added; compatible)
- Before: GET /v1/profiles/{id} was not available in the versioned API.
- After: Get a player profile. Returns the public Epic profile, the linked Discord account metadata egdata stores, the profile creation date, the review count, and a per-sandbox achievement summary. Private self-profile and mutation endpoints are not part of v1. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements/{sandboxId} (getProfileAchievements; added; compatible)
- Before: GET /v1/profiles/{id}/achievements/{sandboxId} was not available in the versioned API.
- After: Get profile achievements for one sandbox. Returns the stored player achievement records for one sandbox together with the achievement-set metadata referenced by those records. Empty arrays are returned when the profile has no recorded achievements for the sandbox. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/information (getProfileInformation; added; compatible)
- Before: GET /v1/profiles/{id}/information was not available in the versioned API.
- After: Get profile details and statistics. Returns the public Epic profile together with aggregate achievement statistics (games played, unlocked achievements, awards, total XP, reviews), the donation details stored for the account, and whether a Discord account is linked. This resource is not paginated. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/random-game (getProfileRandomGame; added; compatible)
- Before: GET /v1/profiles/{id}/random-game was not available in the versioned API.
- After: Get a random owned game. Returns the full offer for a game the profile has achievement data for. When
sandboxis supplied, that game is returned instead of a random one. This resource is bounded and not paginated. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements/{sandboxId} (getProfileRareAchievements; added; compatible)
- Before: GET /v1/profiles/{id}/rare-achievements/{sandboxId} was not available in the versioned API.
- After: Get rarest profile achievements for one sandbox. Returns up to three of the rarest unlocked achievements for one sandbox, ordered by
completedPercentascending. This collection is bounded and not paginated. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/profiles/sitemap.xml (getProfilesSitemap; added; compatible)
- Before: GET /v1/profiles/sitemap.xml was not available in the versioned API.
- After: Public profile sitemap. Response media: application/xml. Requires an API key with profiles:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/promotions/{id}/cover (getPromotionCover; added; compatible)
- Before: GET /v1/promotions/{id}/cover was not available in the versioned API.
- After: Promotion cover offer. Returns the localized base-game offer from the first namespace referenced by the promotion. This is the offer metadata the legacy endpoint returned; it is not a rendered image. OG image routes remain outside v1. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/promotions-sitemap.xml (getPromotionsSitemap; added; compatible)
- Before: GET /v1/promotions-sitemap.xml was not available in the versioned API.
- After: Promotion sitemap. Response media: application/xml. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/region (getRegion; added; compatible)
- Before: GET /v1/region was not available in the versioned API.
- After: Resolve a country's pricing region. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/related (getRelatedOffers; added; compatible)
- Before: GET /v1/offers/{id}/related was not available in the versioned API.
- After: Related offers. Returns up to 25 offers from the same namespace with current regional prices. Bounded and not paginated. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/robots.txt (getRobots; added; compatible)
- Before: GET /v1/robots.txt was not available in the versioned API.
- After: Crawler policy. Native text/plain robots policy for API consumers. Sitemap and share-image paths remain crawlable; catalog data remains disallowed. Response media: text/plain. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId} (getSandbox; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId} was not available in the versioned API.
- After: Get a sandbox. Returns the stored sandbox record, falling back to the corresponding namespace record when no sandbox document exists. Sandboxes from the list operation are always retrievable. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/base-game (getSandboxBaseGame; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/base-game was not available in the versioned API.
- After: Get the base game for a sandbox. Returns the released base-game offer for the sandbox with its current regional price and localized text. When no released base game exists it falls back to a pre-purchase base game, then to an executable item, which is returned with
isItem: true. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/changelog (getSandboxChangelog; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/changelog was not available in the versioned API.
- After: List changelog entries for a sandbox. Returns changelog entries for the sandbox, its offers, its items, their assets, and their builds as
{ hits }, ordered bytimestampdescending with_iddescending as a stable tie-breaker. Each hit carries the resolved context document inmetadata.context. Totals are not calculated; usemeta.pagination.hasMore. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og (getSandboxOg; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/og was not available in the versioned API.
- After: Sandbox share image (PNG). Response media: image/png, image/webp. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/og.webp (getSandboxOgWebp; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/og.webp was not available in the versioned API.
- After: Sandbox share image (WebP). Response media: image/png, image/webp. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/stats (getSandboxStats; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/stats was not available in the versioned API.
- After: Get sandbox statistics. Returns offer, item, asset, build, and achievement counts for the sandbox. The asset count includes synthetic assets generated from release info without a stored artifact. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sandboxes/sitemap.xml (getSandboxesSitemap; added; compatible)
- Before: GET /v1/sandboxes/sitemap.xml was not available in the versioned API.
- After: Sandbox sitemap. Response media: application/xml. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/search/{id} (getSearchQuery; added; compatible)
- Before: GET /v1/search/{id} was not available in the versioned API.
- After: Get a cached search query. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/search/{id}/count (getSearchQueryCount; added; compatible)
- Before: GET /v1/search/{id}/count was not available in the versioned API.
- After: Count and facet a cached search query. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sellers/{id}/cover (getSellerCoverOffers; added; compatible)
- Before: GET /v1/sellers/{id}/cover was not available in the versioned API.
- After: Get cover offers for a seller. Returns up to five offers from the top-sellers collection for the seller, falling back to the seller's most recently modified offers. Each offer carries the current regional price and the response carries localization metadata. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sellers/{id}/stats (getSellerStats; added; compatible)
- Before: GET /v1/sellers/{id}/stats was not available in the versioned API.
- After: Get seller statistics. Returns offer, item, game, and free-game counts for the seller, together with the serialized seller record. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sitemap.xml (getSitemap; added; compatible)
- Before: GET /v1/sitemap.xml was not available in the versioned API.
- After: Offer sitemap. Native XML sitemap for website offer pages. Omit
pagefor the index. Sitemaps are crawler interfaces and retain page-based paging. Response media: application/xml. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/stats (getStats; added; compatible)
- Before: GET /v1/stats was not available in the versioned API.
- After: Catalog totals. Returns total document counts for offers, items, tags, assets, price-engine rows, changelogs, sandboxes, and products, plus the number of offers and items created in the current year. Counts are cached for one hour. Response media: application/json. Requires an API key with stats:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/open-api.json (getV1OpenApi; added; compatible)
- Before: GET /v1/open-api.json was not available in the versioned API.
- After: Version 1 OpenAPI document. Machine-readable OpenAPI 3.0 contract for the versioned public API. The legacy contract remains at /open-api.json. Response media: application/json. Public metadata operation; no API key required.
- Client action: None
- v1 GET /v1/stats/creations/yearly (getYearlyCreationStats; added; compatible)
- Before: GET /v1/stats/creations/yearly was not available in the versioned API.
- After: Yearly base-game creations. Returns the number of base-game offers created per year since December 2018. Pre-purchases and code-redemption-only offers are excluded. Results are cached for one day. Response media: application/json. Requires an API key with stats:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/stats/releases/yearly (getYearlyReleaseStats; added; compatible)
- Before: GET /v1/stats/releases/yearly was not available in the versioned API.
- After: Yearly base-game releases. Returns the number of base-game releases per year since the Epic Games Store launch in December 2018. Pre-purchases and code-redemption-only offers are excluded. Results are cached for one day. Response media: application/json. Requires an API key with stats:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 POST /v1/catalog/hydrate (hydrateCatalog; added; compatible)
- Before: POST /v1/catalog/hydrate was not available in the versioned API.
- After: Hydrate a bounded catalog graph. Read-only bulk cache-warming protocol. Returns one NDJSON line per requested root in input order. Unknown records are omitted unless they changed. Responses are never shared-cached. Response media: application/x-ndjson. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/active-sales (listActiveSales; added; compatible)
- Before: GET /v1/active-sales was not available in the versioned API.
- After: Active promotional events. Returns promotional tag groups whose regional prices are currently discounted, with up to three representative offers each. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/builds/{id}/files (listBuildFiles; added; compatible)
- Before: GET /v1/builds/{id}/files was not available in the versioned API.
- After: List files in a build snapshot. Returns file snapshot records ordered by
depth,fileName, orfileSizewith afileNametie-breaker, filtered by literal path search and extension. Items without the sort value use the natural BSON null order for the requested direction. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/builds/{id}/items (listBuildItems; added; compatible)
- Before: GET /v1/builds/{id}/items was not available in the versioned API.
- After: List catalog items associated with a build. Returns catalog items whose release info references the build app name, ordered by catalog
idascending. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/builds (listBuilds; added; compatible)
- Before: GET /v1/builds was not available in the versioned API.
- After: List observed builds. Returns observed builds ordered by the requested timestamp field with
_idas a tie-breaker in the same direction and missing timestamps last. Each entry is a build summary with the matching executable catalog item when one is known. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers/{id}/in-bundle (listBundlesContainingOffer; added; compatible)
- Before: GET /v1/offers/{id}/in-bundle was not available in the versioned API.
- After: Bundles containing an offer. Returns up to one entry per bundle that contains this offer, with the bundle offer and its regional price. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/changelist (listChangelist; added; compatible)
- Before: GET /v1/changelist was not available in the versioned API.
- After: Recent catalog changes with context. Compatibility alias for /v1/changelog. Returns the same keyset-paginated change feed. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/changelog (listChangelog; added; compatible)
- Before: GET /v1/changelog was not available in the versioned API.
- After: Recent catalog changes. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/countries (listCountries; added; compatible)
- Before: GET /v1/countries was not available in the versioned API.
- After: List pricing countries. Returns the ISO 3166-1 alpha-2 countries supported by the pricing API. This is a bounded reference list and is not paginated. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/featured-discounts (listFeaturedDiscounts; added; compatible)
- Before: GET /v1/offers/featured-discounts was not available in the versioned API.
- After: Featured discounted offers. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/free-games/sellers (listFreeGameSellers; added; compatible)
- Before: GET /v1/free-games/sellers was not available in the versioned API.
- After: Free game sellers. Returns every seller that has appeared in the giveaway catalog, with the number of distinct giveaways attributed to it, ordered by that count descending. The aggregate is global and does not depend on a pricing country. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/free-games (listFreeGames; added; compatible)
- Before: GET /v1/free-games was not available in the versioned API.
- After: Current free games. Returns current and announced giveaways from the desktop free-games catalog and the mobile freebies feed. Offer documents are expanded and localized, and every entry carries
giveawaymetadata (including the full desktop giveaway history), the current regional price, and the items unlocked by the offer. Cookies are never used. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/free-games/history (listFreeGamesHistory; added; compatible)
- Before: GET /v1/free-games/history was not available in the versioned API.
- After: Free game history. Cursor-paginated giveaway history ordered by
endDatedescending and theniddescending. Each entry contains the giveaway record, the expanded localized offer, and the current regional price. Cursors are bound to the filter set, ordering, country, locale, and page size, and expire after 24 hours. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/items (listItems; added; compatible)
- Before: GET /v1/items was not available in the versioned API.
- After: List catalog items. Returns catalog items ordered by
lastModifiedDatedescending withidascending as a stable tie-breaker; items without a modification date sort last. Passmeta.pagination.nextCursorascursorto fetch the next page. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/items-from-offer/{id} (listItemsFromOffer; added; compatible)
- Before: GET /v1/items-from-offer/{id} was not available in the versioned API.
- After: List items linked to an offer. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/latest-achievements (listLatestAchievements; added; compatible)
- Before: GET /v1/offers/latest-achievements was not available in the versioned API.
- After: Offers with newly tracked achievements. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/latest-released (listLatestReleased; added; compatible)
- Before: GET /v1/offers/latest-released was not available in the versioned API.
- After: Recently released offers. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/free-games/mobile (listMobileFreeGames; added; compatible)
- Before: GET /v1/free-games/mobile was not available in the versioned API.
- After: Current mobile free games. Returns the mobile freebies that are active now, expanded with the localized offer, the normalized giveaway record, and the current regional price. Entries without a matching offer document are omitted. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/changelog (listOfferChangelog; added; compatible)
- Before: GET /v1/offers/{id}/changelog was not available in the versioned API.
- After: Offer change log. Keyset-paginated change history for the offer, its items, and its assets, newest first. Each entry includes the changed document. Cursors expire after 24 hours and are bound to the filter set. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/events (listOfferEvents; added; compatible)
- Before: GET /v1/offers/events was not available in the versioned API.
- After: List active offer events. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/genres (listOfferGenres; added; compatible)
- Before: GET /v1/offers/genres was not available in the versioned API.
- After: List storefront genres. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/{id}/price-history (listOfferPriceHistory; added; compatible)
- Before: GET /v1/offers/{id}/price-history was not available in the versioned API.
- After: Offer price history. Keyset-paginated historical prices for one region, newest first, ordered by
dateand_iddescending. When neithercountrynorregionis given, the response is an object keyed by pricing region instead (bounded by the region list and not paginated). Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers/{id}/reviews (listOfferReviews; added; compatible)
- Before: GET /v1/offers/{id}/reviews was not available in the versioned API.
- After: Offer reviews. Keyset-paginated public reviews for the offer, newest first. Reviews are not personalized: no user identity is read from the request, and cursors are bound to the
verifiedfilter. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/offers (listOffers; added; compatible)
- Before: GET /v1/offers was not available in the versioned API.
- After: List offers. Live keyset-paginated offer list ordered by last modification time. Catalog changes can move records during traversal; cursors are bound to the filter set and expire after 24 hours. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/profiles/{id}/achievements (listProfileAchievements; added; compatible)
- Before: GET /v1/profiles/{id}/achievements was not available in the versioned API.
- After: List unlocked profile achievements. Lists the profile's unlocked achievements, joined with the achievement-set metadata and the owning base-game or DLC offer. Ordered by unlock date descending, with
sandboxIdandachievementNameas unique tie-breakers.meta.paginationcarrieslimit,hasMore, andnextCursor. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/profiles/{id}/games (listProfileGames; added; compatible)
- Before: GET /v1/profiles/{id}/games was not available in the versioned API.
- After: List profile games. Returns one achievement-completion summary per sandbox the profile has played, ordered by the selected
sortwithsandboxIdas the unique tie-breaker. Useplatinum=trueto keep only games with a platinum award.meta.paginationcarrieslimit,hasMore, andnextCursor; the legacypageparameter is replaced by the cursor. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/profiles/leaderboard (listProfileLeaderboard; added; compatible)
- Before: GET /v1/profiles/leaderboard was not available in the versioned API.
- After: Profile XP leaderboard. Ranks public Epic player profiles by the achievement XP stored for every sandbox they have played. Ties share the same
rank; entries are ordered byrankascending and thenaccountIdascending.datais the leaderboard array andmeta.paginationcarrieslimit,hasMore, andnextCursor. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/profiles/{id}/rare-achievements (listProfileRareAchievements; added; compatible)
- Before: GET /v1/profiles/{id}/rare-achievements was not available in the versioned API.
- After: List rarest unlocked profile achievements. Returns the 25 rarest unlocked achievements across all of the profile's games, ordered by
completedPercentascending. Each entry includes the matching base-game offer when one is available. This collection is bounded and not paginated. Response media: application/json. Requires an API key with profiles:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/promotions/{id} (listPromotionOffers; added; compatible)
- Before: GET /v1/promotions/{id} was not available in the versioned API.
- After: Offers in a promotion. Cursor-paginated offers carrying the promotion's event tag. Results are ordered by
sortByandsortDirwith the offer ID ascending as a unique tie-breaker, defaulting tolastModifiedDatedescending.pricesorting uses the current price engine row for the selected region.qfilters titles case-insensitively. Cursors are bound to the promotion, query, ordering, country, locale, and page size. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/promotions (listPromotions; added; compatible)
- Before: GET /v1/promotions was not available in the versioned API.
- After: Active promotions. Returns a bounded list of active event tags ordered by their number of referenced offers. The legacy endpoint returned every active event; v1 caps the list with
limitand never uses cookies. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/regions (listRegions; added; compatible)
- Before: GET /v1/regions was not available in the versioned API.
- After: List Epic pricing regions. Returns every Epic pricing region, its currency, description, and member countries. Bounded reference data, not paginated. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sales (listSales; added; compatible)
- Before: GET /v1/sales was not available in the versioned API.
- After: Currently discounted offers. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/achievements (listSandboxAchievements; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/achievements was not available in the versioned API.
- After: List achievement sets for a sandbox. Returns every achievement set stored for the sandbox. The bounded reference response is not paginated. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/assets (listSandboxAssets; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/assets was not available in the versioned API.
- After: List assets in a sandbox. Returns stored asset records merged with synthetic assets generated from item release info that has no stored artifact, ordered by
updatedAtdescending withartifactIdand thenplatformascending. Synthetic assets report zero sizes, the source item title, and a deterministic_idso cursors stay stable. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/builds (listSandboxBuilds; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/builds was not available in the versioned API.
- After: List builds for a sandbox. Returns build summaries for every build app referenced by the sandbox's items, ordered by
updatedAtdescending with_iddescending as a stable tie-breaker. Useplatformto restrict the items whose release info is considered. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/items (listSandboxItems; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/items was not available in the versioned API.
- After: List items in a sandbox. Returns catalog items whose namespace matches the sandbox, ordered by
lastModifiedDatedescending withidascending as a stable tie-breaker; items without a modification date sort last. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/sandboxes/{sandboxId}/offers (listSandboxOffers; added; compatible)
- Before: GET /v1/sandboxes/{sandboxId}/offers was not available in the versioned API.
- After: List offers in a sandbox. Returns offers whose namespace matches the sandbox, ordered by
lastModifiedDatedescending withidascending as a stable tie-breaker. Each offer is localized for the requested locale and carries the current price for the country's Epic pricing region when one is stored. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/sandboxes (listSandboxes; added; compatible)
- Before: GET /v1/sandboxes was not available in the versioned API.
- After: List sandboxes. Returns the known Epic namespaces (sandboxes) ordered by namespace identifier (
_id) ascending. Passmeta.pagination.nextCursorascursorto fetch the next page. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/search/developers (listSearchDevelopers; added; compatible)
- Before: GET /v1/search/developers was not available in the versioned API.
- After: List developers with offer counts. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/search/offer-types (listSearchOfferTypes; added; compatible)
- Before: GET /v1/search/offer-types was not available in the versioned API.
- After: List offer types with counts. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/search/publishers (listSearchPublishers; added; compatible)
- Before: GET /v1/search/publishers was not available in the versioned API.
- After: List publishers with offer counts. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/search/tags (listSearchTags; added; compatible)
- Before: GET /v1/search/tags was not available in the versioned API.
- After: List active search tags. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/sellers/{id} (listSellerOffers; added; compatible)
- Before: GET /v1/sellers/{id} was not available in the versioned API.
- After: List offers for a seller. Returns a cursor-paginated list of the seller's offers with the current regional price attached, ordered by
lastModifiedDatedescending withidascending as a stable tie-breaker. UseofferTypeto restrict the offer type andignoredSandboxesto exclude namespaces. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/sellers (listSellers; added; compatible)
- Before: GET /v1/sellers was not available in the versioned API.
- After: List sellers. Returns the bounded reference list of sellers referenced by at least one offer, sorted by display name. The list is not paginated;
meta.truncatedreports whether the safety cap was reached. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/tags (listTags; added; compatible)
- Before: GET /v1/tags was not available in the versioned API.
- After: List catalog tags. Bounded reference data. Use the optional group filter for a single tag group. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/top-sellers (listTopSellers; added; compatible)
- Before: GET /v1/offers/top-sellers was not available in the versioned API.
- After: Top selling offers. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/top-wishlisted (listTopWishlisted; added; compatible)
- Before: GET /v1/offers/top-wishlisted was not available in the versioned API.
- After: Top wishlisted offers. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/offers/upcoming (listUpcomingOffers; added; compatible)
- Before: GET /v1/offers/upcoming was not available in the versioned API.
- After: List upcoming offers. Response media: application/json. Requires an API key with offers:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/multisearch/items (multisearchItems; added; compatible)
- Before: GET /v1/multisearch/items was not available in the versioned API.
- After: Cross-catalog item search. Response media: application/json. Requires an API key with items:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/multisearch/offers (multisearchOffers; added; compatible)
- Before: GET /v1/multisearch/offers was not available in the versioned API.
- After: Cross-catalog offer search. OpenSearch offer search with legacy multisearch filters. Cursor pagination uses search_after. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/multisearch/sellers (multisearchSellers; added; compatible)
- Before: GET /v1/multisearch/sellers was not available in the versioned API.
- After: Cross-catalog seller search. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 POST /v1/search/natural-language (naturalLanguageSearch; added; compatible)
- Before: POST /v1/search/natural-language was not available in the versioned API.
- After: Natural-language offer search. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 POST /v1/builds/resolve-launcher-records (resolveLauncherRecords; added; compatible)
- Before: POST /v1/builds/resolve-launcher-records was not available in the versioned API.
- After: Resolve parsed Windows manifests to launcher metadata. Resolves bounded, path-free metadata from parsed Windows manifests. Results preserve request order and echo each
requestIdwith its per-candidate status. Ambiguous catalog, asset, and parent relationships are reported asambiguousinstead of guessing. Response media: application/json. Requires an API key with builds:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/search/changelog (searchChangelog; added; compatible)
- Before: GET /v1/search/changelog was not available in the versioned API.
- After: Search catalog changes. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- Client action: None
- v1 GET /v1/free-games/search (searchFreeGames; added; compatible)
- Before: GET /v1/free-games/search was not available in the versioned API.
- After: Search free games. Searches the
egdata.offersOpenSearch index for offers with giveaway entries, using the legacy title, offer type, tag, and category filters. Pagination usessearch_afterinstead of offsets, so cursors stay stable while the index changes. Results default tolastModifiedDatedescending withid.keywordascending as a unique tie-breaker.meta.result.totalis an OpenSearch estimate and may be a lower bound when the index reports agterelation. Response media: application/json. Requires an API key with catalog:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 GET /v1/search (searchOffers; added; compatible)
- Before: GET /v1/search was not available in the versioned API.
- After: Search offers. OpenSearch-backed offer search. Pagination uses
search_after; cursors are bound to the normalized filters, ordering, country, locale, and page size.meta.result.totalis deliberately omitted for live cursor traversal. Response media: application/json. Requires an API key with search:read permission; the gateway enforces per-key quotas. - Client action: None
- v1 POST /v1/search (searchOffersRedirect; added; compatible)
- Before: POST /v1/search was not available in the versioned API.
- After: Normalize search filters to a cacheable GET request. Validates a JSON filter document and returns a bodyless 303 redirect to the equivalent GET URL. No search is executed and no result body is returned. Requires an API key with search:read permission; the gateway enforces per-key quotas.
- 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.
Undated historical notes are excluded from alerts.