---
title: "Report Outgoing Error"
method: POST
path: "/v2/errors"
tags: ["Outgoing Transactions"]
---

# Report Outgoing Error

`POST /v2/errors`

## Request

- Base URL: `https://api.procuros.io`
- URL: `https://api.procuros.io/v2/errors`
- Auth: HTTP bearer

If you encounter an error while building an outgoing transaction payload, you can report it here. The error will enter the same exception handling process as an error reported while processing incoming transactions.

## Request body

- object
  - `errorReason` string, required: The reason for the error.
  - `errorType` 'DATA' | 'INTERNAL', 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.
  - `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.
  - `transactionType` 'ORDER' | 'ORDER_RESPONSE' | 'SHIPPING_NOTICE' | 'INVOICE' | 'CREDIT_NOTE' | 'DISPATCH_INSTRUCTION' | 'DISPATCH_INSTRUCTION_RESPONSE' | 'RECEIVAL_NOTICE' | 'REMITTANCE_ADVICE' | 'PRODUCT_CATALOG' | 'INVENTORY_REPORT' | 'SALES_REPORT': Type of transaction.

## Response `201`

Created

- object
  - `message` string, required: Status message
  - `errorUrl` string: URL to the Procuros portal where users can view the error and mark it as resolved.

## Other responses

- `422`: Validation Error
- `4XX`: Client Error
- `5XX`: Server Error

---

[API](https://skmtc.dev/procuros/apis/procuros-api.md) - [All operations](https://skmtc.dev/procuros/apis/procuros-api/llms.txt) - [OpenAPI document](https://skmtc.dev/procuros/apis/procuros-api/revisions/28a1d5326ce9?raw)