Documentation
Developer docs
Start with “Why?” Before the endpoints below, here's the engineering case for building on DataTap rather than rolling your own integration on Microsoft Graph — the reactive collection pipeline, scale-to-zero workers, per-tenant provisioning on Azure, and everything you'd otherwise own and operate. Read the technical build-vs-buy case →
Not sure where to start? Just ask.
The DataTap assistant is grounded on the live documentation, connector specs and API reference. Describe your use case — Exchange collection, OneDrive backup, user scoping, scheduling — and it returns runnable samples in Python, curl, or whatever language your stack uses. Just ask. No digging through docs, no guessing at field names.
Then start here. Each section below summarizes a part of the documentation and links straight to it — work top to bottom the first time, then jump back to whichever you need.
API reference
The complete, read-only reference for every endpoint: routes, parameters, request and response models, and worked examples. It comes in two parts — a public reference open to everyone, and an admin reference (admin + public) that you unlock by entering a full-scope admin key. Use this when you need the exact shape of a request or the meaning of a field.
Workflows
Task-oriented guides that stitch the endpoints into end-to-end flows — onboarding, collecting Microsoft 365 data, searching the collection, restoring, and the admin operations. Every step comes with a copy-paste Python script you can run against your own tenant. Start here if you're integrating for the first time.
Conventions
The cross-cutting rules that apply across the whole API: how authentication and key scopes work, the three pagination styles, filtering syntax, date formats, resource-id naming, and the standard error codes — plus a few known inconsistencies to be aware of. Skim this once to avoid surprises.
Interactive API (try it out)
The reference above is read-only. To send real requests, open the Apollo-hosted Swagger UI and authenticate with your API key — a tenant key unlocks the public endpoints, an admin key unlocks everything. Best for exploring and validating calls before you write code.