Your client list, now in the API
The API reaches your clients. Alongside decks, an API key can now read and update the people in your firm's client book. In Settings → Developer, two new permissions decide how far a key goes: read the client book, or add and update people. Clients are shared with the whole firm, so a key created by a guest is refused, the same as that person is in the app.
Keep your client list in step with the CRM you already use. A new bulk endpoint takes a batch of people from any outside system — through Zapier, Make, or a script of your own — and files them into the book. Each person carries the id your system uses, so someone who changes jobs and changes email keeps their Foveate record, their meeting notes and their profile. Send the same list twice and nothing happens the second time; only real changes are written.
It will not quietly merge two people, and it will not delete anyone. When an incoming person matches someone already in your book beyond doubt, the two join up. When the evidence is weaker — two contacts sharing one address, or just the same name — you get both records and a note that they might be the same person, for you to decide. Removing someone in your own system marks the connection and leaves their Foveate record, notes and profile untouched.
Corrections you make by hand stay corrected. If you fix a phone number or a job title in Foveate, a later sync from an outside system leaves your version alone instead of overwriting it on the next run.
Adding the same person twice no longer creates a duplicate. Whether a person arrives from the API, a form, a share link or a CSV, Foveate recognises someone already in the book and fills in only what was missing.




