Developers
API & webhooks
Read content and SEO fixes from an API, and get goal events by webhook.
Built your own site? Eminex works with custom stacks too. Add one tag to your site's <head>, or go further with a read-only Site API that hands your build the articles and SEO fixes Eminex has ready.
What Eminex does with API & webhooks
- 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.
How to connect API & webhooks
- 1In Eminex, open Connections, choose Website, and pick “Custom / Next.js · tag”.
- 2Paste the tag into your site's <head> and click I've added the tag — check it.
- 3For server-side rendering, open Advanced, create a read-only API key and add it to your app's environment.
- 4To 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.
API & webhooks questions
- Do I need the API, or is the tag enough?
- The tag is enough to apply SEO fixes. Use the API when you want search engines to see the fixes in the first HTML response, or to publish Eminex articles on your own blog.
- Which webhook events are sent?
- Goal completed and goal failed, plus a test ping.
- Is API access on every plan?
- API keys and webhooks depend on your plan — see Pricing for what each plan includes.