Projects
Create sandbox and production projects, separate usage by use case, and keep keys, reports, and alerts tied to the right workload.
Projects split environments and workloads cleanly so usage, keys, and reports stay explainable.
The project page should keep the production handoff visible from the same setup flow.
Project setup should stay tied to the endpoints and events it actually powers.
Avoid mixing protected production traffic into the first integration while ownership and usage are still being proven.
That gives teams an obvious place to create the first key, run test traffic, and review real usage later.
Projects are the unit that make dashboard and API ownership legible for real engineering organizations.
Once that path works, the team can clone the same shape into production with a much lower chance of configuration drift.
Protected production traffic should not be mixed into the first integration.
Project setup should stay tied to the endpoint and event flow it actually powers.
Project setup should flow directly into key issuance once the scope is clear.
The top-level project page should keep environment posture visible before any production move is attempted.
The project page should clarify that keys and webhook targets belong to the project, not to the workspace in general.
Once the project exists, the next serious step is a protected lookup and webhook check.
Projects let a team separate integrations by environment, product line, or internal use case. A sandbox project can stay experimental while production stays clean and easy to review.
That gives teams an obvious place to create the first key, run test traffic, and review real usage later.
Each project can own its own keys, webhook endpoints, usage view, alert thresholds, and export or report history.
Projects are the unit that make dashboard and API ownership legible for real engineering organizations.
The recommended first step after account and organization setup is to create one sandbox project, label the purpose clearly, and connect a single test endpoint before applying for production access.
Once that path works, the team can clone the same shape into production with a much lower chance of configuration drift.