Organization management API¶
An organization groups cameras, folders and users. An external account management system can create organizations for enterprise sites and manage user access to their cameras. All examples use Client API v3 and Bearer authentication.
Creating and deleting organizations requires permission to manage organizations in the domain. An owner can also rename their own organization. Changing limits or the owner requires domain permissions; ownership alone is insufficient.
List organizations¶
GET /watcher/client-api/v3/organizations?limit=100
Authorization: Bearer <token>
The response contains the organizations array and pagination fields next, prev and estimated_count. To fetch the next page, pass next as cursor, retaining the other filters. Only organizations accessible to the caller are returned.
Create an organization¶
Domains without a creation date, or created before January 16, 2026, 08:30:29.622 UTC, have an additional requirement: outside the main domain, creating or administratively changing an organization is allowed for the login billing or a login ending in _master. Account for this when choosing a service account.
This example creates an organization with an existing user as owner: replace 15 with that user's Watcher ID. If owner.id is omitted, the creator becomes the owner.
POST /watcher/client-api/v3/organizations
Authorization: Bearer <token>
Content-Type: application/json
{
"title": "Garden Street building",
"owner": {"id": 15},
"limits": {"streams": 24, "users": 50}
}
Save the created organization's id from the response. Watcher also creates the root folder Cameras. In the following independent read, update and delete examples, replace 7 with the target organization's ID; 16 in the ownership change example is the new owner's ID.
Limits are nested in limits:
- streams — maximum number of cameras in the organization; the schema default is
5000. - users — maximum number of users; the schema default is
2000.
Archive settings come from the preset and camera settings. Legacy fields camera_limit, user_limit and dvr_limit are not used in the v3 example.
Get organization details¶
GET /watcher/client-api/v3/organizations/7
Authorization: Bearer <token>
The response provides organization settings and statistics. user_permissions describes the caller's permissions in this organization. It helps determine available actions, but the corresponding write request performs the final check.
Update an organization¶
PUT /watcher/client-api/v3/organizations/7
Authorization: Bearer <token>
Content-Type: application/json
{"title": "Garden Street, building 2", "limits": {"streams": 32, "users": 50}}
Send the fields you want to change. To change the owner, send {"owner":{"id":16}}. Watcher removes the owner flag from previous members and assigns the new owner; if the new owner is not yet a member, membership is created.
An organization owner without domain organization management permission can change the title. Use an account with domain permissions to change limits or ownership.
Delete an organization¶
DELETE /watcher/client-api/v3/organizations/7
Authorization: Bearer <token>
X-Force: true
Without X-Force, Watcher rejects deletion of an organization with dependent objects. The root folder is also a dependent object. X-Force permits cascading deletion of the organization and its objects. User accounts belonging only to that organization are also deleted. Check the organization's contents and the ID in the URL first. The domain's default organization cannot be deleted. A successful response is 204.
Removing a member from an organization is described in the user API. It preserves the account itself.