Bridge/Permission

post

https://test-api.sygna.io/v2/bridge/transaction/permission

This request works as a response to Bridge's Permission Request. Whenever a beneficiary VASP finishes processing the request from Bridge, it must post a permission request back to Bridge server, containing the confirmation result.

The Beneficiary VASP signs the body parameters with its private key to construct the signature.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

transfer_id

string

required

length between 64 and 64

Unique Id generated by Bridge

permission_status

string

enum

required

length ≥ 1

Status of the transfer permission, currently available values: ACCEPTED, REJECTED.

Allowed:

expire_date

integer

≥ 0

Use a Unix timestamp with milliseconds for expire_date and avoid setting it to a past time. The Sygna Bridge protocol stops relaying transfer requests after the expiration date. Default “30 days of expire date” if “expire_date” is not specified.

reject_code

string

enum

length ≥ 1

Only required when the permission_status is REJECTED, reply with BVRC.

reject_message

string

Only required when the permission_status is REJECTED and reject_code is 'BVRC999', reply with BVRC.

forced_sending_when_VASP_is_not_healthy

boolean

check vasp status or not

signature

string

required

length between 128 and 128

Signature of the object that includes the constraint fields.

Response

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200