Reporting HTTP Errors - 40X, 50X, and Others

When encountering 40X or 50X errors, providing the right details upfront helps us diagnose and resolve the issue faster. Please include the following information when submitting a support request:

Required Information

1. Error Code

   • The specific HTTP status code you encountered (e.g., 404, 500).

2. Environment

   • Indicate whether the issue occurred on Testnet or Mainnet.

3. Endpoint

   • Specify the exact REST API endpoint(s) causing the issue (e.g., "/v3/ethereum/transaction").

4. Provide a cURL Request

   • Include a cURL request showing:
     • Headers
     • Payload
     • Full Response Body

5. Error Details

   • Attach the full error response received from the API. Example format:
   JSON

   {
       "statusCode": ###,
       "errorCode": "###",
       "message": "###.",
       "data": [
           "###error_verbose"
       ],
       "dashboardLog": "https://dashboard.tatum.io/logs?id=####" // Send this "id" code to support
   }
   

6. Reproduction Steps:

   • Provide a clear, step-by-step guide on how to reproduce the issue.

7. Timestamp:

   • Include the exact time when the issue occurred (e.g., 2025-01-12 15:00 GMT).

8. Description

   • Briefly explain the problem (e.g., "The endpoint fails intermittently.").

Why This Information Matters

Providing your error details, cURL request, and reproduction steps allows us to diagnose issues accurately and efficiently. Without these details, troubleshooting can be significantly delayed or even unfeasible.

• HTTP errors can originate from misconfigured requests, network issues, or API changes.
• Clear reproduction steps help us replicate the problem and identify potential fixes.
• The dashboard Error log ID (when available), provides insights into the request history, making investigation faster.