-
- abort-payment-on-terminal
- capture-payment
- filter-payments
- find-payment
- initiate-payment-flow
- list-activity-logs
- list-payment-activities
- list-payments
- list-payments-by-contact
- list-payments-by-terminal
- refund-payment
- request-payment
- resume-payment-on-terminal
- retrieve-refund-performance
- retrieve-sales-performance
- reverse-payment
- start-payment-on-terminal
- void-payment
Retrieve metadata
Retrieve metadata for a given key, optionally at a specific nested path.
key
string
Required. The unique key for the metadata.
path
string
Optional. Optional dot-separated path to retrieve.
data_only
boolean
Optional. If true, only the metadata value will be returned.
| Attribute | Description |
|---|---|
keystring
|
Always present. The unique key for the metadata. |
metadataany
|
Nullable. The stored JSON metadata. |
bytesizenumber
|
Always present. The size of the metadata in bytes. |
versionnumber
|
Always present. The current version number (lock_version). |
updated_atnumber
|
Always present. The Unix timestamp (seconds since epoch) when the metadata was last updated. |
created_atnumber
|
Always present. The Unix timestamp (seconds since epoch) when the metadata was created. |
expires_atnumber
|
Nullable. The Unix timestamp (seconds since epoch) when the metadata will expire. May be null. |
UNHANDLED_ERROR
This error occurs when the server encounters an unexpected internal error that it cannot handle gracefully. This typically happens due to bugs, infrastructure issues, or edge cases that weren't anticipated during development.
INVALID_ARGUMENTS
This error occurs when the request contains invalid or missing parameters. Common cases include missing required fields, or values that don't match the expected format or type.
BAD_VERSION
This error occurs when making requests to an API version that does not exist. This commonly happens when using an outdated SDK or when the API version specified in the request URL is incorrect.
curl "https://api.reservepay.com/merchants/retrieve-metadata" \
-X POST
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer $(RESERVEPAY_API_KEY)" \
-d '{
"key": "myData",
"path": "tags.a"
}'
