Rishi_SinosendRishi_Sinosend
Rishi_SinosendPLUS
Aug 21, 2025

Q: How to update contacts?

If a contact detail has changed, how do we update Encharge to match our backend, the only way I see it is to upload a csv everytime?

Is there an API we can use to update contacts details which we can use in broadcast email?

Founder Team
David_Encharge

David_Encharge

Aug 21, 2025

A: Hey Rishi! 👋 Great question — and you’re not alone in thinking about how to keep Encharge synced with your backend.

There are 3 main ways to update contact details in Encharge:

1. CSV Import (manual sync)
You already mentioned this — and yep, it works! But definitely not ideal if you’re trying to keep things in sync automatically.

2. API (recommended for dev teams)
Yes! Encharge offers a REST API that lets you create or update contact details programmatically, including name, email, tags, custom fields, and more. You can use this to keep Encharge updated in real time with changes from your backend.

This is perfect for syncing user data you want to use in Broadcast emails, segmentation, or Flows.

3. Zapier, Pabbly, or other no-code tools
If you’re not using a developer-led workflow, we also integrate with Zapier, Pabbly, and Integrately. You can use those to update contacts when something happens in your backend system.

Let me know what your backend is (custom? Airtable? a CRM?) — happy to suggest the best sync option.

And just to clarify: yes, once a contact’s data is updated (via API, CSV, Zapier, etc), you can use those updated fields in Broadcast emails, segment filters, Flows — all of it 💥

Share
Helpful?
Log in to join the conversation

Verified purchaser

Awesome. Actually I am currently using your sdk , the js enctracking to ident the users, this is working for me. Is this the API you are talking about ?Actually how is this different from the injest api... Just asking. My backend is a a mongo database but that doesn't matter so much , it's nice to send the data from my client side app directly when the user logs in and updates something .

Yep! That JS snippet is part of our site tracking SDK — it's different from the Ingest API. You're using the client-side method, which updates contact info in real time based on user behavior. Perfect for your setup 👌

Just a heads-up: the Ingest API is backend-only and part of the Premium plan, so it’s not included in the 2025 LTD.

Verified purchaser

That makes sense. No problem about the ingest api, im glad that the js snippet works the way it does -- but curious though as to the functionality of the ingest vs the js tracking -- i mean i could use the js tracking in a node backend and update user profiles from there no? Unless there is more functionality that the ingest api offers.. -- thanks for your prompt response ---

Great question! You can technically call the JS identify() from Node, but it’s not really designed for server-side use, it relies on browser context like cookies.

The Ingest API is built for backend use and offers more power + flexibility, but it’s part of the Premium plan (not included in the 2025 LTD). If the JS snippet is working well for your use case, you’re good to roll with that! 🙌

Related questions
View product details