Appearance
List accessible Razuna workspaces ​
Team admins only. Public HTTPS URL defaults to https://app.razuna.com. Development also permits the matching r.n.lan, r.d.lan, or r.lan hostname derived from the configured Managani app URL. Production still rejects private hosts. Tokens are encrypted and masked. Blank or KEEP keeps the stored token unless the URL changes, which requires token entry. Save checks access and stores AI instructions. Workspace/folder/keyword fields are obsolete and are removed when saving. Disconnect does not remove Ghost images.
Request preparation ​
Send a POST request to /product/sites/{siteId}/integrations/razuna/workspaces on the appropriate server. Check the API overview for base URL guidance and the server information in the interactive reference. Replace path placeholders with identifiers from the intended account or site; a similarly named record in another workspace is not interchangeable.
The declared request parameters are:
siteId(path, required): Use the type and constraints shown in the parameter reference.
This operation defines an optional request body. Documented media types: application/json. Review required fields, nested objects, and allowed values in the request schema. Keep identifiers and field types intact when replacing example data with your own values.
Authentication and scope ​
The specification lists these security alternatives: BearerAuth, AccessToken. Read any operation-specific restrictions as well: browser-session, account-role, and signed-user requirements may impose additional conditions. See authentication before choosing a credential.
Keep credentials in the appropriate private configuration and remove secrets from shared logs. Confirm the target resource belongs to the intended workflow before issuing a request. Authentication alone should not be treated as confirmation that a supplied account, site, or customer identifier is correct.
Response handling ​
The documented responses for List accessible Razuna workspaces are:
- 200: Accessible workspaces: {workspaces: [{id, name}]}; no credentials returned
- 400: Invalid input, unavailable provider, or preparation failure; retry after resolving the error
- 401: Authentication required
- 403: Team admin access required for connection changes
Exercise this operation with controlled test data before enabling it in an automated workflow. Validate the request against the schema and inspect the response before updating local state. Do not assume that a successful response means background processing has finished; follow any documented status or follow-up operation when the action queues additional work.
If a connection fails after submission, investigate the current server state before repeating an action whose outcome is uncertain. When requesting support, retain the method, route, response status, and sanitized error message. The interactive reference below provides the detailed schemas and examples for this specific operation.
List accessible Razuna workspaces​
POST
/product/sites/{siteId}/integrations/razuna/workspaces
Team admins only. Public HTTPS URL defaults to https://app.razuna.com. Development also permits the matching r.n.lan, r.d.lan, or r.lan hostname derived from the configured Managani app URL. Production still rejects private hosts. Tokens are encrypted and masked. Blank or KEEP keeps the stored token unless the URL changes, which requires token entry. Save checks access and stores AI instructions. Workspace/folder/keyword fields are obsolete and are removed when saving. Disconnect does not remove Ghost images.
Authorizations​
BearerAuth
JWT token from login
Type
HTTP (bearer)
or
AccessToken
Personal access token. Value: Token <your-token>
Type
API Key (header: Authorization)
Parameters​
Path Parameters
siteId*
Type
Requiredstring
Request Body​
application/json
JSON"access_token": "string","url": "https://app.razuna.com","instructions": "string"
{
 Â
 Â
 Â
}
Responses​
Accessible workspaces: {workspaces: [{id, name}]}; no credentials returned