Dispatch

All Sections

API Error Codes

Content

    Error response format

    An error will bla bla....

    HTTP/1.1 400 Bad Request
    Content-Type: application/json
    ...
    {
    errors: [
    {
    "code": "InvalidParameter",
    "message": "The value 'tomorrow' for property 'deliveryTime' is not a valid ISO 8601 DateTime"
    },
    {
    "code": "MissingParameter",
    "message": "The required property 'targetId' was not present in the request body"
    }
    ]
    }

    Common Errors

    HTTP Status CodeError CodeDescriptionRetryable?
    500-Internal Server ErrorYes*
    400InvalidParameterA supplied parameter did not match an expected value or formatNo
    400MissingParameterA required parameter was not present in the requestNo
    401MissingAccessTokenNo access token was provided in the requestNo
    401InvalidAccessTokenThe access token could not be verifiedNo
    401ExpiredAccessTokenThe provided access token has expiredNo
    401MissingPermissionThe provided access token is missing a required permission in its scopeNo

    * Depending on the nature of the underlying error the problem may or may not be resolved by retrying. We advice only performing a small amount of retries in case the error is more permanent.

    Specific Errors

    HTTP Status CodeError CodeDescriptionRetryable?
    400E-DI-3001Target not foundNo
    400E-DI-3002Unknown target typeNo
    400E-DI-3003Cannot enable an already enabled targetNo
    400E-DI-3004Cannot disable an already disabled targetNo
    400E-DI-3010Unknown errorMaybe*
    400E-DI-3011The endpoint domain has not been verifiedNo
    400E-DI-3020Unknown errorMaybe*
    400E-DI-3021Insufficient role permissionsNo
    400E-DI-3022The target queue does not existNo
    400E-DI-3023Unable to assume the configured roleNo
    400E-DI-3030Unknown errorMaybe*
    400E-DI-3031Insufficient role permissionsNo
    400E-DI-3032The target topic does not existNo
    400E-DI-3033Unable to assume the configured roleNo
    400E-DI-3034Unable to parse AWS region from Topic ARNNo
    400E-DI-4001Domain not foundNo
    400E-DI-4002Domain name already in useNo
    400E-DI-4003Domain has already been verifiedNo
    400E-DI-4004Domain has been marked as deletedNo
    400E-DI-4005The domain is still in use by targetsNo
    400E-DI-4011Unable to resolve domainNo
    400E-DI-4012Unable to find matching TXT record on domainNo
    400E-DI-4020Unknown errorMaybe*
    400E-DI-4021The file content did not match the expected valueNo
    400E-DI-4022Unexpected HTTP statusNo
    400E-DI-4023Unable to connect to the hostNo
    400E-DI-5001Message not foundNo
    400E-DI-5002Payload was too largeNo
    400E-DI-5003Cannot cancel message in the current stateNo
    400E-DI-5004Cannot reschedule already delivered messagesNo
    400E-DI-5005Monthly free tier limit reachedNo

    * Depending on the nature of the underlying error the problem may or may not be resolved by retrying. We advice only performing a small amount of retries in case the error is more permanent.