REST API
Combined route and backend behavior reference for Symbol Management.
These are the routes used by the Symbol Management module.
- Folders: left-panel library grouping.
- Symbols: main-panel library records.
- Base URL: current frontend default is `http://localhost:5203/api`.
- Auth header: include `x-api-key: CLIENT_API_KEY` on folder and symbol requests.
Protected Symbol Management routes require a valid client API key before folder and symbol requests will succeed.
- Required setup: complete API Key Management Overview before integrating protected Symbol Management requests.
Folders use name-based payloads. Symbols use name, MIME type, serialized `data`, and optional folder reassignment.
Protected deployments expect `x-api-key` in the request headers, even for read operations.
Handle these backend behaviors explicitly in the client.
- 404 Not Found: missing folder or symbol record.
- 409 Conflict: duplicate folder name.
- 400 Bad Request: validation failure.
- 401/403: missing or invalid client API key when route protection is enabled.
- Unique folder names: the backend should reject duplicates.
- Auth requirement: current client integrations send `x-api-key` on all Symbol Management routes.
This module belongs in your backend service layer and client application logic, not in the viewer postMessage contract.
A common flow is to load folders first, load symbols when a folder ID is available, and refresh the affected collection after every successful mutation.
This example shows one client-side integration pattern using React state and effects.
React Page Types
Load Folders
Load Symbols For Selected Folder
React Effects
Page Skeleton
