Each guide below builds one integration end to end, using several parts of the API together. Pick the row closest to what you are making.
| If you're building… | Start with |
|---|---|
| An event with check-in, tickets, and rewards for attending | Running an Event |
| A page, kiosk or link preview that shows who a tapped card belongs to | From a Tap to a Profile |
| Rewards handed out in person, to people who may not have an account | Rewarding Someone Without an Account |
| A paid or tiered membership, with perks that follow the tier | Building a Membership Program |
| A reward that fires from a form, a spreadsheet, or another tool | Rewarding a Google Form Submission |
| Access to a chat server, forum or private space that follows a membership | Gating a Members-Only Community |
By the problem you're solving
If your case is not in the table, find the shape it matches:
Something outside Davi should cause something inside it, such as a form submission, a purchase, or a scan in your own app. Start with Rewarding a Google Form Submission. It is the smallest complete example, and it solves the token problem every unattended automation has.
Something inside Davi should cause something outside it, such as a membership granting a role or a check-in updating your records. Start with Gating a Members-Only Community, then Receiving Webhooks for the delivery contract.
You show Davi's data in your own interface. From a Tap to a Profile needs no token.
You run something in the physical world: doors, stands, counters. Running an Event covers letting people in; Rewarding Someone Without an Account covers giving them something.
If none of these fit
Everything the guides use is documented on its own:
- Core Concepts: how users, cards, wallets, organizations and profiles relate.
- API reference: every endpoint, generated from the OpenAPI document.
To set something up for your own organization rather than build against it, use the Davi app. See When to use the API.