Registrant API: domain registrant confirmations #1742
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
changed the title
karlerikounapuu
force-pushed
the
registrant-confirmation-api
branch
from
af054a9 to
4eaa806
Compare
karlerikounapuu
force-pushed
the
registrant-confirmation-api
branch
from
e756cee to
64d35a8
Compare
karlerikounapuu
force-pushed
the
registrant-confirmation-api
branch
from
a763c26 to
54eb1e9
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.
Dependency of registrant_center#19
In
config/application.yml, add a new propertyregistrant_portal_verifications_base_url.Leave it as
''to use legacy registrant portal for confirmation mails. Populate it with root address (https://registrant.internet.ee for example) of new registrant_center to use new registrant_portal for confirmation mails.Get data about registrant change / domain delete
GET /api/v1/registrant/confirms/<domain>/change/<token>GET /api/v1/registrant/confirms/<domain>/delete/<token>Approve / Reject registrant change action
POST /api/v1/registrant/confirms/<domain>/change/<token>/confirmedPOST /api/v1/registrant/confirms/<domain>/change/<token>/rejectedApprove / Reject domain delete action
POST /api/v1/registrant/confirms/<domain>/delete/<token>/confirmedPOST /api/v1/registrant/confirms/<domain>/delete/<token>/rejected