Developer projects and environments
Organize Torq applications, credentials, origins, webhooks, quotas, and preview environments.
A Torq Developer project is an approved organization plus one or more applications. Each application binds its environment, credential class, scopes, browser origins, quotas, webhooks, wallet sessions, and usage records. Project access remains Developer Preview.
Project model
| Object | Purpose |
|---|---|
| Organization | Owns membership, applications, audit records, and production-access requests. |
| Application | Isolates one integration and its environment policy. |
| Secret key | Server-only authentication for approved scopes. |
| Publishable key | Browser-safe only when bound to an approved origin and wallet session. |
| Webhook endpoint | Receives signed, retryable event deliveries for one application. |
| Sandbox admission | Grants controlled Sepolia fixtures, faucet use, and reset policy. |
Create and operate a project
- Accept the Torq-issued Developer Preview invitation.
- Establish the wallet-first Developer Console owner session.
- Create separate test applications for separate products or trust boundaries.
- Register exact browser origins; wildcards are not an authorization shortcut.
- Issue only the key type and scopes the application requires.
- Configure and verify webhook endpoints before relying on event-driven state.
- Inspect usage, audit, quotas, and stable error codes during testing.
- Submit a production-access request only after the Sepolia integration is complete.
Tooling boundary
No Torq CLI is published. Manage approved applications through the Developer Console and the
documented /v1/organizations, /v1/applications, /v1/keys, /v1/webhook-endpoints, /v1/usage,
/v1/audit-log, /v1/sandbox, and /v1/production-access-requests APIs. Do not install or execute
an undocumented torq command.
See Developer Console, Authentication, Testing, and Platform status.