Projects and Collections
APIContext organises your monitoring work into two levels: Projects and Collections.
Projects
A Project is the primary unit of work. Everything you create in APIContext lives inside a project:
- Monitors (API endpoints you run on a schedule)
- Authentications (OAuth tokens, API keys, certificates)
- Workflows (chains of monitors run in sequence)
- Schedules and downtime windows
- Conformance and SLO settings
Projects have their own billing subscription, quota, and CASC Quality Score.
Collections
A Collection is a group of projects. In the current model, each user account has one Collection that holds all their projects.
For Enterprise accounts, a Collection maps 1:1 to an Organisation. If you are an Enterprise customer, your admin may manage multiple users and billing across the whole Collection. The UI may show "Organisation" where this documentation says "Collection" — they refer to the same thing in the current tier structure.
This page will be updated if a future tier introduces sub-Collections or independent Collection management.
Access and roles
Project membership controls who can view and edit monitors within a project. See Access Roles for the full permission matrix.
Creating a project
See Create a new project for step-by-step instructions.