Symbols
Upload payloads and symbol record contracts for the Symbol Management module.
Use these routes to manage symbol records within a folder.
- List by folder: load all symbol records for a folder ID.
- Create: add a new symbol under the active folder.
- Get by ID: open detailed symbol information.
- Patch: update metadata, content, or move the symbol to another folder.
- Delete: remove the symbol record.
- Auth header: include `x-api-key` on every symbols request. If you need to issue or manage that client key, see API Key Management Overview.
The module stores uploaded file information inside the `data` field as a JSON string containing file metadata and base64 content.
For readability, document the inner `data` object separately and then show the final payload using `JSON.stringify(...)`.
Serialized Data Structure
Create Symbol Payload
Update Symbol Payload
The user selects a file from the computer, the frontend reads it, extracts base64 content, measures the image dimensions, and serializes that data into the `data` string.
Use the file name without extension for the symbol `name`, and use the uploaded MIME type for `type`.
- Preview source: a client can generate a local data URL before save if preview support is needed.
- Stored contract: the backend receives the serialized JSON string, not the raw data URL.
- Protected uploads: the same `x-api-key` header is required for list, create, update, and delete requests.
- Folder refresh: after create, update, move, or delete, reload the active folder symbols list.
These examples show request functions you can call from a client application after a file is prepared for upload.
Shared Types
Get Symbols
Create Symbol
Update Symbol
Delete Symbol
