Skip to main content
POST

Authorizations

Authorization
string
header
required

JWT bearer token obtained via the OAuth2 client-credentials grant from the platform Authentication API. The token's scopes gate the endpoints it may call, and its audience names the Guardian instance. This is the standard way to authenticate to Guardian.

Headers

x-destination-url
string<uri>
required

The target URL to which the request shall be forwarded. Guardian forwards calls only to whitelisted destination URLs (major payment providers are included by default). Contact support to whitelist a custom URL.

Example:

"https://api.psp.example.com/payments"

x-own-header-name
string

Name of a header to set on the forwarded request. Guardian strips the credential your call authenticates with (for example x-api-key) before forwarding; use this pair to send the destination's own credential instead. Only takes effect together with x-own-header-value.

Example:

"x-api-key"

x-own-header-value
string

Value for the header named by x-own-header-name, set on the forwarded request — typically your credential for the destination.

Example:

"sk_live_51Hxxxx"

Path Parameters

id
string<uuid>
required

The ID of the wallet token to forward.

Body

application/json

The payload to forward to the third-party provider.

Use placeholders to inject the wallet token's card data on the fly. Append | unwrap to emit a value as its native type instead of a string, e.g. {{ expiry_month | unwrap }}.

Response

Success response

The response from the third-party provider.