Skip to content
Qeet Group · API Platform

One platform for Every Qeet API.

The unified developer platform for current and future Qeet products. Explore API references, guides, SDKs, search, and OpenAPI-first workflows from one workspace.

API operations
780
API areas
16
Published specs
OpenAPI 3.1
Build. Test. Integrate.
Unified workspace
api.qeet.inlocalOpenAPI 3.1
GET/v1/auth/meSend
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())
200 OKExampleapplication/json
{
  "principal": "usr_8f1c2a9e",
  "tenant": "org_ace19f2c",
  "scopes": ["identity.read","openid"],
  "authenticated": true
}
  • Unified navigationAll products in one place
  • Shared auth patternsClear, product-specific credentials
  • OpenAPI-firstConsistent, developer-friendly
  • Built to scale across productsToday and what's next

Everything you need to build, in one place.

Different products. Familiar tools. One developer home that keeps the context with you.

Switch products. Keep your bearings.
Your stack. Your environment.http://localhost:4001Start with the quickstart

From endpoint to working integration.

A clear path from the API contract to a request you can run, inspect, and build on.

  1. 01DiscoverChoose a product and find your endpoint.
  2. 02UnderstandRead the contract, inputs, and responses.
  3. 03AuthenticateChoose the credential your product expects.
  4. 04IntegrateMake your first request against your local stack.
  5. 05VerifyInspect the response and handle errors.
Your first requestLocal
GET/v1/auth/me
curl --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 token
The response contractQeet ID
200OK
Current principalUser, tenant, session, and granted scopes.application/json
401
UnauthorizedCheck the credential and authorization header.
PrincipalResponse schemaHandle errors & rate limits
Local services. Product-specific credentials. No production requests.Read Quickstart
The contract comes first

Engineered for a growing API platform.

More products. The same discipline. Open specifications, checked into source control and built into one developer experience.

Explore the API surface
public/specs/Source controlled
Product contracts. Shared conventions.
Documented operationsAcross the published product bundles
780
API areasOrganized by product and capability
16
Product referencesOne extensible developer platform
3
From source to reference
  1. Source specs
  2. Vendor & bundle
  3. Validate in CI
  4. Reference & search

OpenAPI-first contracts

Versioned specifications describe endpoints, schemas, and authentication.

Vendored. Validated. Committed.

CI checks references, operation IDs, and consistency between split and bundled specs.

Product-scoped credentials

Use the authentication scheme and permissions defined by each product.

Documented error handling

Error envelopes, HTTP status codes, and retry guidance in one place.

Searchable by design

Guides, tags, and operations feed the same cross-product search index.

Ready for more products

A shared product registry powers navigation, environments, and reference routes.

Ready to build

Start building with Qeet APIs.

Explore the API reference, follow the quickstart, and start integrating in your local environment, all in one place.

Start typing to search the documentation.

↑↓ navigate↵ open