How to expose full error message of a step via the integrator.io api

Integrator.io
1

Good day Everyone,

I was wondering if there is a way to get around this?

We have an Amazon to NetSuite IA tile for shipments, and I want to export the full error message from one of the steps.

image
image518×276 13.2 KB

image
image964×583 77.4 KB

The issue is that when I use the integrator.io API to export the error, the message is trimmed.

The image displays an API error message with a 400 code, highlighting issues related to missing required fields such as 'prepOwner' and 'labelOwner', with some text redacted for privacy. (Captioned by AI)
The image displays an API error message with a 400 code, highlighting issues related to missing required fields such as 'prepOwner' and 'labelOwner', with some text redacted for privacy. (Captioned by AI)843×511 108 KB

The reason I’m trying to export the full error message is that I plan to build a custom flow that will retry the step based on the error message received.

Thank you!

2

Call:

GET /v1/flows/{{_flowId}}/{{_processorId}}/requests/{{reqAndResKey}}

To get something like this:

{
    "request": {
        "headers": {
            "Accept": "application/json",
            "Content-Type": "application/json",
            "User-Agent": "axios/1.8.2",
            "Content-Length": "17",
            "Accept-Encoding": "gzip, compress, deflate, br",
            "authorization": "Bearer ********"
        },
        "url": "https://api.integrator.io/v1/mirror",
        "method": "POST",
        "body": "{\"failed\":\"test\"}"
    },
    "response": {
        "statusCode": 200,
        "headers": {
            "date": "Tue, 22 Jul 2025 16:21:29 GMT",
            "content-type": "application/json; charset=utf-8",
            "content-length": "17",
            "connection": "keep-alive",
            "x-dns-prefetch-control": "off",
            "x-frame-options": "SAMEORIGIN",
            "x-download-options": "noopen",
            "x-content-type-options": "nosniff",
            "x-xss-protection": "1; mode=block",
            "referrer-policy": "same-origin",
            "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
            "etag": "W/\"11-rO+h0j8p46CFcts9OnDETFb9Hn0\"",
            "vary": "Accept-Encoding",
            "authorization": "Bearer ********"
        },
        "receivedAt": 1753201289115,
        "body": "{\"failed\":\"test\"}"
    },
    "key": "5504917110885-81db6afa1d49455fb5d752c8955331da-200-POST-import",
    "id": "81db6afa1d49455fb5d752c8955331da",
    "time": 1753201289115
}
2 Likes
3

This should be documented soon by @kathyanaqueeman. It was going through the approvals last week.

1 Like
4

Thank you! @tylerlamparter. Tested it and was able to get the whole error message.

Awesome stuff