Use HandyTechHelper from your own code.

Quick start

1. Get Pro or Pro Max. The API is included with both.
2. In your account’s Developer section, create an API key and copy it. It is shown only once.
3. Call the API:

curl https://handytechhelper.com/api/v1/transform \
  -H "Authorization: Bearer $HTH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jobs":[{"operation":"json-format","input":"{\"hello\":\"world\"}"}]}'

The response contains one output string per job, in the same order, plus the credits the request used:

{"results":["{\n  \"hello\": \"world\"\n}"],"creditsUsed":1}

Field names in the response may gain additions over time; ignore fields you don’t use.

JavaScript

const response = await fetch('https://handytechhelper.com/api/v1/transform', {
  method: 'POST',
  headers: {Authorization: `Bearer ${process.env.HTH_API_KEY}`, 'Content-Type': 'application/json'},
  body: JSON.stringify({jobs: [{operation: 'sha256', input: 'Hope This Helps.'}]}),
});
if (!response.ok) throw new Error((await response.json()).error);
console.log(await response.json());

Python

import os, requests
r = requests.post("https://handytechhelper.com/api/v1/transform",
    headers={"Authorization": f"Bearer {os.environ['HTH_API_KEY']}"},
    json={"jobs": [{"operation": "text-upper", "input": "hello"}]}, timeout=10)
r.raise_for_status()
print(r.json())

Keys and scopes

Send your key in the Authorization header as Bearer hth_… on every request. Keys are stored only as hashes, so we can’t show a key again after you create it. Never put a key in browser code or a public repository. If a key leaks, revoke it in your account straight away.

Scopes

Each key has one or more scopes, chosen when you create it. Give each app only what it needs.

Rotation and expiry

Keys expire after 90 days. Click Rotate next to a key to get a replacement with the same name and scopes. The old key keeps working for 24 hours, so you can update your apps without downtime. Each key shows its request count and when it was last used. You can have up to 5 keys, plus retiring keys during a rotation (10 active at most).

Endpoints

Operations

Each operation uses one credit. Inputs are plain text up to 8 KiB each and 64 KiB per request.

Plans and limits

Credits reset at the start of each billing period and don’t roll over. The site administrator may set lower temporary ceilings to protect the shared server; the effective limits are always reported by /api/v1/entitlements.

Errors

Errors return a JSON body like {"error":"A valid API key is required."} with one of these status codes: