Errors
The following reference contains a list of error codes, their messages, and descriptions for errors that may be encountered when using the Layer1 API.
These errors are returned in the following format:
{
"code": "layer1:digital-asset:XXXX",
"status": "<the status of the request>",
"message": "<error message>"
}
Error Codes
Validation or Unknown Exception
| Code | Status | Description |
|---|---|---|
layer1:digital-asset:1000 | BAD_REQUEST | Error given for validation or unknown exceptions. |
Validation Errors
| Code | Status | Description |
|---|---|---|
layer1:digital-asset:4000 | BAD_REQUEST | Error given for invalid inputs. |
layer1:digital-asset:4001 | CONFLICT | Error given when a transfer request exists with different data. |
layer1:digital-asset:4002 | BAD_REQUEST | Error given for invalid outputs. |
layer1:digital-asset:4003 | BAD_REQUEST | Error given for an invalid request. |
layer1:digital-asset:4004 | CONFLICT | Error given when a master key already exists. |
layer1:digital-asset:4005 | CONFLICT | Error given when there is data inconsistency. |
layer1:digital-asset:4006 | PRECONDITION_FAILED | Error given when an asset pool is not empty. |
layer1:digital-asset:4007 | CONFLICT | The error appears when an asset pool is not empty. |
layer1:digital-asset:4008 | NOT_FOUND | The error appears when the requested item can't be found. |
Export Job Errors
| Code | Status | Description |
|---|---|---|
layer1:digital-asset:4100 | CONFLICT | Error given when an export job execution is already running. |
layer1:digital-asset:4101 | CONFLICT | Error given when an export job restart fails. |
layer1:digital-asset:4102 | BAD_REQUEST | Error given when an export job instance is already complete. |
layer1:digital-asset:4200 | CONFLICT | The error appears when a consolidation request with this reference already exists for the asset pool. |
layer1:digital-asset:4201 | BAD_REQUEST | The error appears when the blockchain address is not associated with the specified asset pool. |
layer1:digital-asset:4202 | BAD_REQUEST | The error appears when the specified address is a master address and cannot be used as a consolidation source. |
Failure reasons
In webhooks and responses from GET endpoints, you can see the failure.reason field for describing the reason for an unsuccessful operation. Layer1 supports the reason values, including but not limited to the following:
| Failure reason | Description |
|---|---|
APPROVAL_REJECTED | Transactions was rejected as part of your configured approval policies |
BLOCKCHAIN_TRANSACTION_BUILD_FAILED | Could not construct blockchain transaction ahead of signing |
BLOCKCHAIN_TRANSACTION_FAILED | Transaction failed on the blockchain |
DUST_AMOUNT | Transaction was categorised as a small dust amount |
INSUFFICIENT_FUNDS | Not enough funds on balance to process transaction (can also be gas fee balance) |
PROCESSING_FAILED | General processing error for a transaction |
SCREENING_REJECTED | Transaction was rejected as a result of compliance screening |