Organization
Update Organization
Updates the organization from your authenticated session.
PATCH /api/organization
Request Body
{
"name": "New Name",
"companyName": "New Company Name",
"street": "New Street",
"postalCode": "54321",
"city": "New City",
"country": "US",
"vatId": "US123",
"billingEmail": "new@example.com",
"defaultNotificationChannels": {
"email": true,
"sms": false,
"webhook": true,
"integrations": false
},
"defaultNotificationTargets": {
"email": "both", // customer, organization, both
"sms": "organization",
"webhook": "organization",
"integrations": "customer"
}
}Example (cURL)
BASE_URL="https://uptimeify.io"
TOKEN="<your-api-token>"
curl -X PATCH "$BASE_URL/api/organization" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{
"name": "New Name",
"billingEmail": "new@example.com"
}'Notes:
- The organization is derived automatically from your authenticated session or API token.
- The legacy route
PATCH /api/organizations/:organizationPublicIdremains supported for compatibility. - The plural org-less alias
PATCH /api/organizationsis also supported. - Global admins need an active organization context in the authenticated session for the org-less route.
Common errors
400 Invalid request bodywhen the payload does not match the schema400 Organization ID is required in the authenticated sessionwhen no organization can be derived from the current session/token401 Unauthorizedwhen you are not logged in403 Forbiddenwhen you do not have admin access to update the organization
Response
Returns the updated organization object. See Error Codes for error responses.
Update Billing Details
Updates billing information for the organization in your authenticated session.
Upsert Package Config
Creates a new package config (by :packageType) or updates an existing one. packageType is a free-form identifier chosen by the organization, and customer endpoints can later reference that same key.