What the API integration does
Create named server side OAuth clients with scoped permissions.
Automate invitation, widget and review workflows from your systems.
Work from the public OpenAPI description and server side examples.
What moves between the two systems
- What starts it
- Your own code calls it.
- What WebVouch receives
- Whatever the request carries: invitations, widget configuration, review queries.
- What goes back to API
- The response the call asked for. Pair it with webhooks when you also need telling about new reviews.
How to set it up
- 1
Create a client
Add a confidential OAuth client in the business panel, name it after the system that will use it, and keep the credentials on your server.
- 2
Grant only the scopes you need
Scope each client to the work it does. A service that only sends invitations has no reason to read moderation data.
- 3
Call the API
Follow the public OpenAPI description. Pair it with webhooks when you also need to react to reviews as they arrive.
When API is the right choice
Pick the API when no plugin can see the sale, for example a phone order, a second sales channel, or a booking a person confirms. For a plain shop checkout the store integration is less work and needs no maintenance.
API integration questions
Through confidential OAuth clients created in the business panel. They are server side credentials, so they never belong in a browser or a mobile app.
Integration details last updated
