If you’re building a headless WordPress site — React, Next.js, Nuxt, SvelteKit, Astro, or any other JavaScript frontend — you need to fetch translated content from WordPress over HTTP. Lang Forge exposes a full REST API with 12 endpoints so you can.
All endpoints live under /wp-json/langforge/v1/ and follow standard WordPress REST API conventions — HTTP methods, status codes, and authentication via WordPress’s existing auth mechanisms (cookies for logged-in users, application passwords for API keys, OAuth for third-party apps).
GET /languages — list all configured languages on the siteGET /languages/current — return the current language based on request contextGET /translations/<post_id> — list all translations of a given postGET /translations/<post_id>/<lang> — get the translated version of a post in a specific languagePOST /translations/<post_id>/<lang> — create a new translationPUT /translations/<post_id>/<lang> — update an existing translationGET /strings — list all registered translatable strings with filters (domain, status, language)GET /strings/<id> — fetch a single string with its translationsPUT /strings/<id> — update a translation for a stringGET /tm/search — search the translation memory by source text (exact or fuzzy match)POST /tm/entry — add a new entry to the translation memoryGET /glossary — list glossary termsThe REST API uses WordPress’s native authentication. For headless frontends, the recommended approach is application passwords (a built-in WordPress feature since 5.6) or JWT via a third-party plugin. Lang Forge doesn’t introduce its own auth layer — it respects whatever you already have.
Read-only endpoints (language list, published translations, glossary) are public by default and don’t require authentication. Write endpoints require the appropriate capability (edit_posts for translations, manage_options for language config).
Fetch translated content into a React or Next.js frontend. Lang Forge returns the same shape as the WordPress core REST API, with additional language metadata on every post.
Consume translated content in a native mobile app via the REST API. Users see the app in their preferred language, served by WordPress on the backend.
A Zapier, Make, or n8n workflow that fetches a translated post on demand — for sending out newsletters, syndicating to social media, or piping content into a separate CMS.
Build an admin dashboard in Retool, Budibase, or your own tool that talks to Lang Forge directly. Useful for agencies managing multilingual content across dozens of client sites.
Nightly build pipelines that fetch the latest translations and rebuild a static site.
Lang Forge’s REST endpoints respect standard WordPress rate limiting. Response bodies are cache-friendly (proper ETags, Last-Modified headers) so you can put a CDN in front of read endpoints without any special configuration.
Full endpoint documentation, with request/response examples and authentication walkthroughs, lives in our documentation →.
Get Lang Forge — from $54/year →
The REST API is included in every paid plan and in the free version on WordPress.org.
We use analytics and marketing cookies (Google Analytics, Google Ads, Meta) to understand traffic and improve the site. Strictly-necessary cookies are always on. See our Privacy Policy.