TextForge
28 text transformations in one API call
7 followers
28 text transformations in one API call
7 followers
TextForge exposes 28 deterministic text transformations behind a single HTTPS API: slugify, camelCase, base64, email extraction, and batch processing with predictable JSON.
How does the batch endpoint handle rate limits when I push a few thousand payloads through it, and is there a synchronous mode if I need results back in the same call?
Rate limits: /batch uses the same limiter as /v1/run. Each batch request = 1 request toward your daily/minute quota (Free: 1K/day, 60/min; Pro: 50K/day, 1K/min). The 100 items inside don't multiply the count.
For a few thousand payloads: Chunk into multiple batch requests (max 100 items each). 1,000 items = 10 batch calls = 10 rate-limit hits. Free tier handles this fine.
Synchronous? Yes — processes all items via Promise.all and returns all results in the same HTTP response. No polling needed.
Limits: 100 items/request, 100KB/item. Order preserved via index.
Webhook: Optional, fire-and-forget. If provided, receives results asynchronously; response returns immediately regardless.
Endpoint: POST /v1/batch — { "action": "slugify", "items": ["hello world", "foo bar"], "webhook": "https://..." }
Hit the slugify endpoint a few times and the results were identical every run, which is exactly what I want from a text API. The batch endpoint handled a mixed list of strings cleanly in one call.
Slugs came back identical across two runs, which is exactly what I needed for a flaky build script. The batch endpoint saved me from looping through 200 lines of copy myself.