Discover, test, secure, and operate Qeet ID and Qeet Notify from one OpenAPI-first workspace, with live references, generated code, and production-ready auth flows.
/v1/auth/meSend$ curl https://api.id.qeet.in/v1/auth/me -H "Authorization: ApiKey qk_live_..." -H "X-Qeet-Env: production"
{
"principal": "usr_8f1c2a9e",
"tenant": "org_ace19f2c",
"scopes": ["identity.read", "openid"],
"trace": "qtr_4b7d9a"
}webhook.delivered
hmac verified · retry 0
schema
OpenAPI 3.1
audit
trace persisted
codegen
JS · Go · Python
Trusted by engineering teams worldwide
Speaks the open standards you already trust
Discover, integrate, manage, secure, monitor and scale every API your business runs — from a single control plane, behind a single credential.
Any client
Unified API Gateway
api.qeet.in
Qeet ID
Live API
Qeet Notify
Live API
Qeet Logs
Observability
Qeet Pay
Payments
Qeet People
HCM
Qeet News
Media
Each product is independently useful and shares a single platform for identity, notifications and audit. Two APIs are live today, with more on the way.
Passkeys-first authentication, MFA, OAuth 2.1 / OIDC, SAML SSO, SCIM, sessions and RBAC.
Open referenceMulti-channel transactional messaging — email, SMS, WhatsApp, in-app and webhooks.
Open referencePrivacy-first, identity-aware log management — and the group's shared audit sink.
View docsPayments, subscriptions and billing — India-first, with UPI and GST built in.
View docsHCM for the modern org — directory, workforce records and people workflows.
View docsAI-first global news platform — multi-perspective, multilingual and trust-first.
View docsNo moving targets. The same guarantees back every product on the platform — from your first call to production scale.
Requests terminate at the edge closest to your users, with regional failover behind a single hostname.
Every endpoint and schema is generated from a versioned spec — never hand-written, never stale.
Explicit API versions with additive-only changes, and idempotency keys that make retries safe.
Mutual TLS, OAuth 2.1 and least-privilege API-key scopes secure every call by default.
Every privileged action is written to an immutable, queryable audit log via Qeet Logs.
Subscribe to signed webhooks for the events that matter — no polling, no missed state.
Two hundred and fifty-plus operations across products — searchable, filterable and instantly reachable. Discovery is a feature, not a scroll.
/v1/usersQeet ID↵/v1/users/{id}Qeet ID/v1/organizationsQeet ID/v1/messagesQeet Notify/v1/audit/eventsQeet IDEverything you need to go from first request to production — quickstart, authentication, errors, SDKs and a live, runnable reference.
/v1/auth/merequires identity.readEndpoint guide
Returns the current user, tenant, session, and granted scopes for any API key or OAuth token. Examples stay language-aware and production-ready.
$ curl https://api.id.qeet.in/v1/auth/me \ -H "Authorization: ApiKey qk_live_..." 200 OK { "principal": "usr_8f1c2a9e", "scopes": ["identity.read"] }
GET/v1/auth/mePOST/v1/usersPOST/v1/messages{
"user_id": "usr_8f1c2a9e",
"tenant_id": "org_ace19f2c",
"scopes": ["identity.read", "openid"]
}{
"id": "usr_a1b2c3d4",
"email": "ada@qeet.in",
"status": "invited",
"created_at": "2026-07-06T09:00Z"
}{
"id": "msg_7k2p9x",
"channel": "email",
"state": "queued"
}A first-class console lives next to every endpoint. Send authenticated requests, inspect real responses, and copy the exact code you need.
One credential, every API. Authenticate with the standard that fits, authorize with fine-grained scopes, and let the gateway enforce it.
/oauth/token TLS 1.3grant_type=client_credentials scope=identity.write notify.send
Access token · decoded
valid 3600s"sub": "svc_billing_worker",
"iss": "https://id.qeet.in",
"exp": 1751792400,
"scope":
openapi.yamlOpenAPI 3.1 qeet sdk generateimport { Qeet } from "@qeet/sdk";
const qeet = new Qeet({ apiKey: process.env.QEET_KEY });
const user = await qeet.identity.users.create({
email: "ada@qeet.in",
});
// ^? User — fully typedclient := qeet.New(os.Getenv("QEET_KEY")) user, err := client.Identity.Users.Create(ctx, &qeet.NewUser{Email: "ada@qeet.in"}, ) // user *qeet.User, err error
from qeet import Qeet qeet = Qeet(api_key=os.environ["QEET_KEY"]) user = qeet.identity.users.create( email="ada@qeet.in", ) # user: User
Ship in the language your team already writes. Every SDK is generated from the same OpenAPI document that powers the reference — so it always matches the live API.
Average latency
p99 at the edge
Uptime SLA
across all regions
API endpoints
fully OpenAPI 3.1 typed
Countries served
via multi-region edge
Platform products
one key, every API
SDK languages
cURL · JS · Go · Python
Understand traffic, performance and failures across every endpoint — without wiring up your own metrics pipeline first.
Requests
Last 7 days · all products
Requests · 7d
8.42M
+18%
Success rate
99.98%
+0.01
p95 latency
42ms
−6ms
Top endpoints
POST /v1/messages34%GET /v1/users26%POST /v1/auth/token21%GET /v1/audit/events12%All systems operational
status.qeet.inEvery region, every endpoint, probed around the clock. See the health of your integration the way your users experience it.
Fair, transparent limits keep every tenant fast. You always know your budget, and hitting a limit is a signal — never a surprise outage.
Resets in 41s · burst up to 1,500 rps
Response headers
X-RateLimit-Limit:10000
X-RateLimit-Remaining:3820
X-RateLimit-Reset:1751792460
X-RateLimit-Policy:10000;w=60
Free
250k/mo
Growth
10M/mo
Enterprise
Custom
User · v2026-06-01no breaking changesVersioning is a contract, not a chore. Ship improvements continuously while every integration keeps working exactly as it did the day it went live.
Push the moments that matter to your systems — securely signed, reliably delivered, and fully observable from first fire to final ack.
POST https://api.acme.com/hooks
X-Qeet-Signature: t=1751792…, v1=3a8f9c…
user.created1200 OKmessage.delivered1200 OKinvoice.paid2 retryingpayment.failed1200 OKSSO, RBAC, audit and least-privilege access are first-class across the platform — capabilities of the live specs, not bolt-on add-ons.
OIDC and SAML 2.0 SSO with SCIM 2.0 provisioning for your entire workforce.
Fine-grained roles, permissions and ReBAC checks across multi-tenant organizations.
WebAuthn passkeys, TOTP and step-up MFA are first-class on every auth flow.
Scoped API keys, service accounts and AI-agent credentials with least privilege.
Per-key limits with clear rate-limit headers and burst controls on every response.
Immutable audit logs, usage analytics and tenant operations across the platform.
Acme Corp
Workspace · 12 members
Ada Mehta
All products
Priya Sundaram
ID · Notify
Tomás García
ID · read/write
dev@acme.com
Invitation pending
Ship together without stepping on each other. Roles, environments and provisioning that scale from a two-person startup to a global enterprise.
The Qeet CLI turns every capability into a command. Authenticate, call any endpoint, generate SDKs and tail logs — without leaving your shell.
$ brew install qeetInstall the CLI$ qeet login ✓ Authenticated as ada@acme.com $ qeet keys create --name ci --scope identity.read ✓ qk_live_9f2c… · copied to clipboard $ qeet api GET /v1/users/usr_8f1c { "id": "usr_8f1c", "status": "active" } $ qeet sdk generate --lang go ✓ Generated qeet-go in 1.2s $ qeet logs tail --product id 2026-07-06T09:14Z 200 POST /v1/messages 41ms
Qeet meets your stack where it is — native SDKs, first-class observability exports, and open webhooks that connect to anything else.
Don't see yours? Every event and metric can stream out over signed webhooks and the REST API — so you can wire Qeet into anything.
Explore the APINo SDK to install, no boilerplate. Grab a key, send a header, and you're talking to production.
Authorization: ApiKey <key> (Qeet ID) or X-Qeet-Api-Key (Qeet Notify).curl https://api.id.qeet.in/v1/auth/me \
-H "Authorization: ApiKey qk_live_..."const res = await fetch("https://api.id.qeet.in/v1/auth/me", {
headers: { Authorization: "ApiKey qk_live_..." },
});
const principal = await res.json();req, _ := http.NewRequest("GET", "https://api.id.qeet.in/v1/auth/me", nil)
req.Header.Set("Authorization", "ApiKey qk_live_...")
res, _ := http.DefaultClient.Do(req)import requests
res = requests.get(
"https://api.id.qeet.in/v1/auth/me",
headers={"Authorization": "ApiKey qk_live_..."},
)
print(res.json())We evaluated five identity platforms. Qeet ID was the only one that had passkeys, SCIM, and a real OpenAPI spec on day one. The reference console alone saved us two weeks of integration work.
Arjun Mehta
CTO · Lattice Systems
Switching our notification stack to Qeet Notify took one afternoon. The multi-channel API is genuinely well-designed — same payload shape whether you're sending email, SMS or webhooks.
Priya Sundaram
Lead Platform Engineer · Finsight
The audit log API is the first one I've seen that's actually queryable in real time. Our compliance team went from dreading audit reviews to running them in self-service.
Tomás García
Platform Architect · Buro Cloud
Every plan includes the full interactive API reference, live request console, and OpenAPI 3.1 specs. No surprises.
Everything you need to build and ship your first integration.
For teams shipping production workloads at scale.
For organizations that require compliance, SLA and dedicated support.
All plans include multi-region edge routing, OpenAPI 3.1 specs, and the interactive reference console. —Compare plans ↗
Still have questions? Open the reference and run a live request — or reach us at support@qeet.in.
You can authenticate using an API key (pass it as Authorization: ApiKey <key>) or via OAuth 2.1 with a Bearer token. API keys are created in the Qeet console. For machine-to-machine flows, use the client credentials grant. Full details are in the Authentication guide.
Yes. A single API key or OAuth token is scoped to the products and permissions you grant it — so one credential can call Qeet ID, Qeet Notify, and any other live product. Scopes are additive and least-privilege by default.
Yes. Every spec is published as OpenAPI 3.1 YAML under apis.qeet.in/specs/. The interactive reference is built directly from these files — they're never hand-written, so they're always in sync with the actual API surface.
The reference ships ready-to-run code snippets for cURL, JavaScript, Go, and Python. Idiomatic SDK packages are on the roadmap. You can also import any spec into Postman — a pre-built collection for Qeet ID is available on the SDKs page.
The Developer plan is free forever and includes 250,000 API requests per month, access to the full interactive API reference, and community support. It's designed to let you ship your first integration without a credit card.
Growth plans include a 99.9% monthly uptime SLA; Enterprise plans include 99.99%. All plans benefit from multi-region edge routing and automatic regional failover — SLA tiers add contractual commitments and credits.
Webhooks are delivered as signed HTTP POST payloads — each request includes an X-Qeet-Signature header so you can verify authenticity before processing. Deliveries are retried with exponential backoff. You can subscribe to events in the Qeet console.
One platform for every API your business needs. Discover, integrate, secure, monitor and scale — starting with your first request today.
$ curl /v1/auth/me 200 OK 42ms { "principal": "usr_8f1c2a9e", "trace": "qtr_4b7d9a" }