Get record
GET/v2/key-value-stores/:storeId/records/:recordKey
Gets a value stored in the key-value store under a specific key.
The response body has the same Content-Encoding header as it was set in
Put record.
If the request does not define the Accept-Encoding HTTP header with the
right encoding, the record will be decompressed.
Most HTTP clients support decompression by default. After using the HTTP
client with decompression support, the Accept-Encoding header is set by
the client and body is decompressed automatically.
Please note that for security reasons, Apify API can perform small modifications
to HTML documents before they are served via this endpoint. To fetch the raw HTML
content without any modifications, use the attachment query parameter.
Request
Path Parameters
Key-value store ID or username~store-name.
WkzbQMuFYuamGv3YFKey of the record.
Example:someKeyQuery Parameters
Signature used to access the record.
Example:2wTI46Bg8qWQrV7tavlPIIf true or 1, the response will be served with Content-Disposition: attachment header,
causing web browsers to offer downloading HTML records instead of displaying them.
trueStatus 200
Response Headers
{
"foo": "bar"
}
Schema
Status 302
Response Headers
- Location
Status 400
Bad request - invalid input parameters or request body.
{
"error": {
"type": "invalid-input",
"message": "Invalid input: The request body contains invalid data."
}
}
Schema
error object required
- type string requiredExample:
run-failed - message string requiredExample:
Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)
- type string requiredExample: