Davi is a platform that ties together three things:
- Identity: who a person is, and their public profile pages.
- Rewards: a points and rewards ledger held in wallets.
- Credentials: tap-able cards (NFC, QR, or virtual) that route to a profile and a wallet.
It runs branded membership cards, NFC smart business cards, event badges, and loyalty programs. Organizations issue cards, run activities, define membership tiers, and distribute rewards. Users carry the cards, collect rewards, and present a profile when they tap.
These docs are for developers connecting Davi to a product, a website, or another tool.
When to use the API
Use the Davi app to do the work itself:
- Creating cards, rewards, activities, sessions and membership tiers
- Publishing a reward, issuing one to somebody, checking people in
- Setting up webhooks, and registering an application
Some of these are only available in the app, so every integration starts there. For anything the app already does, the API offers no advantage.
Use the API to connect Davi to something else:
- Something outside Davi should cause something inside it. A form submission issues a certificate; a purchase in your shop grants a membership.
- Something inside Davi should cause something outside it. Joining a tier grants a role in your community; a check-in updates your own records.
- Your product shows Davi's data in your own interface, to your own users.
- People sign in with Davi instead of creating another account.
- The volume is too large to do by hand, such as thousands of cards or a nightly job.
If a task is possible in the app but tedious, an integration is a convenience. If it has to happen somewhere else, automatically, or inside your own product, it needs the API.
What you can build
- Sign in Davi users with OAuth 2.0 / OpenID Connect and read their profile, activity, and reward data, with their consent.
- Act on behalf of an organization: manage its memberships, activities, rewards, and reward triggers using an org-scoped token.
- React to events in real time with webhooks: memberships starting, changing and ending, and rewards redeemed.
What to build has worked examples of each.
How these docs are organized
Get started is a lesson. The Quickstart takes you from nothing to an authenticated request.
Concepts explains the model: how the pieces relate and why they are arranged that way.
The middle sections are how-to guides, grouped by the thing they act on, using the vocabulary from Core Concepts:
| Section | Covers |
|---|---|
| Authentication | Scopes, signing users in, and acting on behalf of an organization. |
| User | Fetching a user, their activities, and their contacts. |
| Card | Claiming cards, and the wallets and transactions behind them. |
| Organization | Activities and check-ins, and receiving webhooks. |
| Memberships | Tiers, membership management, and feature gating. |
| Reward | Defining rewards, issuing them, and automating issuance. |
Guides holds recipes that span more than one of those sections, such as a whole event or a membership program end to end.
Reference is for looking things up mid-task: request mechanics, scopes, webhook events, and the card formats. The API reference lists every endpoint with its request and response shapes, generated from the Davi OpenAPI document.
Next steps
- Quickstart: register an app and make your first authenticated request.
- Core Concepts: how users, wallets, cards, organizations, and profiles fit together.