API Collections (Postman & Bruno)
Ready-made collections for exercising the Ingest API outside a game engine — verify a token, send a test session, bug report or feedback answer, or debug an integration. The same flow the Godot plugin runs, one request at a time.
Downloads
| File | Use with |
|---|---|
| Postman collection | Postman (also imports into Bruno & Insomnia) |
| Postman environment | Postman — holds your token & base URL |
| OpenAPI spec | Insomnia, Hoppscotch, Stoplight, code generators — anything that reads OpenAPI 3 |
Import
- Postman — Import both JSON files, select the Forge Logger Ingest —
Production environment, then open it and paste your token into
loggerToken. - Bruno — Import → Postman Collection and pick the Postman file above, or
Import → OpenAPI and pick the spec. Set
loggerTokenin the environment. - Insomnia / Hoppscotch / others — import the OpenAPI spec.
Set your token
Everything is pre-pointed at https://ingest.forgelogger.dev. The only value you
must set is your logger token (flg_...), created in the dashboard under your
project’s API Tokens. Auth is Authorization: Bearer <token>;
the token carries the project scope, so no request has a project id in its URL.
Run order
Run the requests top to bottom — each one saves the ids the next needs
(sessionId, uploadId, eventId, reportId), so no manual copy-paste:
- 00 Health — confirm the base URL is reachable.
- 01 Start session — opens a session; stores
sessionId+buildId. - 02 / 03 Events — a single event, then a batch.
- 04 Create upload → 05 Upload bytes — reserve a signed URL, then PUT the
file straight to storage (this request carries no
Authorizationheader — the signed URL is the auth). - 06 Submit report — links the upload and event into a bug report.
- 07 Resubmit (idempotent) — same
clientRequestIdreturns the original report withidempotent: trueinstead of creating a duplicate. - 08 Unauthorized — a request with no token, expected to return
401. - 09–12 Demo feedback — set
feedbackLinkTokenfirst (a link of an open feedback form of the same project). 09 fetches the form and stores itsETagandschemaVersion, 10 revalidates it (304), 11 submits answers and 12 resends them with the sameclientRequestId(idempotent: true).
Versioning
The collections track the /v1 API and are named accordingly. When a new major
version ships, a parallel v2 set is published and the v1 files stay unchanged,
so your saved collection keeps working. The OpenAPI spec’s info.version is the
canonical version marker.
For the full request/response reference, see the Ingest API Reference.