Documentation

Waitlist

Submit waitlist registration through the local application API.

Playground

Send these requests to your own running sidecar. Values stay in this browser.

Not connected

Base URL Bearer token optional Session token optional

How this works

The sidecar listens on a loopback port chosen at startup and prints it in its ready line; use that URL and the CADCAMFUN_TOKEN it was started with. Requests go straight from this page to that address.

The sidecar sends CORS headers only to the Tauri origins and to http://localhost or http://127.0.0.1 on any port. From the hosted docs the browser blocks the response, so run the docs locally (bun run dev in packages/web) to use the playground, or copy the request as curl. To experiment without touching real data, start the sidecar with CADCAMFUN_DATA_DIR pointed at a throwaway directory — see the API walkthrough.

Operations

1 endpoint in the waitlist group, generated from the sidecar's own OpenAPI document. Protected operations take Authorization: Bearer $CADCAMFUN_TOKEN; see authentication. Behaviour and limits are in the subsystem guide.

post

/api/waitlist

waitlist.join

Waitlist operations in 3D Drag to orbit · scroll to zoom · right-drag to pan

One block per operation (1), stacked per resource section of this page and coloured by method: green GET, orange POST, blue PUT, violet PATCH, red DELETE. Generated from the OpenAPI document at build time.

/api/waitlist

post /api/waitlist # waitlist.join

Requires Authorization: Bearer <token>.

Request body · required · application/json

{
  email: string
}

Responses

201 object application/json

{
  success: true
  message: string
}

400 WaitlistBadRequestEncoded application/json

WaitlistBadRequestEncoded

401 UnauthorizedEncoded application/json

UnauthorizedEncoded

409 WaitlistConflictEncoded application/json

WaitlistConflictEncoded

500 WaitlistInternalEncoded application/json

WaitlistInternalEncoded

SDK example

waitlist.join

import { CadCam } from "@cadcamfun/api/sdk"

const client = CadCam.make({
  baseUrl: process.env.CADCAMFUN_URL!,
  headers: { authorization: `Bearer ${process.env.CADCAMFUN_TOKEN}` },
})

// WaitlistJoinInput
const result = await client.waitlist.join({
  email: ""
})

curl

POST /api/waitlist

curl --request POST "${CADCAMFUN_URL}/api/waitlist" \
  --header "Authorization: Bearer ${CADCAMFUN_TOKEN}" \
  --header "Content-Type: application/json" \
  --data-binary @request.json

Try it

Request body application/json

Schemas

Named schemas reachable from this group's parameters, bodies and responses. A ? marks an optional field; | null marks a field that may be present with a null value.

UnauthorizedEncoded

{
  _tag: "Unauthorized"
  message: string
}

WaitlistBadRequestEncoded

{
  _tag: "WaitlistBadRequest"
  success: false
  message: string
}

WaitlistConflictEncoded

{
  _tag: "WaitlistConflict"
  success: false
  message: string
}

WaitlistInternalEncoded

{
  _tag: "WaitlistInternal"
  success: false
  message: string
}

Calling this group

Operation ids have the form waitlist.<name>. The generated Promise SDK (@cadcamfun/api/sdk) exposes most of them as client.<namespace>.<method>(input), where input is one flat object of path parameters and body fields; each card's SDK example shows the exact accessor and input type. Multipart uploads, binary or JavaScript responses and raw webhooks are not generated; those cards show fetch instead.

Errors from the Promise SDK

import { CadCam, ClientError } from "@cadcamfun/api/sdk"

const client = CadCam.make({
  baseUrl: process.env.CADCAMFUN_URL!,
  headers: { authorization: `Bearer ${process.env.CADCAMFUN_TOKEN}` },
})

try {
  await client.projects.list()
} catch (error) {
  if (error instanceof ClientError) {
    // Transport | UnexpectedStatus | UnsupportedContentType | MalformedResponse | SseEventTooLarge
  } else {
    // a declared error body: switch on error._tag
  }
}

Troubleshooting

Symptom	Likely cause	Fix
401 on every call	Token from a previous launch, or missing `Bearer` prefix	Send `Authorization: Bearer <token>` with the token the sidecar was started with.
400 before anything happens	Body or parameter does not match the schema	Compare the payload with the request schema on the card.
403 or 404 on a record you can see elsewhere	The acting account differs	Send the right `x-session-token`, or use the local profile that owns the record.
409	Conflicting state, such as a duplicate name or a stale branch head	Re-read the resource and retry with current data.
Try it says "blocked by CORS"	The docs are served from a non-loopback origin	Run the docs locally or copy the request as curl.
Connection refused	The sidecar restarted on a new port	Read the port from the new `ready` line.