Minidump Request

POST /minidump?timeout=5&scope=123 HTTP/1.1
Content-Type: multipart/form-data; boundary=xxx

--xxx
Content-Disposition: form-data; name="upload_file_minidump"
[binary blob]

--xxx
Content-Disposition: form-data; name="sources"
[
  {
    "id": "<uuid>",
    "type": "http",
    ... // see "Sources"
  },
  ...
]

--xxx
Content-Disposition: form-data; name="platform"
"native"

--xxx
Content-Disposition: form-data; name="rewrite_first_module"
[
  {"from": "[^/\\\\]+ (?<suffix>Framework|Helper( \\(.+\\))?)$", "to": "Electron $suffix"},
  {"from": "[^/\\\\]+\\.exe\\.pdb$", "to": "electron.exe.pdb"},
  {"from": "[^/\\\\]+$", "to": "electron"}
]
--xxx--

Query Parameters

• timeout: If given, a response status of pending might be sent by the server.
• scope: An optional scope which will be used to isolate cached files from each other

Request Body

A multipart form data body containing the minidump, as well as the external sources to pull symbols from.

• platform: The event' platform.
• sources: A list of descriptors for internal or external symbol sources. See Sources.
• upload_file_minidump: The minidump file to be analyzed.
• rewrite_first_module: Rewriting rules for rewriting the debug file name of the first (by address) module in the minidump. This is used because that debug file may be found on a symbol source under another name.

Response

See Symbolication Response.