Hi team,
We’re integrating the Conversions API for Superhuman and our server-side POSTs to https://bzr.openai.com/v1/events are returning 401 with:
"You have insufficient permissions for this operation. Missing scopes: ads.third_party_events.write. Check that you have the correct role in your organization, and if you're using a restricted API key, that it has the necessary scopes."
We’ve tried generating multiple keys from Ads Manager → Conversions → Manage conversion keys, but the UI doesn’t expose any scope selection:
-
No scope picker when creating a new key
-
No way to edit scopes on existing keys
-
Every key we generate hits the same 401
We also tried generic API Keys from Setting → General → API Keys, but we got the same result (and also no option to set scopes).
Could anyone know what’s happening? I know we’re on Beta here, so something could me missing?
Thanks!
Hey @allisson.superhuman 
Thanks for flagging this. We’re tracking this through your support case as well, so we’ll continue the detailed investigation there.
From what you shared, this looks specific to the Conversions API key/scope path rather than the browser pixel path. The team is reviewing the ads.third_party_events.write scope behavior and the expected way to provision or enable access for server-side event delivery.
We’ll follow up in the support thread once we have confirmed guidance or next steps.
Hey @allisson.superhuman, following up here as well for visibility.
We replied in your support case with one specific repro step that will help the team narrow this down: please create a fresh Development Conversion Key from Ads Manager > Conversions > Manage conversion keys, use it for one request against the dev pixel, then send us the exact UTC timestamp, any request/trace ID returned in the response headers, and the email address of the user who was signed in when the key was created.
Please don’t share the key itself.
We’ll keep the detailed investigation in the support case, but I wanted to make sure this didn’t get missed here.
Hi Siddhant,
Confirmed working! Generating a fresh Conversion Key via Ads Manager → Conversions → Manage conversion keys resolved the scope issue. The CAPI now accepts our requests 
Additionally, the full server-side integration (both signup and purchase events firing from our back-end’s Conversions API client) is now confirmed end-to-end.
Thank you so much for the support here 
Hey @allisson.superhuman
Thanks for confirming this is working now, and glad the fresh Conversion Key resolved the scope issue.
For anyone else who runs into this: use the key generated from Ads Manager > Conversions > Manage conversion keys for CAPI, rather than a generic platform/project API key.
Closing this thread now.
