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

CodeStatusDescription
layer1:digital-asset:1000BAD_REQUESTThe error appears during validation or due to unknown exceptions.

Validation Errors

CodeStatusDescription
layer1:digital-asset:4000BAD_REQUESTThe error appears for invalid inputs.
layer1:digital-asset:4001CONFLICTThe error appears when a transfer request exists with different data.
layer1:digital-asset:4002BAD_REQUESTThe error appears for invalid outputs.
layer1:digital-asset:4003BAD_REQUESTThe error appears for an invalid request.
layer1:digital-asset:4004CONFLICTThe error appears when a master key already exists.
layer1:digital-asset:4005CONFLICTThe error appears when there is data inconsistency.
layer1:digital-asset:4006PRECONDITION_FAILEDThe error appears when an asset pool is not empty.
layer1:digital-asset:4007CONFLICTThe error appears when an asset pool is not empty.
layer1:digital-asset:4008NOT_FOUNDThe error appears when the requested item can't be found.

Export Job Errors

CodeStatusDescription
layer1:digital-asset:4100CONFLICTThe error appears when an export job execution is already running.
layer1:digital-asset:4101CONFLICTThe error appears when a restart of an export job fails.
layer1:digital-asset:4102BAD_REQUESTThe error appears when an export job instance is already complete.
layer1:digital-asset:4200CONFLICTThe error appears when a consolidation request with this reference already exists for the asset pool.
layer1:digital-asset:4201BAD_REQUESTThe error appears when the blockchain address is not associated with the specified asset pool.
layer1:digital-asset:4202BAD_REQUESTThe 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 reasonDescription
APPROVAL_REJECTEDThe transaction was rejected as part of your configured approval policies.
BLOCKCHAIN_TRANSACTION_BUILD_FAILEDCould not construct blockchain transaction ahead of signing
BLOCKCHAIN_TRANSACTION_FAILEDTransaction failed on the blockchain.
INSUFFICIENT_FUNDSNot enough funds on balance to process transaction (can also be gas fee balance)
PROCESSING_FAILEDGeneral processing error for a transaction
SCREENING_REJECTEDThe transaction was rejected as a result of compliance screening