Claim a registry namespace
Claims a namespace for the project's organization, or renames it before anything is published; claiming the current namespace again changes nothing.
Only a person who is an organization admin can do this. A namespace has lowercase letters, digits and dashes, at most 39 characters, and core, project, voidhash and vh are reserved.
Guide: Publishing
A project secret key: vh_sk_... for production, vh_sk_test_... for test. Keep it on your servers.
In: header
Path parameters
The project's id, proj_.... A secret key works only in the project it belongs to.
Request body
application/json
TypeScript definitions
Use the request body type in TypeScript.
The namespace to claim: lowercase letters, digits and dashes, starting with a letter or digit, at most 39 characters. core, project, voidhash and vh are reserved.
Examples
curl -X PUT "https://api.voidhash.com/api/v1/projects/proj_tz4a98xxat96iws9zmbrgj3a/registry-publisher" \ -H "Authorization: Bearer vh_sk_..." \ -H "Content-Type: application/json" \ -d '{ "namespace": "acme" }'{ "id": "cmp_pub_r6t1y8u3i5o2p9a4s7d0f2g6", "organizationId": "org_w5xk2e7q0lzv3n8b1c4d6f9g", "namespace": "acme", "createdAt": "2026-03-05T10:00:00.000Z"}{ "error": { "type": "invalid_request", "code": "invalid_namespace", "message": "\"Acme\" is not a valid namespace: use lowercase letters, digits and dashes, starting with a letter or digit, at most 39 characters.", "param": "namespace" }}{ "error": { "type": "unauthenticated", "code": "invalid_api_key", "message": "This secret key is not valid." }}{ "error": { "type": "permission_denied", "code": "permission_denied", "message": "Insufficient permissions." }}{ "error": { "type": "not_found", "code": "project_not_found", "message": "There is no project proj_tz4a98xxat96iws9zmbrgj3a, or this credential cannot use it.", "param": "projectId" }}{ "error": { "type": "conflict", "code": "namespace_taken", "message": "The namespace cannot be claimed. \"acme\" is already taken.", "param": "namespace" }}{ "error": { "type": "internal", "code": "internal_error", "message": "Something went wrong on our side. Try again, and contact support with the Request-Id header if it keeps failing." }}Response body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
Errors
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request | invalid_namespace | For any other namespace. |
| 409 | conflict | namespace_taken | When another organization has the namespace. |
| 409 | conflict | namespace_in_use | When components are already published under the current one. |
It can also fail with the errors every operation shares, such as unauthenticated; see Errors.
More in Component registry
- Retrieve the registry publisher
GET - List registry components
GET - Publish a component bundle
POST - Publish a project component
POST - Retrieve a registry component
GET - Update a registry component
PATCH - List a registry component's versions
GET - Retrieve a registry component version
GET - Update a registry component version
PATCH - Retrieve a version's file
GET - Review an install
GET - List installed components
GET - Install a registry component
POST - Retrieve an install
GET - Update an install
PATCH - Uninstall a registry component
DELETE
Something wrong or missing on this page? Tell us by email or on Discord.