HonestHook

Free API key (1,000/mo)Sign in

Home · Solutions · By who you are

For agencies — many clients, one response shape

Reporting across clients on platforms that disagree about field names. The envelope is the same everywhere, and a number the platform hides comes back null instead of zero.

The problem

Client reporting breaks on the exceptions: one platform rounds, one hides the count, one renames the field. A report that silently prints zero for a hidden number is worse than a gap, because nobody checks it.

What answers it — 2 endpoints

Shape, parameters and the errors each one returns are in the endpoint reference, generated from the same catalogue the router reads.

The recipe

There is no recipe for this one yet. The 3 that exist are all about the archive, and pointing you at one of them from here would send you to steps that do not answer this question. The recipe index says which they are.

Where to go next