Connect Ghost
Import the titles and text of your Ghost posts and pages into transglot for translation.
Import only
Nothing is written back to Ghost. A Ghost post is single-language and has no per-language slot to write into. Take the translations out through the REST API, the transglot CLI or the CDN.
| Direction | Import only |
| Imported | The title and plaintext of posts and pages |
| Written back | Nothing |
| Sync | Sync from CMS |
| Plan | Starter and above |
Before you start
In Ghost admin, add a custom integration in the integration settings and copy its Admin API key. It has the form {key-id}:{hex-secret}.
Connect
Open your project's settings, choose CMS, and pick Ghost in the CMS list.
| Field | What to enter |
|---|---|
| Ghost site URL | Your Ghost site root, for example https://blog.example.com. transglot adds /ghost/api/admin/… itself. It must use https and be publicly reachable |
| Admin API key | The custom integration's Admin API key |
| Content types | posts, pages, or both |
| Translatable fields | title, plaintext, or both |
Select Connect, then Test connection. A successful test names the site.
What gets imported
transglot reads each post and page through the Ghost Admin API and imports its title and its plain-text body. The plaintext field is the body without formatting, so markup and cards are not carried into transglot.
Troubleshooting
- The form refuses the key: an Admin API key is a 24-character hex ID, a colon, and a 64-character hex secret. A Content API key has a different form and will not work.
The Ghost Admin API key is malformed (expected "id:hex-secret").orThe Ghost Admin API secret is not valid hexadecimal.Copy the Admin API key again from the custom integration.Failed verifying the Ghost Admin API key: the credentials were rejected.The key is wrong or the integration was deleted.... the resource was not found, check the site URL.Check Ghost site URL points at the site root.