How it works
Resources can be assigned to a project in two ways:- At creation time — include
project_idin the request body of any create endpoint for jobs, event monitors, datasets, or webhooks. - Post-hoc — use the Add resources endpoint to assign one or more existing resources by type and ID.
resource_type values are job, monitor, dataset, monitor_group,
and webhook.
Most resources belong to at most one project. Webhooks are the exception: the
same webhook can be attached to several projects at once, since one endpoint
often serves multiple workstreams. Entities cannot be assigned to projects —
they are shared across the entire organization.
Create a project
Assign resources
Passproject_id in the request body at creation time:
cURL
project_id on creation in the same way:
cURL
project_id does not exist, the request fails with 404. If it belongs
to another organization, it fails with 403; in both cases the webhook is not
created.
To add an existing resource post-hoc:
cURL
Filter by project
All list endpoints accept aproject_id query parameter to return only
resources belonging to a specific project:
- Jobs
- Event Monitors
- Datasets
- Webhooks
Get a project overview
Returns resource counts grouped by type and status — useful for dashboards without fetching full resource lists:cURL
jobs and monitors, keys are status values with integer counts. For
datasets, monitor_groups, and webhooks, only a total count is returned.
Delete a project
By default, deleting a project unassigns its resources — they continue to exist without a project association. Setdelete_resources=true to permanently delete
all assigned resources along with the project.
Webhooks are never deleted by either option. An attached webhook is only
detached from the project and keeps delivering, because the same webhook may
still be attached to other projects. To remove a webhook itself, call
Delete webhook.
- Unassign resources (default)
- Delete project and resources

