The integration sends a request to this endpoint to create an installation. This is required, especially when API keys are used for authorisation.
JWT Bearer token authentication. Include the token in the Authorization header as: Bearer <token>
Installation request
Metadata associated with the installation. This can be used to store additional information about the installation, for example external references, but it is not used by any Pleo system.
{ "externalConfigurationId": "123456789" }| Value | Description |
|---|---|
| ACTIVATED | The installation is active and operational. |
| INACTIVE | The installation is inactive and not currently in use. |
| AUTHORIZED | The Pleo authorisation server has authorised the user, but the installation is not yet active or ready for use. |
| PENDING_INTEGRATION | The integration is synchronising or performing other background tasks. When an installation is in progress, the integration synchronises the user's Pleo account with the target application, so that tax codes, tags, and vendors are all similar in both Pleo and the third-party application. |
| ERROR | The installation has encountered an error and is not operational. An error code will be provided to explain the reason for the error. |
ACTIVATED, INACTIVE, AUTHORIZED, PENDING_INTEGRATION, ERROR Installation created.
The unique identifier of the application this installation is for.
"123e4567-e89b-12d3-a456-426614174000"
The date and time when the installation was created.
"2021-01-01T00:00:00Z"
The unique identifier of the installation.
"123e4567-e89b-12d3-a456-426614174000"
Additional information about the installation.
{ "key": "value" }The resource that the installation is for.
"urn:pleo:company:123e4567-e89b-12d3-a456-426614174000"
This can be one of InstallationStatus values
"ACTIVATED"
The date and time when the installation was last updated.
"2021-01-01T00:00:00Z"
Explains the error that inactivated the installation. This appear if the installation status is inactive.
"NOT_ENTITLED"