The API uses the following error codes:
General errors
| HTTP Status Code | Description |
|---|---|
| 400 | Bad Request -- Your request is malformed, invalid, or you are missing parameters |
| 401 | Unauthorized -- Please make sure authentication was done properly |
| 403 | Forbidden -- This API request requires additional access rights. |
| 404 | Not Found -- The specified entity could not be found. |
| 500 | The server encountered an unexpected condition which prevented it from fulfilling the request. |
Sygna Bridge - Custom errors:
Please be noted that Sygna Gate/ Hub have dedicated Custom errors. (Working in Progress, will release soon.)
| Error code | Error message | Description |
|---|---|---|
| 010203 | The originator_vasp_code ${vasp_code} does not exist in sygna-bridge | |
| 010204 | The beneficiary_vasp_code ${vasp_code} does not exist in sygna-bridge | |
| 010205 | Verify originator's data signature failed | |
| 010207 | Verify beneficiary's signature failed | |
| 010116 | API key id is not valid | |
| 010211 | You do not have permission to access this data transfer. Please ensure that the transfer_id is correct and that you are either the Originator VASP or the Beneficiary VASP. | |
| 010213 | Verify originator's callback signature failed | |
| 010214 | Verify originator's signature failed | |
| 010215 | The transfer already has permission status | |
| 010216 | The transfer already has txid | |
| 010217 | The transfer already has permission status | |
| 010218 | The permission_status does not exist in the transfer | |
| 010219 | The permission_status is not ACCEPTED | |
| 010222 | There is no vasp_receive_url or callback_url | |
| 010319 | The transfer does not exist | |
| 010322 | There is no VASP with the query condition (VASP not exist) | |
| 010362 | The currency_id ${currency_id} does not exist in sygna-bridge | |
| 010363 | The currency_id ${currency_id} was deactivated | |
| 010365 | The beneficiary ${vasp_code} does not register the endpoint to provide validation of address | |
| 010367 | The response from the beneficiary VASP ${vasp_code} is not expected (the Beneficiary wallet address validation does not pass or the Beneficiary VASP server does not respond). Please check with the beneficiary VASP. | |
| 010368 | The address are not belong to the beneficiary ${vasp_code} | |
| 010380 | The transfer already confirmed txid | |
| 010385 | Target service is not supported yet | |
| 010386 | Target service is deactivated | |
| 010387 | Target service is not activated | |
| 010388 | Target service is expired | |
| 010389 | Target service would be activated at ${started} | |
| 010398 | The counterparty VASP (${vasp_code}) service status is ${vasp_status}. | |
| 010400 | This data transfer is expired based on the duration set at the beginning or set by the counterparty VASP. | |
| 010401 | The value of expire_date should not be set to a past time. | Bridge API </permission-request> or </permission> with “expire_date”: 0 or a value that represents a past time. |