FAQ: Mitti rebrand for developers
What changed on the Developer Portal and what it means if you build on the Mitti API.
SafetyCulture is now Mitti. This page covers what changed on the Developer Portal and what it means if you build on the Mitti API.
The rebrand launched on 11 August 2026. The Developer Portal, the API base URL, and the documentation are already on Mitti. Migrating customer organizations to the Mitti domains is a separate piece of work that runs in stages into 2027.
Developer Portal
Where is the Developer Portal now?
The Developer Portal moved from developer.safetyculture.com to https://developer.mitti.com.
Do my old Developer Portal links still work?
Yes. Requests to the old domain redirect to the new one, so bookmarks and saved links resolve correctly.
What changed in the documentation?
The home page copy, logo, and visual assets are now Mitti, and SafetyCulture was replaced with Mitti throughout the documentation, including endpoint descriptions and authentication guides. The API reference now documents api.mitti.com as the base URL.
API integration
Will my existing API calls break?
No. Endpoint paths, request and response schemas, authentication, API tokens, and rate limits are all unchanged. Existing integrations kept working through the rebrand, and your current tokens remain valid.
Do I need to update my base URL?
Not immediately. https://api.mitti.com is live and is the long-term host. https://api.safetyculture.io still works and no shutoff date has been set, so you can move across when it suits you. Any change to that is published in the Changelog.
Is there a regional base URL?
No. One host serves all regions.
Did webhook signature headers change?
No. Webhooks still sign with the x-safetyculture-signature header, and your existing signature verification keeps working. The header name is unchanged despite the rebrand, so leave it as it is in your code. Any change to it is published in the Changelog.
Are native integrations like Zapier, Workato, Power Automate, Power BI, Procore, Samsara, or Geotab affected?
The listings for these connectors in the Integrations Marketplace are being renamed to Mitti in stages over the coming weeks. A rename changes the connector's name and logo in that platform's directory.
Did the SafetyCulture Exporter change?
Yes. It's now the Mitti Exporter. The tool works the same way and your existing configuration is unaffected.
Domains and allowlists
My organization allowlists SafetyCulture domains in our firewall. Do I need to do anything?
Yes, if your organization restricts outbound traffic by domain or IP address. Add the Mitti domains before your organization's migration window. Organizations migrate in stages through 2026 and into 2027, and each one is emailed its own window. See Network configurations for Mitti for the full list.
Getting help
Who do I contact if something isn't working?
Contact the Mitti support team at mitti.com/contact-us.
Updated 25 days ago