---
title: "unknown_error"
description: "Error type: unknown_error"
canonical: "https://studio.inttegro.dev/e/t-unknown_error"
format: inttegro-machine-docs/v1
language: "cURL"
reader_profile: optional
reader_manifest: "https://studio.inttegro.dev/machine/curl/readers/index.json"
reader_identification: "Optional: declare your client only if known and your current-session capabilities; use reader_manifest for supplemental recommendations."
preamble_estimated_tokens: 324
model_token_report: "https://studio.inttegro.dev/machine/token-report.json"
preamble_questions: 5
preamble_source: "general"
recommended_mcp_tools: []
estimated_tokens: 901
token_estimate_method: "utf8_bytes_divided_by_4"
---

## Machine preamble

**Summary:** Error type: unknown_error This cURL representation preserves HTTP paths and JSON wire names.

### Five questions

#### Q1. When should the reader use unknown_error?

Use this page as orientation before selecting the narrower guide or reference that owns the implementation contract.

#### Q2. What is authoritative on this page?

Use this page for orientation; follow its canonical SDK, guide, API, or MCP links for exact contracts.

#### Q3. What page-specific constraint matters most?

Use the page to choose a canonical next source instead of treating summary material as a complete implementation contract.

#### Q4. Can Inttegro MCP materially help with this task?

No catalog ability is sufficiently specific to recommend for this page. Use the documentation directly; consult the MCP catalog only if the task later requires governed live account context or a supported operation.

#### Q5. How should the reader verify the answer and continue?

Select the narrowest linked guide or reference, apply its stated completion condition, and verify against authoritative resource state when the task changes data. Continue with [contact_customer_support](https://studio.inttegro.dev/machine/curl/e/f-contact_customer_support.md) when those concerns enter scope.

## Document content

# unknown\_error

Error type indicating an unexpected failure that doesn't fit established error categories.

## What this means

An unexpected error occurred that the Inttegro API couldn't categorize into known error types like `invalid_request_parameter` or `transient_error`. These errors represent edge cases, unhandled system states, or failures that require engineering investigation to properly classify. When you encounter an `unknown_error`, the system has logged comprehensive details for internal analysis, but the error doesn't map to any established failure pattern.

For example, if scheduling a payout fails due to an unforeseen database constraint violation or an unexpected third-party service response, it may surface as an unknown error. The presence of this error type typically indicates the fix code will be `contact_customer_support`, as resolution requires manual investigation by the engineering team to understand the root cause and potentially reclassify the error for future occurrences.

## Example error response

```json
{
  "error": {
    "type": "unknown_error",
    "cause": "unknown",
    "code": "1923",
    "message": "unexpected system error",
    "detail": "An unexpected error occurred while processing your request. Our team has been notified and is investigating.",
    "fix_code": "contact_customer_support",
    "url": "https://studio.inttegro.com/e/1923"
  }
}
```

## Related errors

- [contact\_customer\_support](https://studio.inttegro.dev/machine/curl/e/f-contact_customer_support.md) - Fix code often associated with unknown errors