Tigzig APIs Tell You What Went Wrong. If Your Code Reads Only the Status Code, You Never See It.

Published: September 7, 2026

Tigzig APIs try to tell you what went wrong when you hit an error.. with customized error hints. However, if your code reads only the status code, you never see any of it. The hint is sitting there in the response body and one line of printing gets you it.

If you are debugging by hand, just print the whole body. If it is automated code, print out the error block or the specific 'hint' piece. That's it.

No, not all errors carry hints - I try and cover the most common / recurring errors that I see in the logs ..

API catalog: tigzig.com/apis

Quick tips

• Debugging by hand? Just print the whole body. Everything is in there.
• In code, pull out the error block on purpose. In Python that is r.json()["error"]. In JavaScript, await res.json() and then j.error. That gives you the whole error block.
• Where the tailored line sits. On the MF API it is in error.hint. On Vigil, Tremor and the database API it is in error.message. That inconsistency is mine and I am sorting it out; taking the block works on all of them today.

Here is why automated code might miss it

• requests, httpx and aiohttp all return normally on a 400, so nothing stops your code and nothing tells you to look.
• urllib does raise, but str(e) is only "HTTP Error 400: Bad Request" and the body is on e.read().
• raise_for_status() turns a status into an exception, and that exception carries the summary line only, so log the body itself.
• For curl, reach for --fail-with-body.

Quick reference: the API debugging guides

Here are quick reference links to the main Tigzig API debugging guides. Just copy text from the guide and hand it over to your AI agent to debug, along with the API doc link at the end.

• Demystifying Tigzig API errors. Twenty common failure modes across the mutual fund, macro and red-flag APIs, every one of them taken from real server logs.
• Why a SQL error is usually the URL it travelled in. The plus sign, line breaks getting eaten, and clients that stop encoding at the first bracket.
• An ISIN checker for when a fund lookup fails. It separates a malformed identifier from a valid one whose data is simply absent, and where a character has been dropped it often suggests the intended ISIN.
• Getting a 429. Almost never your total, usually many unbounded calls firing at the same instant.
• Is it you or is it me. A status page with 90 days of uptime history per service.

API catalog

• For you: tigzig.com/apis
• For your agent: api.tigzig.com

---

Working on something similar? How I work covers the rates, the availability and what I take on.