This guide walks you through the full integration flow: obtaining credentials, registering a card dispatch, calling the Status API, reading the response, and surfacing delivery information to your cardholders.Documentation Index
Fetch the complete documentation index at: https://docs.varmo.fi/llms.txt
Use this file to discover all available pages before exploring further.
Get your API key
Contact Varmo to request API access. Once your account is provisioned, Varmo issues you an API key scoped to your organisation.Pass the key in the Keep your key secret — never expose it in client-side code or public repositories.
Authorization header of every request:Register a card dispatch
When your issuer backend dispatches a card to a cardholder, notify Varmo so it can begin tracking the delivery. Your backend sends the dispatch event to Varmo, and Varmo returns (or assigns) a
dispatch_id — a UUID that identifies this specific card journey.Store the dispatch_id alongside your internal order record. All subsequent status queries for this card use that ID.Call the Status API
Query
GET https://api.varmo.fi/v1/status/{id} at any point after dispatch — on page load, on a scheduled interval, or in response to a user action. Replace {id} with the dispatch_id you stored in the previous step.Read the response
A successful request returns a JSON object with delivery state, predicted arrival dates, and UI copy:Key fields to understand:
status— the current delivery state of the card (e.g.dispatched,in_transit,delivered).prediction.delivery_window— theminandmaxdates Varmo predicts for arrival, expressed as ISO 8601 date strings.prediction.confidence_level— how confident Varmo is in the window:High,Medium, orLow.ui_suggestion— a ready-to-render object containing alocale, arecommended_messagefor the cardholder, and arecommended_actionyour app should surface (or"None"if no action is needed).