Loading documentation…
Loading documentation…
Organize applications, environments, and usage within one Customer account.
A Project groups the Service Accounts, API requests, and usage for an application or integration. Use Projects to keep applications or environments separate while managing them from one Customer account. All Projects share that account's credit balance, funding, pricing, and login settings.
Every Customer has one active Default Project. If you are building one integration, use it and continue directly to creating a Service Account. Create another Project when you need a meaningful separation such as production versus staging, two products, or two independently operated workloads.
| Project-owned | Customer-wide |
|---|---|
| Service Accounts and Credentials | Balance and funding |
| Request and usage attribution | Pricing and settlement |
| Lifecycle and audit history | Login identity and account settings |
| Future event-delivery configuration | Support and billing ownership |
Recorded activity stays linked to its original Project. Renaming a Project, choosing another Default Project, rotating a Credential, or archiving a Project does not move that activity elsewhere.
Use Dashboard → Projects to create, rename, archive, restore, and inspect Projects. Manage these settings in the Dashboard, not through the public API.
Archiving a Project stops new workload requests and suspends its active Credentials. Restoring the Project makes it available again, but does not reactivate old Credentials; issue replacement Credentials before resuming traffic. You cannot archive the Default Project: choose another active Project as the default first.
Requests and Usage can be viewed across all Projects or filtered to one Project in the Dashboard. Customer Events provides Project-level completion webhooks and authenticated SSE only in environments where the feature is explicitly enabled. It is not generally available. See the Events guide for the current contracts and availability limits. Otherwise, use the documented refresh-status endpoint with bounded polling.
Continue with Service Accounts, Credentials, and Authentication.