Trading API returning Akamai 503 for any POST with X-EBAY-API-CALL-NAME header
Has anyone else been hitting this since around 2026-05-23 06:00 UTC? Our Trading API integration has been completely down for 30+ hours, and after extensive testing I can reproduce the issue is at the Akamai WAF layer, not in our code. Posting the full repro in case other devs are seeing the same.
REPRODUCTION
Request A (BROKEN — Akamai 503):
Method: POST
URL: https://api.ebay.com/ws/api.dll
Headers: Content-Type: text/xml;charset=utf-8
X-EBAY-API-CALL-NAME: GeteBayOfficialTime
Body: a valid GeteBayOfficialTimeRequest XML document
Result: HTTP 503, Akamai HTML page "Service Unavailable - Zero size object"
Request B (WORKS — HTTP 200 from eBay):
Same as Request A but WITHOUT the X-EBAY-API-CALL-NAME header
Result: HTTP 200, real eBay XML response — Ack=Failure, ShortMessage="Unsupported API call."
(eBay backend rejects it correctly because the routing header is missing)
A plain GET to the same URL also returns HTTP 200 with eBay XML "Unsupported verb", proving the endpoint and backend are healthy.
The only common factor that triggers the Akamai 503 is the presence of the X-EBAY-API-CALL-NAME request header. Since that header is REQUIRED for routing every Trading API call, the entire Trading API is unusable for us right now.
VERIFIED ACROSS
- 2 different Google Cloud egress IPs
- Home wifi (Spectrum)
- T-Mobile cellular
- With our real OAuth token, with a fake App ID, and with no auth header at all
- REST APIs at api.ebay.com/sell/* work normally from all the same IPs
The 503 fires BEFORE any auth check on eBay's side.
AKAMAI REFERENCES
15.cca5dc17.1779563418.ccb59daa
15.69a7cb17.1779607871.ac079ab0
Block onset: ~2026-05-23 06:00 UTC, ongoing 30+ hours.
No active Trading API incident currently listed at https://developer.ebay.com/support/api-status
My App ID: PeterLia-Revision-PRD-484c0e5fe-8b0e7d40
Has eBay support or any DSAs seen this? Any other developers affected? It looks like a WAF rule deployed around 2026-05-23 06:00 UTC that misfires on the X-EBAY-API-CALL-NAME header.
Thanks,
Peter
developer-support@ebay.com
Hi @supervtec ,
Thank you for your post!
We’ve reviewed your query, and to assist you more effectively, we need some additional information. Specifically, please provide the request and response details, as well as the rlogid associated with your request, so we can better understand the issue you are facing.
To ensure your case is handled securely and efficiently, we kindly ask that you submit a support ticket using the following link: eBay Support Tickets This is a complimentary service and will help us investigate the issue in detail.
Additionally, please avoid sharing sensitive information here in the forum, as it may contain confidential data that could pose security risks if posted publicly.
Best Regards,
eBay Developer Support
ardonis-2000
·4 months ago"GeteBayOfficialTime" was likely called to document the error. However, since the beginning of 2025 (API version 1399), "GeteBayOfficialTime" has been decommissioned
https://developer.ebay.com/devzone/xml/docs/ReleaseNotes.html
"... Added error message for 1399; GeteBayOfficialTime Call Decommissioned; ..."