Upcoming API Change: Compression Will Be Required by July 1, 2025
Effective Date: July 1, 2025
Action Required: Start using the Accept-Encoding header for API requests
To improve API efficiency and performance, all Market Data (MD) API endpoints will soon require compression. Currently, compression is optional, but beginning July 1, 2025, all requests to MD endpoints must include an Accept-Encoding header with one of the following values:
gzipdeflatebr(Brotli)
Why This Change?
Enforcing compression provides several key benefits:
- Reduced bandwidth usage – Save on data transfer costs
- Faster response times – Improve API performance
- Better scalability – Ensure smoother operations as your API usage grows
Timeline & Next Steps
- Now – February 17, 2025: API responses now include a warning (
X-Warning: Compression will be required by July 1, 2025). Customers are encouraged to start using compression. - March 1, 2025: Reminder emails will be sent to customers who have not yet adopted compression
- June 1, 2025: Final notice will be sent to impacted customers
- July 1, 2025: API requests without compression will be rejected with an error:
HTTP 400: Compression required. Please use gzip, deflate, or br
What You Need to Do
If you are not already using compression, update your API requests to include the Accept-Encoding header with one of the values listed above. Need help? Check out our updated API Documentation with implementation guides and examples.
For any questions or concerns, please contact our support team at: support@amberdata.io. Let’s work together to ensure a smooth transition!