Public API
A
Alyssia Wheat
Endpoint to communicate with DC with access token. We have so many systems that could connect with our CRM, but it seems your team is the only way to go when connecting. It would more thoughtful if your team created a robust API and then any system would be able to connect without putting extra load on your dev team.
Shelby Parker
Thanks for raising this, Alyssia Wheat — totally hear you on wanting a more robust public API so integrations don’t have to run through our team. To help us understand what would be most valuable to ship first, could you share (1) the top 1–3 actions you’d want to handle via API right away (e.g., create/update leads, pull customer/vehicle records, log activities, send messages, reporting), (2) which external systems you’re trying to connect to DriveCentric and what outcome you’re aiming for with those integrations, and (3) who would be using the API on your side (internal devs, third-party vendors/partners, or both) and whether access needs to be scoped to specific rooftops/dealerships or certain data areas?
B
Brian Coon
I second this request!