Delete all custom alphabets
If several custom alphabets have served their purpose, they SHOULD be deleted. This can be done using a single mass data operation instead of explicit individual operations. To do this, the request MUST be sent without any HTTP request path parameter.
The deleted custom alphabets are returned from the remote service as list in the JSON response body. Each data object of type: alphabet in the list has the same structure as if it had been requested by its identifier via HTTP request path parameter.
This operation can be used at any time during an existing session. All existing custom alphabets of the current session will be irretrievably destroyed, so the operation SHOULD be used responsibly.
Request endpoint
DELETE SERVER:PORT/api/alphabets
Response status
200
Request headers
Accept:application/vnd.api+json
Content-Type:application/vnd.api+json
Session-Key:SSSSSSSS-SSSS-SSSS-SSSS-SSSSSSSSSSSS
Response headers
Transfer-Encoding:chunked
Connection:keep-alive
Accept:application/vnd.api+json
Cache-Control:no-cache
Date:Tue, 19 Mar 2024 12:52:24 GMT
Content-Type:application/vnd.api+json
Server:nginx/1.25.4
Request body
# intentionally blank
Response body
{
"links": {
"self": "/api/alphabets"
},
"data": [
{
"attributes": {
"ascii": true,
"length": 4,
"bytes": 4,
"parity": 0,
"chars": "bat4"
},
"id": "BAT",
"type": "alphabet"
},
{
"attributes": {
"ascii": true,
"length": 3,
"bytes": 3,
"parity": 112,
"chars": "bas"
},
"id": "BAS",
"type": "alphabet"
},
{
"attributes": {
"ascii": true,
"length": 3,
"bytes": 3,
"parity": 113,
"chars": "bar"
},
"id": "BAR",
"type": "alphabet"
}
]
}
HTTPie example
$ http delete SERVER:PORT/api/alphabets Accept:application/vnd.api+json Content-Type:application/vnd.api+json Session-Key:SSSSSSSS-SSSS-SSSS-SSSS-SSSSSSSSSSSS