Get 2nd requested info
In order to get the requested (instead of the current) status of the production line of the 2nd tokens part, the identifier of the tokens object MUST be sent as the first HTTP request path parameter together with requested as the second HTTP request path parameter.
If the JSON response body contains the path data attributes status: requested together with other attribute–value pairs, the production of the 2nd tokens part is just requested. In this case, neither the tokens data nor the snapshot of the production line is linked in it or available for download at this point.
Request endpoint
GET SERVER:PORT/api/tokens/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/requested
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:57:40 GMT
Content-Type:application/vnd.api+json
Server:nginx/1.25.4
Request body
# intentionally blank
Response body
{
"meta": {
"seed": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
},
"links": {
"self": "/api/tokens",
"info": "/api/tokens/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
},
"data": {
"attributes": {
"digits": "100",
"status": "requested",
"analysis": "none",
"size": "1000",
"reachable": "10485",
"alphabet": "UPPER_VOWELS",
"available": "7888609052210118054117285652827862296732064351090230047702789306639625",
"timestamps": {
"requested": "2024-03-19T12:57:33.263Z"
}
},
"id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"type": "tokens",
"relationships": {
"payment": {
"data": {
"id": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"ident": "pi_XXXXXXXXXXXXXXXXXXXXXXXX",
"type": "transaction"
}
}
}
}
}
HTTPie example
$ http get SERVER:PORT/api/tokens/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/requested Accept:application/vnd.api+json Content-Type:application/vnd.api+json Session-Key:SSSSSSSS-SSSS-SSSS-SSSS-SSSSSSSSSSSS