A shared directory your software keeps current.
The Contacts API creates and syncs contacts on the fly over REST. One shared softphone directory, automatic caller-ID resolution on incoming calls, and contacts linked to your CRM customer and company records.
A form submission adds the person to the team directory. The next time they call, VanceTel already knows who they are.
curl https://api.netexem.com/v1/contacts \
-H "Authorization: Bearer $NETEXEM_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"name": "Jane Rivera",
"phone": "+15557654321",
"email": "jane@acme.com",
"company": "Acme Co."
}'One POST adds a contact to the shared softphone directory.
A contact form that fills the phone book.
Call the Contacts API from your form handler and every submission becomes a real contact in the shared VanceTel directory — with the source tagged so you can trace where each one came from.
- 01
Visitor submits your form
Someone fills out a contact, quote or signup form on your site. Your handler already has their name, phone and email.
- 02
Your handler POSTs a contact
In the same request, your backend calls POST /v1/contacts with the submitted details and a source tag so you know where they came from.
- 03
They appear in the shared directory
The contact lands in the softphone directory for the whole team — no import, no spreadsheet, no copy-paste between tools.
- 04
The next call resolves to a name
When that person calls in, caller-ID resolution matches the number and surfaces their name, company and CRM link on the ringing screen.
// Your website contact-form handler (Node)
app.post('/contact', async (req, res) => {
const { name, phone, email, message } = req.body
// Add the submitter to the shared softphone directory
await fetch('https://api.netexem.com/v1/contacts', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.NETEXEM_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
name,
phone,
email,
}),
})
res.status(202).end()
})One directory, resolved on every call.
One shared directory
Contacts live in a single directory every seat shares. Add someone once over REST and the whole team sees them in the softphone on iPhone, iPad, Mac, desktop and web.
Caller-ID resolution
When a known number rings in, VanceTel resolves it against the directory and shows the name, company and CRM link on the incoming call — instead of a bare number.
CRM record linking
Pass a company reference and the contact links to your CRM customer and company records, so the softphone and your CRM point at the same person.
Create & sync on the fly
POST a contact the moment you learn about someone — a form submission, a signup, a webhook from another system. The directory stays current without a manual import.
Numbers become names, automatically.
Every inbound call is matched against the shared directory. A known caller arrives with their name, company and a link to the CRM record — so whoever answers has context before they pick up.
Contacts API, answered.
Want to see resolution and CRM linking on real calls? A live walkthrough is the fastest way.
What is the Contacts API?
The Contacts API is a REST endpoint for creating and syncing contacts in the shared VanceTel softphone directory. You POST a contact with a name, phone, email and optional CRM reference, and it becomes available to every seat — and to caller-ID resolution on the next inbound call.
How does caller-ID resolution work?
When a call rings in, VanceTel matches the inbound number against the shared directory. If it finds a contact, the softphone shows that person’s name, company and any linked CRM record on the incoming-call screen instead of a raw phone number.
Can a website form add someone to the directory?
Yes. Your form handler calls POST /v1/contacts with the submitted name, phone and email. The person is added to the shared softphone directory immediately, so the next time they call your team already knows who they are.
Does the contact link to my CRM?
Pass a company reference when you create the contact and VanceTel links it to your CRM customer and company records. The softphone contact and your CRM customer then point at the same person, so calls and texts line up with the right account.
Is the directory shared across the team?
Yes. There is one shared directory rather than per-device address books. A contact you create over the API shows up for every seat on every platform the VanceTel softphone runs on — iPhone, iPad, Mac, Apple Vision Pro, Windows/Mac desktop and the web.
Keep the phone book in sync with your software.
See the Contacts API, caller-ID resolution and CRM linking working in the VanceTel softphone in a 20-minute walkthrough.