Workspace
Create one Taiega organization and configure its real locations, services, resources, and availability. Hosted booking pages need no API key.
Taiega integration standard
One contract.
Every customer.
Connect a product to Taiega through the same tenant, credential, signing, rollout, and rotation process every time.
Standard process
Six stages from workspace to production.
Credential
Issue one managed key for each environment and server workload. Select only the scopes that workload needs.
Server
Store the client identifier and one-time signing secret in the consumer's server-side secret manager.
Readiness
Check API health, then verify catalog and availability before enabling any booking mutation.
Reliability
Persist idempotency keys before sending. Verify and deduplicate signed webhook events.
Rotation
Add a replacement key, deploy and verify it, then revoke the retired key without downtime.
Server setup
Four values. Kept off the client.
TAIEGA_API_ORIGIN=https://taiega-api.vercel.app
TAIEGA_ORGANIZATION=<workspace-slug>
TAIEGA_CLIENT_ID=<managed-client-id>
TAIEGA_CLIENT_SECRET=<one-time-signing-secret>Security contract
Controls that travel with every integration.
Tenant bound
Every key belongs to one Taiega organization. The database rechecks tenant, status, scope, rate limit, and revocation.
Replay resistant
Requests use HMAC-SHA256, a five-minute timestamp window, and a fresh nonce that is consumed once.
Server only
Signing secrets never belong in browser code, mobile binaries, URLs, analytics, logs, or customer records.
Fail closed
Runtime readiness fails when credential metadata, database authorization, or encryption-key configuration drifts.
Recoverable
Mutations use durable idempotency keys. An uncertain response is recovered with the original operation rather than duplicated.
Auditable
Issuance, revocation, configuration changes, and webhook delivery are recorded without storing plaintext secrets.
Permissions
Grant only what the workload uses.
Basic Scheduling is an included capability profile. Credentials authorize a server workload; they do not represent a person, a booking-page visitor, or a billing plan.
| Scope | Purpose |
|---|---|
availability:read | Discover the configured catalog and available appointment times |
booking:read | Read individual bookings and the organization agenda |
booking:write | Create bookings |
booking:reschedule | Reschedule bookings |
booking:cancel | Cancel bookings |
Public contract
Readable by people and deployment tooling.
The versioned JSON document publishes the supported authentication protocol, scopes, endpoint catalog, reliability rules, and rollout gates without exposing customer or credential information.
View taiega-integration/v1 →