Skip to content

Connect WordPress to JaDel

With the Lynbro Social Auto Post plugin you can share a WordPress post on your social channels in JaDel. The plugin uses only an API key that you create yourself and can revoke at any time.

What the plugin does

  • When you publish or schedule a post, the plugin sends its title, excerpt, link and the images you choose to JaDel.
  • JaDel creates a post for each channel you chose, checks it against the network's rules and publishes it at the scheduled time.
  • The status (published, failed, link to the post) comes back to WordPress and is shown next to the post.

Step 1 — Create a JaDel account

Create a free account and connect the social channels you want to share on (e.g. Telegram, Bluesky or Mastodon).

Create a free account

Step 2 — Create an API key

The button in the plugin opens JaDel with the fields filled in for your site. You can also open the page yourself:

Create a key for WordPress
/app/keys/new/?name=your-site.dk&scopes=posts:write,channels:read,media:write&source=wordpress

Permissions the plugin needs

  • posts:write — create and schedule posts from your articles
  • channels:read — show your channels in the editor so you can choose
  • media:write — send the images you choose with the post

Site addresses: enter your site's address, e.g. https://my-site.dk, and optionally a staging site (at most 5). The key works only from those addresses.

Webhook URL: https://my-site.dk/wp-json/lynbro-jadel/v1/webhook — JaDel sends the status back to the plugin here. It is filled in for you.

Step 3 — Paste the key in WordPress

  1. Copy the key (jd_sk_…). It is shown only once.
  2. Go to WordPress → Settings → Lynbro Social Auto Post → Connection and paste the key.
  3. Press “Test”. The plugin shows your plan, how much you have used and your channels.

Step 4 — Publish a post

  1. Open a post. In the “Lynbro Social Auto Post” panel choose channels and adjust the text if you like.
  2. Publish or schedule the post as usual. JaDel schedules the social posts.
  3. The status comes back through a signed webhook and is shown next to the post.

What is sent to JaDel

Only for the posts you choose to share:

  • title, excerpt and the post's URL
  • the images and texts you choose in the panel
  • the publishing time

What JaDel never gets

  • No WordPress login, no users, passwords, database or FTP access.
  • JaDel reaches your site only through signed webhooks to the plugin's own route — nothing else.

How to disconnect

  • In JaDel: API & WordPress → Revoke. The key stops working at once.
  • In WordPress: Settings → Lynbro Social Auto Post → Disconnect. The plugin deletes the key from the site.

Limits per plan

The WordPress plugin works on every plan. The limits are the same as in the app:

PlanChannelsPostsAPI
Free360 posts per 30 daysWordPress plugin and API (posts, channels, media)
Start8Unlimited posts (fair use)WordPress plugin and API (posts, channels, media)
Pro25Unlimited posts (fair use)Full API: every permission, incl. analytics and AI
Agency75Unlimited posts (fair use)Full API: every permission, incl. analytics and AI

For developers

The plugin uses JaDel's regular API at https://jadel.dk/api/v1. You can use the same API from your own system.

Endpoints a key can use

  • GET/api/v1/me
  • GET/api/v1/channels
  • POST/api/v1/ideas
  • POST/api/v1/ideas/{id}/variants
  • POST/api/v1/ideas/preflight
  • POST/api/v1/ideas/{id}/preflight
  • POST/api/v1/ideas/{id}/schedule
  • POST/api/v1/assets
  • GET/api/v1/openapi.json

Headers

Authorization: Bearer jd_sk_…
The API key. Required.
X-Lynbro-Origin: https://your-site.dk
Required when the key has addresses. Must be one of them.
Idempotency-Key: <uuid>
On every write. Same key + same body within 24 h = same response.
X-Dry-Run: 1 or ?dry_run=true
Validates everything, writes nothing.
Accept-Language: da | en | uk
Language of error messages.
curl -X POST "https://jadel.dk/api/v1/ideas?dry_run=true" \
  -H "Authorization: Bearer jd_sk_…" \
  -H "X-Lynbro-Origin: https://your-site.dk" \
  -H "Idempotency-Key: wp-post-123-rev-4" \
  -H "Content-Type: application/json" \
  -d '{"text": "New on the blog", "link": "https://your-site.dk/post"}'

Error codes

CodeHTTPMeaning
invalid_key401The key is wrong, expired or revoked.
scope_missing403The key lacks a permission (details.scope).
origin_mismatch403X-Lynbro-Origin is missing or not one of the key's addresses.
quota_exceeded402The plan's limit is reached (details.resets_at, details.upgrade_url).
rate_limited429Over 120 requests per minute per key. Wait Retry-After seconds.
idempotency_key_reused422Same Idempotency-Key with a different body.
idempotency_in_progress409The first request with this key is still running.

Idempotency-Key

Send a new UUID for each action and the same one on a retry. If the server sees the key again, you get the first response with the header Idempotent-Replayed: true — a duplicate post is never created.

Dry run and sandbox

With ?dry_run=true or X-Dry-Run: 1 the request is validated but nothing is written. A key created as sandbox always runs as dry run.

Webhooks

  • Events: post.published, post.failed and ping (from the “Test webhook” button).
  • JaDel sends a JSON POST to the key's webhook URL with the headers X-Lynbro-Timestamp, X-Lynbro-Event-Id, X-Lynbro-Event and X-Lynbro-Signature.
  • If delivery fails, JaDel retries with growing pauses for up to about 20 hours.
  • The receiver must check the signature and the time (±300 s), skip duplicates by event id, then re-read the post through the API before acting on it.
{
  "id": "3f6c…-uuid", "type": "post.published", "created_at": "2026-11-17T10:00:00Z",
  "data": { "idea_id": "…", "variant_id": "…", "channel_id": "…", "provider": "bluesky",
            "status": "published", "external_url": "https://…", "published_at": "…", "error": null,
            "idea_status": "published" }
}

Signature

X-Lynbro-Signature: v1=<hex>
<hex> = HMAC-SHA256(webhook_secret, timestamp + "." + "POST" + " " + path + "." + raw_body)

path is the path of the webhook URL (with its query, if any), e.g. /wp-json/lynbro-jadel/v1/webhook. raw_body is the raw body before parsing.

Check in PHP

function lynbro_verify(string $secret, string $path, string $raw_body, array $h): bool {
    $ts  = $h['x-lynbro-timestamp'] ?? '';
    $sig = $h['x-lynbro-signature'] ?? '';
    if (!ctype_digit($ts) || abs(time() - (int) $ts) > 300) {
        return false;                                   // too old or from the future
    }
    $base = $ts . '.' . 'POST' . ' ' . $path . '.' . $raw_body;
    $want = 'v1=' . hash_hmac('sha256', $base, $secret);
    return hash_equals($want, $sig);                    // constant-time compare
}
// Then: skip if X-Lynbro-Event-Id was seen before; re-read the post via the API.