REST API — 12 Endpoints for Headless Multilingual WordPress
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.
The endpoints
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).
Languages
GET /languages— list all configured languages on the siteGET /languages/current— return the current language based on request context
Translations
GET /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 translation
Strings
GET /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 string
Translation memory
GET /tm/search— search the translation memory by source text (exact or fuzzy match)POST /tm/entry— add a new entry to the translation memory
Glossary
GET /glossary— list glossary terms
Authentication
The 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).
Use cases
Headless WordPress sites
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.
Mobile apps
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.
Third-party integrations
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.
Custom admin tools
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.
CI/CD automation
Nightly build pipelines that fetch the latest translations and rebuild a static site.
Rate limiting and caching
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.
Documentation and examples
Full endpoint documentation, with request/response examples and authentication walkthroughs, lives in our documentation →.
Ready to build a headless multilingual site?
The REST API is included in every paid plan and in the free version on WordPress.org.