Allovcita (Legacy) logo

vcita (Legacy) phone integration

vcita stores phone numbers as free text, its real docs live on intandem.tech, and its openapi.json is marketing content. Here is the honest integration guide.

How it connects

Allo connects to vcita (Legacy) through Zapier today.

Licensed operator

Registered telecom operator in France (ARCEP).

Its own network

Allo runs its own VoIP infrastructure, not resold.

GDPR compliant

Your call data stays yours, handled to GDPR.

In the Claude directory

Allo's MCP server is in the Claude connectors directory.

Endpoints

Connect Allo to vcita (Legacy)

Because vcita (Legacy) has a public API, Allo connects over that API and webhooks. These are the API surfaces you point at vcita (Legacy): a small, focused REST API, JSON in and JSON out, with webhooks for real-time events.

CallsREAD

Search your call history. Every record includes transcripts, AI summaries, recording URLs, IVR selections and transfer chains.

GET/v1/api/calls
ContactsREAD & WRITE

Full CRUD on your contact database. Create, fetch by ID, update and search, with engagement data baked into every response.

GET/v1/api/contacts
POST/v1/api/contacts
PUT/v1/api/contacts/:id
SMSSEND

Send SMS programmatically from any of your Allo numbers. Dedicated endpoints for US and France, both in E.164 format.

POST/v1/api/sms
POST/v1/api/sms/fr
WebhooksREAL-TIME

Subscribe a URL to call, SMS and contact events. Full envelope payloads, no secondary fetch to enrich the data.

GET/v1/api/webhooks
POST/v1/api/webhooks
DEL/v1/api/webhooks/:id
ConversationsREAD

Pull the whole thread for a contact: calls and SMS stitched together, in order, with pagination built in from day one.

GET/v1/api/conversations
Phone NumbersREAD

List every Allo number on your account. Use it to route, filter or match a number to an owner without hardcoding.

GET/v1/api/phone-numbers

Native or Zapier

The honest version: here is exactly how the connection is made today, and what is not built yet.

Native Allo integration

Not built yet for vcita (Legacy)

Zapier

5 triggers, 5 actions published

Allo and vcita (Legacy), answered

Yes, in its activity message model. The direction clienttopivot is documented as the client calling the business, regardless of the call outcome, and messages are read from GET /v3/communication/activity_messages.

vcita stores numbers as free text. The vendor's own import sample has 1-540-672-1284 and (300) 045-4811 in one payload, so exact string matching fails. Allo normalises both sides before comparing.

On developers.intandem.tech, not on vcita.com. The developer platform is branded inTandem, which is why searching the vcita domain finds marketing pages.

No. vcita.com serves an OpenAPI document whose paths are marketing question slugs such as /qa/client-portal-software. It parses as a spec and is not the product API. Ignore it.

Phone access is its own granular permission, clients.client_phone.manage. An app can hold general client access and still be blocked from the field it needs to match a call.

Not from a number alone. firstname and externalid are mandatory on client import, so a phone only record cannot be created.

Request a formal vcita (Legacy) integration

Tell us about your team and we'll build the vcita (Legacy) integration and get you early access. The more teams that ask, the sooner it ships.

  • Native calling, texting and AI call notes inside vcita (Legacy)
  • Every call logged to the right record, automatically
  • We build it for your team and give you early access

Prefer to talk it through? Book a call