SOLVED – Bubble API Collections + OneSignal REST API (Engine v33)
After spending many hours debugging Bubble’s new API Collections with OneSignal REST API, I wanted to share the solution because the error messages were extremely misleading.
Our initial Bubble error was:
“this header name is not correct Authorization”
After fixing that, both Bubble and even the official OneSignal API Tester returned:
403 Forbidden
“Please include an Authorization header with a valid API key.”
This made us believe the problem was Authentication, API Keys or Bubble itself.
It wasn’t.
The final working configuration was:
• Bubble Collection Authentication:
- Authentication: Private key in header
- Header name: Authorization
- Private key: Key YOUR_APP_API_KEY
• Do NOT add another Authorization header inside the individual API call.
Keep only:
Content-Type: application/json
The biggest trap we found was a simple copy/paste mistake.
One incorrect App ID inside the JSON body caused OneSignal to return what looked like an Authentication error, even though the Authorization header and the API Key were actually correct.
Before spending hours debugging Authentication, verify ALL copied values very carefully:
- App ID
- App API Key (NOT the Key ID)
- External ID
We also strongly recommend testing the exact request with the official OneSignal API Tester before debugging Bubble. It helped us determine whether the problem was Bubble or the request itself.
In our case the root cause was NOT Bubble.
It was an incorrect App ID caused by a copy/paste mistake, while the returned error message suggested an Authorization problem.
Hopefully this saves someone else several hours of debugging.