Update the organization profile
PATCH/api/v1/orgs/:org
Updates the organization's name, URL slug and/or logo. Owner only — an admin is refused with 403 FORBIDDEN. Standard PATCH semantics: an omitted field is left untouched, and logoUrl accepts null (or an empty string) to clear the logo.
Renaming the slug moves every URL of the organization, including the public ones — status pages, SVG badges and the embed widget. Existing links keep working: the previous slug is remembered and answers a permanent redirect (301 for GET/HEAD, 308 otherwise) to the current slug. Every /api/v1/orgs/{org}/... route is covered except the realtime WebSocket (/api/v1/orgs/{org}/events/ws), where an HTTP redirect is meaningless — reconnect against the current slug. That guarantee ends as soon as another organization claims the freed slug.
Because access tokens are scoped to an organization slug, a rename response also carries a freshly minted session (accessToken, refreshToken, expiresIn, tokenType) for the new slug; the caller must adopt it or every subsequent request will be refused with 403. Other live sessions self-heal on their next token refresh.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 422
Updated organization profile
Authentication required
Permission denied
Resource not found
The requested slug is already taken by a live organization
Validation error