Unfreeze a specific election
PUT/elections/:electionId/unfreeze
Unfreezes the selected election. WARNING: This action cannot be undone and will delete important data.
When you unfreeze an election, you can edit its settings again. However, this will permanently delete:
- All voting tokens that were created for voter groups linked to this election
- The key pair for encrypting votes for this election
- All votes that were cast for this election (TODO)
- All votes in other elections that share the same voter groups (TODO)
Example: If VoterGroup1 is used in both Election1 and Election2:
- Unfreezing Election1 will delete ALL votes in Election2 as well
- Exception: If Election1 is public, only votes from VoterGroup1 will be deleted in Election2
- Votes from other voter groups in Election2 will remain safe
You cannot unfreeze an election while it is still creating its keys for encrypting votes.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 406
- 415
- 429
- default
OK. The request was successfully executed. The election was unfrozen.
Bad Request. The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). Note, the actual error message may be different from the example one.
Unauthorized. The request has not been applied because the user does not have valid authentication credentials for the target resource. Note, the actual error message may be different from the example one.
Forbidden. The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). The request should not be repeated. Note, the actual error message may be different from the example one.
Not Found. The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible. Note, the actual error message may be different from the example one.
Not Acceptable. The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
Unsupported Media Type. The request entity has a media type which the server or resource does not support. For example, the client uses the content type: text/plain, but the server requires application/json.
Too Many Requests. The user has sent too many requests in a given amount of time.
Internal Server Error. A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.