Update namespace
Change a namespace’s display label.
/namespaces/{namespace}PermissionCluster key. Key scopes and actions.
- The name and ID are immutable. Send display_name: null to clear the label.
Path parameters
Namespace name or ns_ ID. It must be visible to this key.
Request body
New display label, or null to clear it. The namespace name remains unchanged.
Responses
200Success
The namespace with its updated display label.
application/json
Response headers
The Engine request ID. Retain it when investigating a failed or unexpected request.
The X-Request-Id you sent, echoed when it is a valid ID. Otherwise, the Engine request ID.
Time the resource was created, as an ISO 8601 UTC timestamp.
Human-readable label. This label does not change the resource name used in URLs.
Immutable namespace ID with the ns_ prefix.
URL name. Use 1–63 lowercase letters, digits, underscores, or hyphens. Start with a letter or digit. A name cannot match its resource ID format.
Time the resource last changed, as an ISO 8601 UTC timestamp.
Current resource counts and storage usage. These are measurements, not tenant plan quotas.
Errors
Select an error in the response example to see its JSON body. See error handling for the common error format.
- 400invalid_request
A field, path, parameter, or conditional request rule is invalid.
What to do: Correct the request. Unknown fields are rejected.
- 401unauthenticated
The API key is missing, invalid, or revoked.
What to do: Send an active key in Authorization: Bearer or X-API-Key.
- 403forbidden
The key can see the resource but lacks permission for this operation.
What to do: Use a key with the required action or scope kind.
- 404not_found
The resource is absent, deleted, or outside this key’s scope.
What to do: Check the identifier and the key’s namespace and collection scope.
- 413request_too_large
The JSON body exceeds the route limit: 6,291,456 bytes on :answer and research, 4,194,304 bytes on :search and :read-spans, and 1,048,576 bytes elsewhere.
What to do: Reduce the JSON body. Use upload or a URI source for larger file content.
- 500internal_error
An unexpected server failure prevented this request from completing.
What to do: Retain request_id for investigation. Follow retryable before retrying a write.