Documentation: docs.versionseven.ai
We've officially released the Victoria public API.
Victoria has always handled the hard part well. Running outreach, managing conversations, surfacing replies, showing notifications, and giving visibility into pipeline activity. Teams could open the app and understand what was happening inside their outbound.
But the moment you wanted Victoria to actively participate in the rest of your business, things got awkward.
Leads lived in other systems. Deals lived in other systems. Internal workflows lived in other systems. So even though the conversations were automated, operations still required people to move information around. Export lists. Update records. Trigger follow ups manually. Double check reporting across tools.
We built the API so Victoria does not just show you activity. It can now act inside your company's processes.
From a Platform You Check to a System That Participates
The goal has never been to build another outreach dashboard. The goal is an AI SDR that actually operates inside a company.
A real SDR does not just start conversations. They react to them. They update records. They create opportunities. They notify the team. They trigger next steps.
Now Victoria can do that with your stack in real time.
- You can automatically import leads instead of uploading lists.
- You can move deals through pipeline stages directly inside the Victoria CRM.
- You can trigger external workflows the moment a prospect replies.
- You can keep reporting and internal dashboards aligned without manual syncing.
Outbound stops being an activity you monitor and becomes a stream of events your business reacts to.
What The API Enables
We released endpoints across leads, campaigns, pipelines, deals, authentication, and webhooks so the data layer is fully accessible both directions.
Your systems can create and update leads programmatically instead of relying on manual uploads. Campaign and performance data can be read directly for internal reporting. Pipelines and deals can be managed automatically as conversations progress.
Webhooks allow Victoria to notify your systems the instant something important happens. A reply, sentiment change, or meeting intent can trigger enrichment, task assignment, routing, or notifications for your team.
In practice this means when a conversation advances, everything else advances with it.
- No waiting for sync jobs.
- No duplicate records.
- No wondering if the CRM matches reality.
Why This Matters
Most outbound software helps you send messages. After that, the real work starts. Someone has to bring the result back into the business.
That gap is why outbound often feels fragile. The pipeline depends on humans remembering to update things.
With direct access to the data layer, Victoria becomes part of the operational flow. Conversations create structure automatically. Opportunities appear where they should. Teams react immediately because the information exists everywhere at once.
The AI SDR is no longer a tool sitting beside your processes. It becomes part of how your processes run.
Where We're Heading
We want pipeline generation to feel like infrastructure. Predictable, connected, and dependable.
The public API is a big step toward that. Companies can now integrate Victoria into CRMs, internal tools, onboarding systems, analytics dashboards, and custom automations so outbound activity immediately drives action across the organization.
If you build on top of it, we would genuinely love to see what you connect.
Start here: docs.versionseven.ai