List all SDK installations
Retrieve a list of all SDK installations in your merchant account. This endpoint returns an array of installation objects, each containing details about:
- Name and platform (web, iOS, Android or Terminal)
- Unique identifier (domain, bundle ID or package name)
- Enabled payment methods
- Current status (enabled or disabled)
See find-installation for the complete list of response attributes.
Common use cases for this endpoint:
- Auditing which installations are currently active
- Checking the configuration of multiple installations
- Finding installations that need to be updated or disabled
- Getting an overview of your integration across different platforms
| Attribute | Description |
|---|---|
installation_idstring
|
The ID of the installation. |
enabledboolean
|
Whether the installation is enabled and active. |
namestring
|
The name of the installation. |
platformstring
|
The platform type of the installation (e.g., 'WEB', 'IOS', 'ANDROID', 'TERMINAL'). |
identifierstring
|
The unique identifier for the installation on the platform. |
payment_methodsarray
|
List of payment methods supported by this installation. |
email_capturestring
|
Email capture configuration for this installation. 'disabled' means no email collection, 'optional' means email is collected if provided by customer, 'required' means email is mandatory for all customers. |
mobile_capturestring
|
Mobile phone capture configuration for this installation. 'disabled' means no mobile number collection, 'optional' means mobile number is collected if provided by customer, 'required' means mobile number is mandatory for all customers. |
created_atnumber
|
The timestamp of the key creation as a Unix timestamp. |
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/list-installations" \
-X POST
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-H "Authorization: Bearer $(RESERVEPAY_API_KEY)" \
-d '{}'
