master-zapier-plan-draft/docs/sphinx/modules/verae-zapier-middleware/middleware/authenticate.md
George Lambert 345aeeead9
Some checks are pending
offline / test (push) Waiting to run
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 Permalink Blame History

verae-zapier-middleware/middleware/authenticate

Package: verae-zapier-middleware
Source: packages/verae-zapier-middleware/src/middleware/authenticate.js
Lines: 34

What this module is

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

Exports

authenticate

Types / interfaces / classes

None extracted.

Functions

No top-level functions extracted.

Methods (class / object)

Name Parameters
next (none)

What it imports / requires

  • ../lib/tokens.js
  • ../services/authService.js
  • ../errors.js
  • ../debug/logger.js

Call graph (identifiers invoked)

createDebugger, asyncHandler, async, extractBearerToken, resolveAuthContext, startsWith, debug, next

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.