Update an app
Replaces the app's configuration. Every field is overwritten with what you send, so a redirect_urls you leave out becomes an empty list — send the whole object, not a patch.
Changing webhook_url takes effect on the next event; there is no verification handshake.
It replaces every field with what the body carries. name, keycloak_client_idenfifier, allowed_domains, redirect_urls and webhook_url are all written as sent, so omitting one erases it — sending an update without webhook_url turns the webhook off. Read the app first and send it back whole.
keycloak_client_idenfifier is the one field that is NOT overwritten. Sending a different one answers ERROR_CODE_547 and nothing is written: it is the client_id your integration authenticates with, and renaming it would lock out everything already asking for tokens with the old one. Send it unchanged, or leave it out. If you need a different identifier, create another app.
An app token works here. This is the one part of /apps that does: an app can read and update its own record, but it cannot list, create, delete, or read the secret. No plan is required: apps are on all four plans, the free one included.
Request
- Base URL: https://api.planvortex.com/v1.0.0
- URL: https://api.planvortex.com/v1.0.0/clients/{id_client}/apps/{id_app}
- Auth: one of:
- HTTP bearer
- OAuth 2 (client credentials, token URL https://api.planvortex.com/v1.0.0/oauth/token)
Path parameters
Client identifier
App identifier
Request body
Example request
{
"keycloak_client_idenfifier": "shop-integration"
}Response
The updated app
Changes
No recorded changes to this operation across all 1 revision of this API.