Umbraco integration
No native Umbraco connector, here is what does work.
We create documents through Umbraco's Management API with draft, publish, and scheduled states.
How it works
Umbraco 14 introduced a Management API that covers full document CRUD, authenticated with OAuth client credentials through an API User. We can save drafts, publish, and use Umbraco's scheduled publishing, so the full editorial state model is available programmatically. Your document types define the payload, and we map to them during setup.
Umbraco is self-hosted, which means two things vary per site: whether your version has the API at all, since Umbraco 13 and older do not, and how your Management API endpoint is exposed to the internet. We check the version at connect time, and our connection diagnostics identify firewall, proxy, and authentication problems by name instead of a generic failure.
Best forOrganizations on Umbraco 14 or newer that want content delivered into their existing document types and workflows.
Setup, step by step
- Confirm your site runs Umbraco 14 or newer, since earlier versions lack the Management API.
- Create an API User in the Umbraco backoffice with permissions limited to the content sections we publish into.
- Add the client ID, client secret, and your site's Management API base URL to SearchHandled's Umbraco connector.
- Map your document types, properties, and any culture variants during setup.
- Run the connection diagnostics, which verify reachability, authentication, and write permission in sequence.
Best practices
Create a dedicated API User
Umbraco's API Users exist so integrations do not ride a person's account. Give ours access to the content sections we publish into and nothing more, and revoking it later touches nothing else.
Use Umbraco's own scheduling
The Management API supports scheduled publishing natively, so we hand the schedule to Umbraco rather than timing calls ourselves. Scheduled items appear in the backoffice where editors can see and change them.
Settle culture mapping early
If your site uses culture variants, the document payload shape changes per language. We map which cultures we write during setup so multilingual sites do not end up with half-filled variants.
Keep the API endpoint deliberately exposed
Self-hosting means you control what the internet can reach. Expose the Management API through your normal HTTPS endpoint with your usual protections, and tell us if it sits behind an allowlist so we can give you our addresses.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Umbraco 13 and older lack the Management API
Sites on Umbraco 13 or earlier have no Management API to call, so the connector cannot work there.
How we handle itWe detect the version at connect time and say so plainly. For older sites, the fallback is our HTML export until your Umbraco upgrade lands.
docs.umbraco.com
Culture and variant payloads differ per setup
Document payloads change shape depending on your document types and whether properties vary by culture, so writes that assume one shape fail on another site.
How we handle itWe map your document types and cultures during setup and validate a test document against them, so shape mismatches show up in onboarding, not production.
docs.umbraco.com
Self-hosted endpoint exposure varies
Firewalls, reverse proxies, and hosting choices mean the Management API may not be reachable from outside, and failures look identical from a generic client.
How we handle itOur connection diagnostics test reachability, TLS, authentication, and write permission separately and report which step failed, so your team fixes the actual problem.
docs.umbraco.com
Questions teams ask
- Which Umbraco versions are supported?
Umbraco 14 and newer, because that is when the Management API arrived. We check the version when you connect, and older sites can use our HTML export in the meantime.
- Does this handle multilingual sites?
Yes, if we map it. Culture variants change the document payload, so during setup we agree which cultures we write and which stay under your team's control.
- How does authentication work?
Through an API User with OAuth client credentials, which is Umbraco's built-in mechanism for machine access. You scope its permissions in the backoffice and can revoke it at any time without affecting anyone's login.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Umbraco matters moves it up the rollout.