Current state
Ominvo has no public API and no webhook endpoints. Everything runs through the dashboard. If you're looking for a way to pull review data into your own systems programmatically, or trigger workflows when a new review lands — that isn't available yet.
This is the honest answer. There's no undocumented API, no early access programme, and no workaround via the current product.
Why not yet
The product is pre-launch and focused on one thing: making the core review management workflow — see review, get AI draft, edit, post — work well for business owners who aren't technical. Adding an API before that core is proven and stable would split focus without delivering proportional value.
Most Ominvo users are small business operators, not developers. The dashboard is the right interface for them. The API is for the ones who want to integrate Ominvo into a larger stack — and that's a smaller, later audience.
What's planned
A REST API and webhook system is on the GigaChad post-launch roadmap. The intended scope:
- REST API: authenticated endpoints to read reviews, AI replies, reply status, and business settings
- Webhooks: POST requests to your endpoint when a new review arrives, when a reply is approved, or when a reply is posted
- Use cases it would unlock: pushing new reviews into a CRM or Slack channel, triggering custom workflows in Zapier or Make, syncing reply history to a reporting tool, building internal dashboards on top of your review data
The API will be a GigaChad feature — not available on Noob or Chad tiers.
How to signal interest
There's no formal early access programme yet. If you're building something that would benefit from API access, the most useful thing you can do is describe your use case. Reach out via the contact form or email listed on /pricing — it directly informs what gets prioritised when API development starts.
Founding GigaChad subscribers will be first in line when the API ships. If you're on the waitlist and your use case needs API access, make sure you're on GigaChad founding pricing before the cap closes.
Updates will appear on /changelog when the API timeline becomes more concrete.