FINAL REMINDER: Starting Monday, Feb 9, 2026 - Requests Without Shared Secret Will Be Rejected

[openapi-support[bot]]

This is the final reminder about the upcoming shared secret enforcement for Etsy OpenAPI requests.

Starting Monday, February 9, 2026, requests without a shared secret will be rejected. We ask those who have not, to please take time to make this change.

No additional grace period will be provided.

Required action (must be completed before Feb 9, 2026)

Update your request headers to use the following format:
x-api-key: keystring:secret

This replaces the previous format:
x-api-key: keystring

Your shared secret is available on the Your Apps page:
https://www.etsy.com/developers/your-apps

Updated documentation can be found here:
https://developer.etsy.com/documentation/essentials/requests

Starting February 9, 2026, requests missing a shared secret will be rejected, which may result in service disruption if your integration has not been updated.

Thank you for taking the time to make this update and helping us keep the Etsy OpenAPI secure. For any questions, please reach out to [email protected].

[ViliusZur]

You need a better communication system and a way to subscribe to these breaking change announcements. GitHub is not my primary git repository so it's difficult to follow your announcements. It's the second time my users are encountering issues or simply cannot use my app because I missed your announcement and then I have to rush a solution.

In the Subscribing to release notes announcement you mention to configure your email to filter for "Breaking", but this announcement about a final reminder does not contain a work "Breaking". It is really frustrating following your announcements.

[lelinhtinh]

You can use an RSS Feed Reader extension to follow this source: https://github.com/etsy/open-api/discussions/categories/announcements.atom

[mikebronka]

Hello, my dev app stopped working (banned by etsy due to inactivity) and new one is pending for like a month now. Someone Can respond to emails? Wrote at [email protected] and [email protected] ...