Errors

Proof APIs will respond with standard HTTP error codes should you make a bad request. 400 and 422 errors will have more specific messaging depending on the API and endpoint used.

HTTP Status Code	Summary
`200` - `SUCCESS`	Successful API request.
`400` - `BAD REQUEST`	Bad request or invalid parameters.
`401` - `NOT AUTHENTICATED`	Not authenticated.
`403` - `NOT AUTHORIZED`	No access to this specific feature.
`404` - `NOT FOUND`	The requested item does not exist.
`422` - `BAD REQUEST`	Violated business rule.
`500` - `SERVER ERROR`	Unknown error. Retry the call.

If you'd like more help deciphering errors and error codes from the Proof API, please contact Support.

Deleting Transactions

Deleting transactions via UI or API will also delete records and objects associated with the transaction.
For example, querying a transaction or attempting to fetch one or more of a transaction's documents after a successful deletion request will return a 404 response.

{
    "errors": [
        "Transaction Not Found"
    ]
}

Transaction deletion requests executed in our UI or via API will only succeed if the transaction is incomplete.
If there is an attempt to delete a transaction while the transaction is complete ( "detailed_status": "complete") the deletion request will fail and return a 422 response.

{
    "errors": [
        "Transaction has already been completed by at least 1 signer."
    ]
}