403 "API key not found or not active" despite Personal Access status

[brettasesma-cyber]

Confirmation

• I confirm this post does NOT contain sensitive data for my account.

Question / discussion

Hi all,

Hoping someone can help troubleshoot — my app shows as approved on the dashboard, but every API request is being rejected.

App name: modernhobbyco-market-research-tool
Keystring: u32syevyj7yedu7xd3kfzmx
Status shown on Your Apps page: Personal Access

The issue:

Every request returns a 403 with:

"API key not found or not active, or incorrect shared secret for API key."

I've tested this directly via curl (not through any third-party tool) against two endpoints:

• GET https://openapi.etsy.com/v3/application/listings/{listing_id}
• GET https://openapi.etsy.com/v3/application/openapi-ping

I've also tried both header formats to rule out a format issue on my end

Both endpoints and both formats return the identical 403. I've double-checked the keystring and shared secret directly against what's shown on my Your Apps dashboard, character by character — they match exactly.

I also emailed developer@etsy.com about this 5 days ago with no response yet.

Has anyone else run into a key that shows "Personal Access" on the dashboard but still gets rejected as not found/not active? Wondering if this is a known backend delay after approval, or if there's something else I should check.

Thanks in advance for any pointers.

[openapi-support[bot]]

We've verified your App is configured correctly. You appear to have a typo in your keystring. Please check the developer portal for the correct value.