# `verae-zapier-middleware/store/tokenRefs`

**Package:** `verae-zapier-middleware`  
**Source:** `packages/verae-zapier-middleware/src/store/tokenRefs.js`  
**Lines:** 21

## What this module is

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

## Exports

`issueTokenRef`, `resolveTokenRef`

## Types / interfaces / classes

_None extracted._

## Functions

| Name | Parameters | Param types (JSDoc) | Returns | Calls (same file / helpers) |
|------|------------|---------------------|---------|-----------------------------|
| `issueTokenRef` | `tenantId` | — | `unknown` | see Call graph |
| `resolveTokenRef` | `ref` | — | `unknown` | see Call graph |

## Methods (class / object)

| Name | Parameters |
|------|------------|
| `persist` | `(none)` |

## What it imports / requires

- `node:crypto`
- `./db.js`

## Call graph (identifiers invoked)

`issueTokenRef`, `randomBytes`, `toString`, `getStore`, `toISOString`, `persist`, `resolveTokenRef`

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`.