Installation and connection
Install the plugin and connect it to your Threadliner workspace.
The plugin itself — its settings page, both block names, its text domain — still says "Threadline" rather than "Threadliner" throughout. That's a naming cleanup that hasn't shipped to the plugin yet; everything below matches what you'll actually see today.
Requirements
- WordPress 6.4 or later
- PHP 8.0 or later
Installing
Install and activate the plugin like any other — via Plugins → Add New if it's listed in your directory, or by uploading the plugin zip under Plugins → Add New → Upload Plugin.
Connecting
- In Threadliner, go to Settings → API Keys, create a key, and copy it
immediately — it's only shown once, and starts with
tl_live_. - In WordPress, go to Settings → Threadline.
- Fill in:
- API URL — your Threadliner API endpoint (e.g.
https://api.threadliner.io), no trailing slash needed. - API Key — the key from step 1.
- API URL — your Threadliner API endpoint (e.g.
- Click Save & Test Connection.
If the connection succeeds, the page shows "Connected to Threadline." in a green notice above the form. If it fails, you'll see "Could not connect to Threadline: <reason>" — see Troubleshooting for what the reason usually means.
What the API key can do from WordPress
The key is stored in WordPress's own options table and never sent to the browser — form
and list pickers in the block editor go through a small WordPress REST API proxy
(/wp-json/threadline/v1/forms and /wp-json/threadline/v1/lists) that attaches the
key server-side, gated to users who can edit posts. The public-facing embed itself
(rendering a form, accepting a submission) doesn't use the key at all — see
Embedding a form for why that's unauthenticated by design.
Uninstalling
Deleting the plugin from Plugins removes its two stored settings (API URL and key)
along with it — nothing is left behind in wp_options.
Last updated on