> ## Documentation Index
> Fetch the complete documentation index at: https://docs.squasher.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Source Maps API

> List, upload, and delete source maps for JavaScript stack trace symbolication.

Use the Source Maps API when releases need source maps uploaded for readable stack traces.

## Operations

| Operation           | Method and path                                              | Purpose                                                                  |
| ------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------ |
| `sourcemaps.list`   | `GET /v1/projects/{project_id}/sourcemaps`                   | List uploaded source maps, optionally filtered by service and release.   |
| `sourcemaps.upload` | `POST /v1/projects/{project_id}/sourcemaps`                  | Upload source map files for a service release using multipart form data. |
| `sourcemaps.delete` | `DELETE /v1/projects/{project_id}/sourcemaps/{sourcemap_id}` | Delete a source map by id.                                               |

Uploads should include the release value used by the SDK. Keep release names stable between SDK event capture and upload.

## CLI and MCP

Use `squasher sourcemaps list`, `squasher sourcemaps upload --service <service>`, or `squasher sourcemaps delete`. Hosted MCP may expose read/delete metadata but uploads are usually API or CLI workflows because they require files.

## Agent handoff

```text theme={null}
Check Squasher source maps for project <project_id> and release <release>. List current uploads, compare the release to SDK config, and ask before uploading or deleting source maps.
```

Related: [Source maps SDK guide](/sdks/source-maps).