Developer

API references

Search documentation... ⌘K

API references

Open merchant dashboard

Merchant API

- Available API versions
- Supported payment methods
- Find key
- List keys
- Revoke key
- Update key
- Get balance
- Find bank account
- Link bank account
- Set primary contact bank account
- Unlink bank account
- Update bank account
- List monthly billing archives
- List plans
- List statements
- Retrieve current plan
- Retrieve monthly billing archive
- Select plan
- Confirm branding upload
- Generate branding upload url
- Remove branding document
- Retrieve branding
- Retrieve branding font
- Update branding
- Find card
- Forget card
- Save card
- Set default card
- Retrieve checkout
- Start checkout
- Add contact
- Filter contacts
- List contacts
- Remove contact
- Retrieve contact
- Update contact
- Find export
- List exports
- Request contact export
- Request payment by contact export
- Request payment export
- Request payout by contact export
- Request payout export
- Disable installation
- Enable installation
- Find installation
- List installations
- Reconfigure installation
- Remove installation
- Add to metadata set
- List metadata
- Remove from metadata set
- Remove in metadata
- Retrieve metadata
- Sync metadata
- List email subscribers
- Retrieve email subscriber
- Retrieve notification topics
- Subscribe to topics
- Unsubscribe from all topics
- Add payment link
- Clone payment link
- Disable payment link
- Enable payment link
- Filter payment links
- Find payment link
- List payment link payments
- List payment links
- Remove payment link
- Abort payment on terminal
- Capture payment
- Filter payments
- Find payment
- Initiate payment flow
- 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
- Filter payouts
- Find payout
- List payout activities
- List payouts
- List payouts by contact
- Send payout
- Send payout to contact
- Set primary bank account
- Turn off auto payout
- Turn on auto payout
- Find refund
- List refunds by payment
- Assign role
- List permissions
- List roles
- Add terminal
- Disable terminal
- Enable terminal
- Filter terminals
- Find terminal
- List terminals
- Remove terminal
- Reset terminal
- Update terminal
- Find topup
- List topups
- List user invitations
- List users
- Disconnect webhook
- Find webhook
- List webhooks
- Pause webhook
- Reconnect webhook
- Resume webhook

All our references

Retrieve metadata for a given key, optionally at a specific nested path.

Endpoint signature

This endpoint requires an API key. Read our authentication guide for more information.

POST https://api.reservepay.com/merchants/retrieve-metadata HTTP/1.1

Content-Type: application/json

Accept: application/json

Authorization: Bearer <token>

{

key: string,

path: string?,

data_only: boolean?,

}

Returns: object

New to Reservepay? Read our guide on how to call endpoints to get started.

Request arguments

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.

Response attributes

Attribute	Description
`key` string	The unique key for the metadata.
`metadata` object	The stored JSON metadata.
`bytesize` number	The size of the metadata in bytes.
`version` number	The current version number (lock_version).
`updated_at` number	The Unix timestamp (seconds since epoch) when the metadata was last updated.
`created_at` number	The Unix timestamp (seconds since epoch) when the metadata was created.
`expires_at` number	The Unix timestamp (seconds since epoch) when the metadata will expire. May be null.

Errors common to all endpoints


              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.

CODE SAMPLES

curl

Learn how to run these code samples in your terminal by reading our guide.