Tokenized Pages · DocsTokenized Pages are public, single-purpose magic-link pages for external contacts. A FileMaker token in the URL (?token=…) is the only credential — there is no login. Each token points to one record and opens only its matching page.
Pages
| Page | URL | Token type | What it does |
|---|---|---|---|
| Order | /order?token=… | Site | Review site + place a fuel order |
| Inventory Setup | /inventory-setup?token=… | Site | View site + add equipment/inventory |
| Reschedule | /reschedule?token=… | Delivery | Reschedule a delivery to a new date |
| Confirm (vendor) | /confirm?token=… | Delivery | Confirm a delivery’s line items |
| Quote | /quote?token=… | Quote | View a quote (read-only) |
Token rules
- The token must exist in this environment’s FileMaker file (staging → dev FileMaker, production → prod FileMaker).
- It must be non-expired — FileMaker Date_Expired empty or a future date (valid through end of that day).
- It must match the page type: a Site token opens Order / Inventory Setup; a Delivery token opens Reschedule / Confirm; a Quote token opens Quote.
- Tokens are reusable (no single-use / no access log). Revocation is instant — delete the FileMaker Tokens row or set Date_Expired.
API (internal — same-origin, called by the pages)
Each page calls a same-origin endpoint that returns JSON. Handy for a quick check:
| Methods | Path |
|---|---|
| GET · POST | /api/order-links/{token} |
| GET · POST | /api/reschedule-links/{token} |
| GET · POST | /api/inventory-setup/{token} |
| GET | /api/quotes/{token} |
| GET · POST | /api/confirm-links/{token} |
Every response carries a status:
| status | meaning |
|---|---|
| ok | Token valid; the record was found. Response carries the page data. |
| not_found | No such token in this environment’s FileMaker, wrong page for the token’s type, or the linked record is missing. |
| expired | Token found but past its FileMaker Date_Expired. |
| error | A submit failed validation or the FileMaker write errored. |
Failures return HTTP 200 with only a status — the endpoint never reveals whether a token exists.
How it works
The pages call the same-origin /api/* route handler, which runs server-side and talks to the FileMaker Data API directly (no intermediary): it resolves the token on the Tokens layout (__kp_Token), gates on Date_Expired, then reads/writes the linked record’s layout. FileMaker credentials live only in the server’s environment — never in the browser.
Environments
| Env | App | FileMaker |
|---|---|---|
| Staging | devlinks.fuellogic.net | dev FileMaker |
| Production | links.fuellogic.net | prod FileMaker |
A token only resolves in the environment whose FileMaker contains it.