When to Use This Endpoint
Upload debug symbols after uploading your binary image when:- You have .pdb files available from your build process
- You want more accurate vulnerability detection
- You need better source code correlation in findings
Tip: Debug symbols significantly improve analysis accuracy. Always upload them when available.
Request
Endpoint| Parameter | Description |
|---|---|
product_id | The product ID (e.g., prod_abc123) |
image_id | The image ID from the upload response (e.g., img_abc123) |
| Header | Value |
|---|---|
Authorization | Bearer <access_token> |
Content-Type | multipart/form-data |
| Field | Required | Description |
|---|---|---|
file | ✅ | The debug symbol file (.pdb) |
Example Request - Single File
Example Request - Batch Upload
If you have multiple .pdb files, upload them in a loop:Response
Returns the created file object with upload confirmation.| Field | Description |
|---|---|
id | Unique file identifier (ULID format) |
filename | The uploaded file name |
createTime | Timestamp when file was uploaded |
Best Practices
| Practice | Description |
|---|---|
| Upload after firmware | Always upload debug symbols after the firmware image |
| Include all symbols | Upload all available .pdb files from your build |
| Automate in CI/CD | Integrate symbol upload into your build pipeline |
| Keep symbols secure | Debug symbols contain sensitive information - transfer via HTTPS only |
Related
User Guides- Debugging Symbols Guide - UI walkthrough for uploading and verifying PDB files