Freeze a specific election
PUT/elections/:electionId/freeze
Freezes the requested election if it is in a valid state. A valid state is:
- The election must have at least one ballot paper.
- Each ballot paper must have at least one section.
- Each ballot paper section must have at least one candidate linked to it.
- All candidates linked to the election must be linked to at least one ballot paper section. Note that freezing an election is an action that should be done with caution and after a careful review of the election configuration. After an election is frozen, the configuration of the election can not be changed anymore. You can not change the number of allowed voters.
After the election is frozen, the key pair for the election will be generated. The access tokens for your voters can be generated after that. Note that depending on the load of the system it will take some time until the generated keys are available. You will get a response quickly without the keys, but the keys will be generated in the background. If the keys are available, you will get them in your normal GET request for the election.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 406
- 415
- 429
- default
OK. The request was successfully executed. The election is now frozen.
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.