POST
/
v2
/
errors
Report Outgoing Error
curl --request POST \
  --url https://api.procuros.io/v2/errors \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "errorReason": "<string>",
  "errorType": "DATA",
  "errorContext": {},
  "transactionIdentifier": "IV-0001",
  "transactionType": "ORDER"
}'
{
  "message": "OK.",
  "errorUrl": "https://portal.procuros.io/.../errors/{{procurosErrorId}}"
}

Authorizations

​
Authorization
string
header
required

The API Token of your ERP Connection.

Body

application/json
​
errorReason
string
required

The reason for the error.

​
errorType
enum<string>
required

The type of the error. DATA indicates that the error is caused by invalid or insufficient data and can be resolved by a user. INTERNAL indicates a system-level error that cannot be fixed by a user.

Available options:
DATA,
INTERNAL
​
errorContext
object

Additional context/meta data for the error.

​
transactionIdentifier
string

Provide if error can be assigned to a specific outgoing transaction. Depending on the transactionType: Order number, Invoice number, etc.

Example:

"IV-0001"

​
transactionType
enum<string>

Provide if error can be assigned to a specific outgoing transaction. Type of transaction.

Available options:
ORDER,
ORDER_RESPONSE,
SHIPPING_NOTICE,
INVOICE,
CREDIT_NOTE,
DISPATCH_INSTRUCTION,
DISPATCH_INSTRUCTION_RESPONSE,
RECEIVAL_NOTICE,
REMITTANCE_ADVICE,
PRODUCT_CATALOG,
INVENTORY_REPORT,
SALES_REPORT

Response

Created

​
message
string
required

Status message

​
errorUrl
string

URL to the Procuros portal where users can view the error and mark it as resolved.