Switch Onesignal to use the new Organization keys #29229
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Onesignal killed the old user auth keys, they no longer work. Here's a conversation with their support... Me: where can I create a user authorization key for use with the API? Me: my key I was using is no longer working Them: Hi there, Thank you for reaching out! On the 14th of November 2024, we announced the new rich API key system described above and started deprecating legacy API keys. The legacy user auth keys will be deprecated on the 1st of March 2025, and legacy app REST API keys will be deprecated in Q1 2026. https://documentation.onesignal.com/docs/keys-and-ids#migrating-from-legacy-api-keys 1. This is the guide on generating the new rich auth key. https://documentation.onesignal.com/docs/keys-and-ids#api-keys Instead of using "Basic { REST API Key}", the new authentication key would be using this format "Key {Rich_Authentication_Key}". This will replace the REST API key. 2. For APIs using the user auth key, it will be replaced with the Organization API key: https://documentation.onesignal.com/docs/keys-and-ids#organization-api-key A sample request via the API can be found here along with other information: https://documentation.onesignal.com/reference/quick-start-api-guide#rest-api-key Let us know if you have any additional questions. Thanks.
AliSoftware
approved these changes
Mar 13, 2025
|
Thanks for the contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
bundle exec rspecfrom the root directory to see all new and existing tests passbundle exec rubocop -ato ensure the code style is validci/circlecibuilds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)Motivation and Context
Onesignal killed the old user auth keys, they no longer work and you can't create new ones. Here's a conversation with their support...
Me:
Them:
Description
Changed the auth header as per their instructions
Testing Steps