API documentation

Every payloadly tool is available as a REST endpoint. The interface is deliberately boring: POST your document as plain text, get the converted document back as plain text. Errors come back as JSON with a descriptive message. Call it from your own code, or drop it into a no-code automation as an HTTP step (see below).

Authentication

Anonymous requests get 25 calls per day. With an API key (issued instantly when you subscribe), requests are unlimited. Pass the key in the X-Api-Key header.

Convert a document

curl -X POST https://payloadly.com/api/v1/tools/json-to-csv \
  -H "Content-Type: text/plain" \
  -H "X-Api-Key: pl_live_..." \
  --data-binary @data.json

Tools that take an option (for example the CSV column extractor, or the JSON formatter's indent) accept it as a query parameter:

curl -X POST "https://payloadly.com/api/v1/tools/csv-column-extractor?option=name,level" \
  -H "Content-Type: text/plain" \
  --data-binary @data.csv

Use it in a no-code automation

Because every tool is a plain HTTP endpoint, you can call it from Zapier, Make, n8n, or any workflow tool that has an HTTP request step, no code required. Configure the step like this:

  • Method: POST
  • URL: https://payloadly.com/api/v1/tools/<tool-slug> (for example json-to-csv; every slug is in the table below)
  • Header: X-Api-Key: your_key
  • Header: Content-Type: text/plain
  • Body: the document to convert as raw text, or map a field from a previous step

The response body is the converted document, ready to map straight into the next step of your workflow. If you send an option, add it to the URL as a ?option= query parameter.

Responses

  • 200: converted document, plain text, correct MIME type.
  • 422: input could not be parsed; JSON body explains why, with line numbers where available.
  • 429: anonymous daily limit reached.
  • 401: invalid or deactivated API key.
  • 413: body over 4 MB.

Endpoints