master-zapier-plan-draft/docs/sphinx/modules/verae-access-web/gate.md
George Lambert 1b199ca4d4
Some checks are pending
offline / test (push) Waiting to run
Separate Zapier, web, API, and leaf access planes with NATS authz
Zapier is one ingress. Direct web, customer API, and S2S leaf nodes are their own services. Every hop to an internal subject must pass verae.access.authz.check (default deny by plane).
2026-09-11 16:05:05 -04:00

1.5 KiB
Raw Blame History

verae-access-web/gate

Package: verae-access-web
Source: packages/verae-access-web/src/gate.js
Lines: 51

What this module is

Implementation module in verae-access-web. The tables below are extracted from the source (signatures + JSDoc).

Exports

PLANE, AUTHZ_CHECK, check, statement, reload

Types / interfaces / classes

None extracted.

Functions

Name Parameters Param types (JSDoc) Returns Calls (same file / helpers)
check subject, { principal, kind, payload } = {} unknown see Call graph
statement customerId, principal unknown see Call graph
reload customerId, cents, principal unknown see Call graph

What it imports / requires

No imports detected.

Call graph (identifiers invoked)

replace, check, fetch, stringify, json, statement, import, connect, split, request, encode, parse, decode, close, reload

Each identifier is a call site in this file. Follow the import list to see the defining module; open that modules 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.