OpenAPI-first contracts
Versioned specifications describe endpoints, schemas, and authentication.
The unified developer platform for current and future Qeet products. Explore API references, guides, SDKs, search, and OpenAPI-first workflows from one workspace.
curl http://localhost:4001/v1/auth/me \
-H "Authorization: ApiKey <your-key>" \
-H "Accept: application/json"const response = await fetch(
"http://localhost:4001/v1/auth/me",
{ headers: {
Authorization: "ApiKey <your-key>"
}}
);
const principal = await response.json();req, err := http.NewRequest(
"GET", "http://localhost:4001/v1/auth/me", nil,
)
if err != nil { log.Fatal(err) }
req.Header.Set("Authorization", "ApiKey <your-key>")
res, err := http.DefaultClient.Do(req)response = requests.get(
"http://localhost:4001/v1/auth/me",
headers={
"Authorization": "ApiKey <your-key>"
},
)
print(response.json()){
"principal": "usr_8f1c2a9e",
"tenant": "org_ace19f2c",
"scopes": ["identity.read","openid"],
"authenticated": true
}{"principal":"usr_8f1c2a9e","tenant":"org_ace19f2c","scopes":["identity.read","openid"],"authenticated":true}Explore current and future Qeet APIs from one consistent platform, with shared reference, guides, SDKs, authentication patterns, and OpenAPI-first workflows.
Identity & access
Authentication, user identity, permissions, and more.
Messaging & events
Transactional notifications, webhooks, and event delivery.
Payments & billing
Payments, subscriptions, refunds, and billing workflows.
Audit & analytics
Privacy-first logs and identity-aware audit trails.
Developer tools
Manage API keys, tenants, and identity settings.
Growing ecosystem
New products. The same developer experience.
Different products. Familiar tools. One developer home that keeps the context with you.
Open specifications. Established identity protocols. Familiar tools that meet you where you build.
Explore authentication Identity protocols are provided by Qeet ID.A clear path from the API contract to a request you can run, inspect, and build on.
/v1/auth/mecurl --include \
http://localhost:4001/v1/auth/me \
-H "Authorization: Bearer $QEET_ID_TOKEN"const token = process.env.QEET_ID_TOKEN;
const response = await fetch(
"http://localhost:4001/v1/auth/me",
{ headers: { Authorization: `Bearer ${token}` } }
);
console.log(response.status, await response.json());import os
import requests
response = requests.get(
"http://localhost:4001/v1/auth/me",
headers={"Authorization": f"Bearer {os.environ['QEET_ID_TOKEN']}"},
)
print(response.status_code, response.json())AuthorizationBearer tokenapplication/jsonMore products. The same discipline. Open specifications, checked into source control and built into one developer experience.
Explore the API surfacepublic/specs/Source controlledqeet-id.yamlQeet ID0.2.0395 operationsOpenAPI 3.1 qeet-notify.yamlQeet Notify1.0.0112 operationsOpenAPI 3.1 qeet-pay.yamlQeet Payv1273 operationsOpenAPI 3.1 Versioned specifications describe endpoints, schemas, and authentication.
CI checks references, operation IDs, and consistency between split and bundled specs.
Use the authentication scheme and permissions defined by each product.
Error envelopes, HTTP status codes, and retry guidance in one place.
Guides, tags, and operations feed the same cross-product search index.
A shared product registry powers navigation, environments, and reference routes.
Start a new integration. Pick up where you left off. Find the answer that moves your work forward.
Ready to build
Explore the API reference, follow the quickstart, and start integrating in your local environment, all in one place.