Communication APIs
What are the Communication APIs on upAPI?
upAPI’s Communication category has one public API: Translate Text. It is a single HTTP POST to api.upapi.io with an X-Api-Key header and returns JSON. It shares one API key and one pooled monthly quota with every other upAPI operation, so there is no separate signup or billing per provider.
1 production-grade communication API on upAPI. Every endpoint below is live behind the same gateway, takes the same API key, and returns JSON — no per-provider signup, no per-provider billing.
Calling a communication API
Every operation on this page is one POST away. Swap the slug, keep the key.
curl -X POST https://api.upapi.io/translate-text.get \
-H "X-Api-Key: $UPAPI_KEY" \
-H "Content-Type: application/json" \
-d '{}'Communication API questions
How do I call a Communication API?
Send an HTTP POST to api.upapi.io followed by the operation slug (for example api.upapi.io/translate-text.get), with your key in the X-Api-Key header and a JSON body. Any HTTP client works the same way: curl, requests in Python or fetch in JavaScript. Each operation’s page lists its input fields, its output fields and a runnable example.
How much do the Communication APIs cost?
Every Communication operation costs 1 weighted unit per call. Every unit draws from one pooled monthly quota shared across the whole catalog. See upapi.io/pricing for what a unit costs on each plan.
Is there a free tier for the Communication APIs?
Yes. The Free plan costs nothing and includes 1,000 weighted units a month across every public operation, so you can try these on real inputs before choosing a paid plan.