Pixmello DevelopersBeta
DOCUMENTATION / GET STARTED

Your first API request.

A verified account, one API key and an HTTP request. Here is the complete path from signup to a working integration.

01

Create your API key

Create an account, verify your email using the latest code, and open API keys & usage. Name the key after its integration, such as “Invoice workflow”.

Create API key →
Copy it once. Keep it private.

The full key is shown only when created. Save it in your server environment or workflow credentials. Never place it in public browser code, a URL or a shared workflow export.

Keys expire after 90 days. You can have up to five active keys. Rotation immediately revokes the previous key. All keys on your account share the same quotas.

02

Make your first request

Set PIXMELLO_API_KEY privately in your terminal or server environment. Choose an example below. This request calculates the SHA-256 hash of hello.

POSThttps://pixmello-web-api.onrender.com/api/v1/execute
curl https://pixmello-web-api.onrender.com/api/v1/execute \
  -H "Authorization: Bearer $PIXMELLO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tool":"sha256-hash","input":"hello"}'

Change tool, input and optional options to call another operation. Find the exact input contract →

03

Use the result

Successful requests return a request ID, operation ID and result. Read result.text for this example. Keep the request ID for troubleshooting.

{
  "requestId": "<request UUID>",
  "tool": "sha256-hash",
  "result": {
    "kind": "text",
    "text": "2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824",
    "mime": "text/plain",
    "filename": "sha256.txt"
  }
}

This illustrates the response shape. File operations return Base64 in result.data, with MIME, filename and decoded byte count. Decode those bytes before saving. Response and error reference →

Connect your workflow

  1. In n8n, add an HTTP Request node. Select POST and use the endpoint above.
  2. Select Generic Credential Type → Header Auth. Set name to Authorization and value to Bearer YOUR_KEY. Store the real key in the private credential.
  3. Send JSON: {"tool":"sha256-hash","input":"hello"}. Set an explicit timeout.
  4. Read result.text, or decode result.data for files.

Make and Zapier can use generic HTTP modules with the same contract. A local n8n runner has been tested against the hosted API; custom connectors and cloud-provider-specific flows are separate integrations.

Download example n8n workflow →

After importing, configure the hosted API URL, private Header Auth credential and output path. The export contains no API key.

Know the limits before building

10 / minute100 / day · 1,000 / month per account
1 MiB filesCombined decoded input; binary output also limited to 1 MiB

Quota windows use UTC. A shared platform budget of 300 requests/day and 10,000/month also applies. Admitted attempts count even if processing fails. Respect quota resets and Retry-After; requests are not idempotent.

Use JSON with padded Base64 for files, not multipart uploads. This API supports synchronous operations. Free hosting can cold-start, and concurrency is bounded. Full limits and error handling →

Using tools directly in your browser?

The website has additional tools with different limits. A website tool is not automatically available over this API. The API reference lists supported operations.

For processing inside your own browser app, explore the separate local JavaScript SDK and its operation reference.