Workspace
Get current workspace
Returns the workspace associated with the X-Api-Key request header. Workspace IDs do not need to be sent in request bodies. is_beta is a read-only workspace flag, disabled by default. Contact the platform to enable access; neither PATCH nor metadata can change it.
https://api.unifyport.ai/v1/workspaceSupported channels
Before you call
Use a server-side X-Api-Key for the workspace that owns the resource. Replace every placeholder before running a sample.
Request parameters
Headers
X-Api-KeyWorkspace API key. The workspace is resolved from this header.
Request body
This endpoint does not require a JSON request body.
Understand the result
Read the documented response fields and HTTP status, then follow the related operations for your next step.
Response 200 OK
{
"request_id": "<REQUEST_ID>",
"data": {
"name": "Production Workspace",
"status": "active",
"metadata": {
"env": "production"
},
"account_quota": 10,
"account_quota_used": 1,
"account_quota_unlimited": false,
"is_beta": false
}
}
Response body
is_betais_beta is a read-only workspace flag, disabled by default. Contact the platform to enable access; neither PATCH nor metadata can change it.
nameWorkspace display name.
statusWorkspace status: active or inactive. Inactive workspaces reject authentication by all of their API keys.
enum: active, inactive
metadataYour own environment labels stored on the workspace.
account_quotaCurrent effective read-only account capacity, including the free quota and paid quota that is still valid, without subtracting used accounts; expired paid quota is not counted.
format: uint64
account_quota_usedRead-only account quota currently in use. Creating an account consumes quota; deleting it releases quota. Accounts awaiting authorization, stopped, or disconnected still count. After paid quota expires, usage may exceed account_quota; the actual usage is returned.
format: uint64
account_quota_unlimitedCompatibility read-only field; the current quota mode always returns false. Use account_quota as the account capacity.
Responses
200200 OK
Request succeeded. See the example response body.
401Unauthorized
The X-Api-Key header is missing or invalid.
500Internal Server Error
The service encountered an unexpected error.
If the request fails
Inspect HTTP status and error.code/numeric_code, and keep request_id for diagnosis. Correct invalid parameters, complete required authorization or check runtime state as appropriate. Confirm the outcome before retrying a send or another write. Error reference
- missing_api_key · 11000 · 401
- Check X-Api-Key and whether the workspace is active.
- invalid_api_key · 11001 · 401
- Check X-Api-Key and whether the workspace is active.