RWHOIS Bridge: Create separate key for Bounces API #1842
Merged
Conversation
This file contains 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
karlerikounapuu
force-pushed
the
separate-api-key-for-bounces
branch
from
75a59e8 to
1b6c451
Compare
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.
RWHOIS Contact requests API key is now named as
rwhois_internal_api_shared_keyThis key must match rest-whois side
registry_api_keykey.registryrwhois_internal_api_shared_key==rwhoisregistry_api_keyRWHOIS Bounce API key is now named as
rwhois_bounces_api_shared_keyThis key must match rest-whois side
bounces_api_shared_keykey.registryrwhois_bounces_api_shared_key==rwhoisbounces_api_shared_key