Custom HTTP Uploader

Wire up any HTTP API as an upload destination using a simple JSON config.

Config Format

{
  "name":         "My Server",
  "url":          "https://example.com/upload",
  "method":       "POST",
  "fileField":    "file",
  "headers": {
    "Authorization": "Bearer YOUR_TOKEN"
  },
  "responsePath": "$.url"
}
name Display name — shown in the Settings dropdown.
url The full endpoint URL that accepts the upload.
method "POST" or "PUT" — depends on your API.
fileField The multipart form field name your server expects for the image file.
headers Any request headers — auth tokens, content type overrides, etc.
responsePath A dot-path into the JSON response to extract the public URL. $ refers to the root.

Response Path Examples

Direct string response
"https://cdn.example.com/img/abc123.png"
responsePath: $
Nested URL field
{ "data": { "url": "https://..." } }
responsePath: $.data.url
Array of links
{ "links": ["https://..."] }
responsePath: $.links[0]

Adding a Custom Uploader

  1. 1. Create a .json file with the config above.
  2. 2. Open Settings → Uploads → Custom HTTP → Import Config.
  3. 3. Select your JSON file.
  4. 4. Reticle validates the config and adds it to the destination list.
  5. 5. Set it as your active destination and enable Upload in After Capture.

ShareX Uploader Compatibility

Reticle's custom uploader format is inspired by ShareX's SXCU format. Many ShareX custom uploader configs can be used in Reticle with minor adjustments. The main difference: Reticle uses responsePath instead of ShareX's URL field.