Looking for more on API? This collection on the Emdash Kits blog brings together related articles, guides, and insights. Browse all 5 posts below.
Clicking "Sign in with GitHub" in the admin panel requested a URL that didn't exist — the admin's own client-side router was treating an external API link as one of its own internal routes.
A failed GitHub sign-in only ever showed a generic schema-validation error in the logs — GitHub's actual reason (a bad code, wrong client credentials) was being silently discarded.
A link-in-bio feature built on its own database tables kept throwing a body-parsing error on any request with a valid, owned ID — the root cause was never found, but moving the same data into a CMS content type made it vanish completely.
There's no Settings → Webhooks panel in EmDash — outbound webhooks are something you build as a small sandboxed plugin using a content hook and ctx.http. Here's the real, working pattern, including the specific capability EmDash's own docs name for exactly this use case.
Content, media, schema, revisions, search, and plugin endpoints, all under one consistent response envelope and Bearer-token auth. This is the practical map of EmDash's REST API for scripts, CI pipelines, and admin tooling.