GraphQL schema

The SDK calls one GraphQL endpoint per workspace:

https://{workspace}.uidu.org/graphql

The schema is large — most of it is internal admin surface (invoices, expense reports, journal entries, approvals) that @uidu/client deliberately doesn't expose. The Apps section is the curated, public-facing slice.

Explore the schema interactively

Open Apollo Sandbox with the uidu endpoint pre-filled. You'll get autocomplete, a schema browser, query history, and shareable URLs — no install required.

To run authenticated queries, click the Headers tab in Sandbox and add:

X-Uidu-Public-Token: pk_live_...

(For your own workspace, swap uidu.uidu.org for {your-workspace}.uidu.org in the URL.)

Types in your editor

If you're writing TypeScript, the canonical reference is the generated types file in the SDK repo:

packages/client/src/generated/index.ts

Every type the SDK consumes — Page, Event, Booking, Course, every connection, every input — is exported from there. The file is regenerated against the live schema on every build of @uidu/client.

Import them directly when you need them:

import type {
  Page,
  Event,
  Booking,
  Course,
  Campaign,
  Contact,
  Deal,
  KbArticle,
} from '@uidu/client';

Alternative explorers

• GraphiQL (https://github.com/graphql/graphiql) — self-host the React component if you want an explorer inside your own app.
• Insomnia / Postman — both have first-class GraphQL support with schema introspection. Useful for testing mutations with custom auth flows.
• graphql-request + a .graphql file — the @uidu/client approach, ergonomic for production code.

Why we don't ship 3000+ auto-generated reference pages

We tried (with graphql-markdown) and the output buried the curated docs under thousands of internal types. Apollo Sandbox is a better experience for the rare cases where you want to dig into the schema directly, and generated/index.ts is a better experience for type lookups while you write code.