List CrackerBinarys
Changed onGET many request to retrieve multiple objects.
Request
- Base URLhttps://docs.hashtopolis.org
- AuthHTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
Pointer to paginate to retrieve the data after the object provided. Specify the base64 encoded JSON string in a uniquely identifiable manner (e.g. object IDs), i.e. by using one (primary) or two (primary and secondary) fields that allow for stable sorting.
Format: {"primary":{"someField": 123},"secondary":{"someOtherOptionalField": "Foo"}}
Example: {"primary":{"crackerBinaryId": 123}} -> eyJwcmltYXJ5Ijp7ImNyYWNrZXJCaW5hcnlJZCI6IDEyM319
Pointer to paginate to retrieve the data before the object provided. Specify the base64 encoded JSON string in a uniquely identifiable manner (e.g. object IDs), i.e. by using one (primary) or two (primary and secondary) fields that allow for stable sorting.
Format: {"primary":{"someField": 123},"secondary":{"someOtherOptionalField": "Foo"}}
Example: {"primary":{"crackerBinaryId": 123}} -> eyJwcmltYXJ5Ijp7ImNyYWNrZXJCaW5hcnlJZCI6IDEyM319
Amount of data to retrieve inside a single page
Filters results using a query. Every key is an attribute name optionally suffixed with a comparison operator, e.g. filter[crackerBinaryId__gt]=200.
Relationships to include in the response, comma seperated. Possible options: crackerBinaryType, accessGroup, tasks, hashtypes
Response
successful operation
Example response
{
"data": [
{
"id": 1,
"relationships": {
"accessGroup": {
"data": {
"id": 1
}
},
"crackerBinaryType": {
"data": {
"id": 1
}
},
"hashtypes": {
"data": [
{
"id": 1
}
]
},
"tasks": {
"data": [
{
"id": 1
}
]
}
}
}
],
"included": [
{
"id": 1
}
]
}Changes
- breaking
added the pattern
^[A-Za-z0-9+/]*={0,2}$to thequeryrequest parameterpage[after] - breaking
added the pattern
^[A-Za-z0-9+/]*={0,2}$to thequeryrequest parameterpage[before] - warning
for the
queryrequest parameterpage[size], the min was set to1.00 - info
for the
queryrequest parameterpage[after], the format was generalized frombyteto no format - info
for the
queryrequest parameterpage[before], the format was generalized frombyteto no format
- breaking
- breaking
the response property
///became nullable for the status - breaking
added
subschema #2subschema #4to the/response propertyoneOflist for the response status - info
added the enum value
accessGroupto the propertyitems/of thequeryrequest parameterinclude - info
added the enum value
hashtypesto the propertyitems/of thequeryrequest parameterinclude - info
added the required property
///to the response with the status - info
added the required property
///to the response with the status - info
added the required property
///to the response with the status - info
added the required property
///to the response with the status
- breaking