Taiega Help Center

Quickstart

Create a project in the API Console, issue one named key for one server workload, copy the secret once, and store it in a protected server environment. Install the SDK and request the workspace catalog before enabling writes.

npm install @taiega/sdk

import { TaiegaClient } from "@taiega/sdk";

const taiega = new TaiegaClient({
  baseUrl: process.env.TAIEGA_API_ORIGIN!,
  clientId: process.env.TAIEGA_CLIENT_ID!,
  secret: process.env.TAIEGA_CLIENT_SECRET!,
  organization: process.env.TAIEGA_ORGANIZATION!
});

const catalog = await taiega.catalog();

Authentication and request signing

Taiega credentials belong on a trusted server. The SDK signs the timestamp, nonce, method, path, and request body. The full secret must never enter browser JavaScript, a mobile application, source control, screenshots, or support messages.

Use separate keys for development, staging, and production.
Grant only the scopes required by the workload.
Record the key owner and rotation date.
Disable a suspected key immediately, then replace and revoke it.

TAIEGA_API_ORIGIN=https://taiega-api.vercel.app
TAIEGA_CLIENT_ID=<server client identifier>
TAIEGA_CLIENT_SECRET=<server signing secret>
TAIEGA_ORGANIZATION=<workspace URL name>

Booking lifecycle

Read the catalog and availability before creating a booking. Persist one idempotency key before every mutation and reuse the exact key with the exact request after an uncertain result. Use the current booking sequence for rescheduling and cancellation so stale updates fail safely.

Operation	Required reliability control
Read catalog	Confirm the expected workspace and enabled services.
Check availability	Send the intended service, resource, range, and time-zone context.
Create booking	Persist and send a matching Idempotency-Key.
Reschedule or cancel	Send the current booking sequence and a new operation key.

Webhook verification

Taiega delivers booking lifecycle webhooks at least once. Verify the signature over the unmodified request body before parsing the event. Deduplicate by event ID, apply sequence numbers monotonically, and return success only after durable processing or queuing.

booking.created
booking.rescheduled
booking.cancelled

The signature contract uses the four documented x-taiega-webhook-* headers. Reject stale timestamps, unknown endpoints, invalid signatures, duplicate event IDs, and sequence regressions.

Production readiness

Verify API health and the exact workspace identity.
Confirm the catalog contains only intended offerings.
Compare availability with configured schedules and time zones.
Exercise idempotent create and recovery in a non-production workspace.
Test rescheduling, cancellation, key revocation, signature failure, and webhook replay.
Monitor request IDs, credential age, last use, and delivery failures.