Skip to content
Developers / AVAILABLE NOW

API & webhooks, meet Eminex.

Read content and SEO fixes from an API, and get goal events by webhook.

WHAT THIS CONNECTION SUPPORTS

Put API & webhooks to work.

  • One script tag applies titles, meta descriptions, canonicals, Open Graph tags and structured data on every page.

  • A read-only Site API returns your published articles, each page's SEO metadata and a sitemap, so you render them server-side in Next.js or any framework.

  • Calls your rebuild hook when an article is published, so static sites stay current.

  • Signed webhooks tell your systems when a goal completes or fails, with retries and a delivery log.

GET CONNECTED

Start here.

  1. 01

    In Eminex, open Connections, choose Website, and pick “Custom / Next.js · tag”.

  2. 02

    Paste the tag into your site's <head> and click I've added the tag — check it.

  3. 03

    For server-side rendering, open Advanced, create a read-only API key and add it to your app's environment.

  4. 04

    To receive events, add an endpoint on the Developer page and send a test ping.

What you approve

Articles only appear in the Site API once you've approved them, and SEO fixes reach your pages only after you apply them.

IN DETAIL

What the Site API returns

Create a key in Settings → API keys and send it as an X-API-Key header or a Bearer token. With it you can list your published articles, up to 200 at a time; fetch one article with its body in Markdown and HTML; get any page's SEO metadata by slug, including the title, description, canonical link, Open Graph tags and structured data; and download a sitemap of your Eminex articles.

A public reviews feed and its widget script need no key at all, so you can show reviews on any page.

Webhooks you can rely on

Webhook endpoints must use HTTPS. Each one gets its own secret, shown once and rotatable, and every delivery is signed so your code can check it came from Eminex. Subscribe to the events you want, or all of them.

A failed delivery is tried three times in total, after 5 and 30 seconds. Every attempt shows in the delivery log, and you can send a test event whenever you change your endpoint.

A LITTLE MORE DETAIL

Your API & webhooks
questions.

Each delivery is signed with your endpoint's own secret, so your code can verify it before acting on it.

KEEP EXPLORING

Make the next connection.

MAKE YOUR NEXT MOVE

Bring API & webhooks into your workflow.

Connect your tools, review the next opportunity and keep moving forward.