Replace a tenant specialty's data in full
PUT/tenant-specialties/:id
Replaces the stored data for an existing tenant specialty. This is a full-replacement operation — fields not included in the request body are cleared, not preserved.
What it does: Overwrites the tenant specialty identified by {id} with the supplied payload. The data layer performs a replace, not a merge, so callers must supply all fields they wish to retain.
When to use: Use this to update any attribute of a tenant specialty after it has been created.
How to call it: Supply the required tenant-id header and the tenant specialty id as a path segment (an opaque, server-assigned string). The request body is validated against the TenantSpecialty JSON Schema on the data field; validation failures return 400. The same request schema is used as for POST. Requires the UPDATE_TENANT_SPECIALTY permission. Returns 404 if no specialty with the given id exists for the supplied tenant-id — the record is looked up before any write is attempted.
What you get back: On success (200) the full updated tenant specialty object is returned. This operation is idempotent — sending the same payload twice produces the same state.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
The full tenant specialty object after replacement.
Missing tenant-id header, or data failing TenantSpecialty JSON Schema validation.
Unauthorized - the request is missing a valid JWT.
Forbidden - the caller lacks the UPDATE_TENANT_SPECIALTY permission for this tenant.
No tenant specialty exists with the given id for the supplied tenant-id.
Internal Server Error - an unexpected error occurred while replacing the record.