offline / test (push) Waiting to run

Details

Bind each customer to a Verae userId for hop tracing

Signup registers/binds a Verae central user and stores veraeUserId. Public access stays the zappier API key. Chain JWTs stay server-side behind tokenRef. Authz, billing, and jobs.watch carry veraeUserId.

2026-09-11 16:18:06 -04:00

1.3 KiB

Raw Blame History

`zappier/statement`

Package: zappier
Source: packages/zappier/src/statement.ts
Lines: 41

What this module is

Implementation module in zappier. The tables below are extracted from the source (signatures + JSDoc).

Exports

composeStatement

Types / interfaces / classes

None extracted.

Functions

Name	Parameters	Param types (JSDoc)	Returns
`composeStatement`	`args: {
customerId: string;
veraeUserId?: string;
prepaidCents: number;
credits: CreditAdjustment[];
usage: UsageEntry[];
invoices: Invoice[];
}`	—	`unknown`	see Call graph

What it imports / requires

./credits
./invoicing
./usage

Call graph (identifiers invoked)

composeStatement, filter, map, now, toISOString, slice, reverse

Each identifier is a call site in this file. Follow the import list to see the defining module; open that module’s MD for parameter and return types.

Return values (how to read this)

HTTP route handlers return Express res.json(...) bodies (see route docs).
Zapier perform functions return a single object (creates) or an array (triggers/searches).
Pricing functions return integer cents on Quote.totalCents.

1.3 KiB Raw Blame History Unescape Escape

zappier/statement