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
- 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
- List contacts
- Remove contact
- Retrieve contact
- Update contact
- Disable installation
- Enable installation
- Find installation
- List installations
- Reconfigure installation
- Remove installation
- List 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
- 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
- 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
- List user invitations
- List users
- Disconnect webhook
- Find webhook
- List webhooks
- Pause webhook
- Reconnect webhook
- Resume webhook

All our references

List all users

Retrieve a list of all users who are members of your merchant account. This endpoint returns an array of user objects containing details about each user.

Common use cases for this endpoint:

Auditing user access to your merchant account
Identifying users who can perform actions on behalf of the merchant
Managing user permissions and roles within the merchant account

Endpoint signature

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

POST https://api.reservepay.com/merchants/list-users HTTP/1.1

Content-Type: application/json

Accept: application/json

Authorization: Bearer <token>

{}

Returns: array

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

Response attributes

Attribute	Description
`user_id` string	The ID of the user. This can be used as an argument in other endpoints. E.g.: `remove-user`
`name` string	The name of the user, as they set it in their profile. This name is informational only and has not been verified.
`email` string	The email address of the user.
`email_confirmed` boolean	Whether the user's email address has been confirmed. If it is `false`, they may not own this address, and their access will be limited.
`mfa_enabled` boolean	Whether the user has enabled multi-factor authentication (MFA) for their account. This is set by the user in their profile settings.
`role_id` string	The ID of the user's role within the merchant account. This can be used as an argument in other endpoints.
`preferred_language` string	The user's preferred language for communication. This is set by the user in their profile settings.

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.