Module: 4/5
Lesson: 6/7
Exercises:
Module 4 | Lesson 5

Lesson 5: Parsing Responses — Getting the Data You Need from What You Get

Reading Error Responses

When an API returns an error, it sends: - An HTTP status code (400, 401, 404, 500, etc.) - A response body with details about the error

The response body matters. It tells you what went wrong.

Example error response from a payment API:

{
  "error": {
    "code": "insufficient_funds",
    "message": "The customer's card has insufficient funds for this transaction",
    "retry_after": 3600
  }
}

Without reading the response body, you only know "something went wrong." With the body, you know the specific reason and when to retry.

Make and n8n both show you error responses in the execution logs. Always check them when something fails.

🔒

This lesson is premium

Get full access to AI Workflows — all modules, all lessons, lifetime access.

Already purchased? Sign in to restore access.