Sustema

D02

Create and secure your workspace

Candidate documentation for reading and synthetic examples. Account creation, live API access, SDKs, collections and MCP are not available here. A released service profile and matching integration instructions are required before use.

Personal free testing is designed to start without a payment card or company registration. Follow email verification and the supported passkey or password-plus-authenticator flow, then accept the applicable account/testing terms. Email verification alone is not multi-factor authentication.

A personal workspace and a company workspace are separate. Joining a company requires a valid invitation or the defined company-formation and authority checks; sharing an email domain does not automatically make you a member. Moving into a company does not silently transfer your personal request history or credentials.

In the workspace overview, check which capabilities are available, whether access is ready and how much allowance is usable. A pending or unavailable allowance is not an invitation to retry activation repeatedly. A free account is not an unlimited service or a production entitlement; use the published profile and account terms.

The signed-in tester uses your current human session and permitted workspace context. It does not require you to paste a machine credential into the browser. To integrate your application, create an integration with the appropriate environment and scope. Give it a recognisable name and keep its owner/steward clear.

Save a newly delivered secret through the protected one-time flow in your own approved secret store. Do not put it in a public repository, browser local storage, screenshots or support messages. If delivery is lost, use the supported reissue/rotation flow; old secrets are not displayed again. Rotate or revoke a suspected compromised integration and review the stated effect.

The data API uses a validated OAuth access token. An identity-provider ID token, browser session cookie or client secret is not a substitute. Your integration instructions must supply the qualified token endpoint, audience, scopes and credential flow for the selected environment; this draft does not invent those values.

Account-terms acceptance and free-testing acceptance are separate. Opening a workspace does not itself provide funding, free-tier consent or company membership. Use the exact versioned terms and actual service-specific privacy information supplied by the accepted access flow; the website privacy policy is not a substitute for account-service information.

Continue with account access and recovery or application credentials.