Programmatic access to alltools.one features. Manage snippets, share data, and track history via REST API.
https://api.alltools.onePull your team's saved JSON / YAML / CSV formatter configs in GitHub Actions or GitLab CI to keep builds consistent.
# .github/workflows/validate.yml
- name: Fetch saved formatter config
run: |
curl -sf "https://api.alltools.one/api/snippets?tool=json-formatter&limit=1" \
-H "X-API-Key: ${{ secrets.ALLTOOLS_API_KEY }}" | jq '.snippets[0].data'When your automation workflow produces a formatted CSV or JSON, POST it directly as a named snippet for later retrieval.
curl -X POST https://api.alltools.one/api/snippets \
-H "X-API-Key: ato_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"tool": "csv-formatter",
"title": "Daily Report 2025-01-15",
"data": { "csv": "name,value\nAlice,42\nBob,99" },
"tags": ["automated", "daily"]
}'Create a shareable link for any formatted output — useful for embedding live data previews in Notion, Slack, or documentation.
curl -X POST https://api.alltools.one/api/shares \
-H "X-API-Key: ato_your_key_here" \
-H "Content-Type: application/json" \
-d '{
"tool": "json-formatter",
"title": "API Response Sample",
"data": { "input": "{\"status\":\"ok\",\"result\":42}" }
}'
# Returns: { "share_url": "https://alltools.one/share/abc123def4", "id": "abc123def4" }Most endpoints require authentication via a Firebase JWT token or an API key.
Obtain a token via Firebase Auth, then include it in the Authorization header:
curl https://api.alltools.one/api/auth/profile \
-H "Authorization: Bearer <firebase_id_token>"Pro users can create API keys from the dashboard. Include the key in the X-API-Key header:
curl https://api.alltools.one/api/snippets \
-H "X-API-Key: ato_your_key_here"Save and manage tool outputs. Free users can store up to 5 snippets; Pro users get unlimited storage.
Create shareable links for tool data. Free shares are permanent (5MB max). Pro shares support up to 50MB.
Track tool usage. Free users: last 20 entries. Pro users: unlimited history.
Manage programmatic API keys. Requires Pro plan. Maximum 5 keys per user.
Manage Pro subscriptions via Razorpay integration.
| Code | Meaning | Common Cause |
|---|---|---|
200 | OK | Request succeeded |
201 | Created | Resource created |
400 | Bad Request | Validation error or malformed input |
401 | Unauthorized | Missing or invalid auth token |
403 | Forbidden | Pro plan required or not the resource owner |
404 | Not Found | Resource does not exist |
409 | Conflict | Duplicate resource (e.g. email already subscribed) |
410 | Gone | Share link has expired |
413 | Payload Too Large | Data exceeds size limit (5MB free / 50MB pro) |
429 | Too Many Requests | Rate limit exceeded |
Available on the Pro plan. Requests are tracked per API key.
5 requests per 60 seconds per IP address.
| Feature | Free | Pro |
|---|---|---|
| Saved snippets | 15 | Unlimited |
| History entries | 20 | Unlimited |
| Share max size | 5 MB | 50 MB |
| Share expiry | Never | Never |
| API requests | — | Unlimited (fair use) |
| API keys | 0 | 5 |