Transasction signing with Pushed Authorization Request (PAR)
For PAR reference, see general section about PAR
Signtext API integration and PAR
As an alternative to the Signtext API integration utilized to generate signtext_id parameters for the OIDC flows, the PAR endpoint available at Signaturgruppen Broker supports setting up the signtext payload directly through a single PAR integration.
The PAR endpoint support the following additional two parameters, which must both be specified to be applied to the flow
PAR parameter | Description |
---|---|
signtext_base64 | Signtext payload in Base64 encoding |
signtext_type | One of text, html or pdf |
When both parameters have been specified, the resulting OIDC flow is equivalent to setting up the signtext_id parameter directly using the Signtext API. This allows for integrations utilizing the transasction signing flow without the need for two API calls and an active integration to the Signtext API.