Has the antitrust scrutiny of Reynolds changed how they handle third-party access?

No, not materially. The automotive tech community and at least one lawsuit have raised concerns that Reynolds and Reynolds uses its integration access restrictions to disadvantage competing software vendors, a model that attracted attention from both regulators and industry groups. Reynolds Connect still requires both dealer authorization and Reynolds approval for each integration. This is a structural condition of the market rather than a developer experience gap that Reynolds is actively working to close. For a team trying to ship an ERA-IGNITE integration on a product timeline, the Reynolds Connect approval process is not a reliable path.

How long does it take to get access to ERA-IGNITE through Integuru?

Chat with us. Most integrations are scoped and ready for testing in 1-2 weeks. The process starts with a technical scoping call to identify the specific ERA-IGNITE workflows your product needs: inventory data, deal records, service orders, CRM, or F&I. From there Integuru reverse-engineers the relevant ERA-IGNITE endpoints, handles authentication, and delivers a documented HTTP API. ERA-IGNITE is one of the most requested DMS integrations in the automotive tech stack.

Back to Platform API Guides

OtherPartner API only· workaround available

Reynolds and Reynolds API

Reynolds and Reynolds gates all ERA-IGNITE API access through Reynolds Connect, requiring both dealer authorization and Reynolds approval. Integuru generates a production-ready HTTP API covering inventory, deals, service, and CRM. Chat with us to get started.

Backed by

Free sandbox trial before production

<3 sec

Response latency per call

99.9%+

Reliability rate on generated APIs

24/7

On-call maintenance on production plans

Sandbox trial before production

What Reynolds and Reynolds currently offers publicly

Partner API only

Reynolds and Reynolds restricts all API access to the ERA-IGNITE platform through the Reynolds Connect dealer data program. Each integration requires explicit authorization from the dealer AND separate approval from Reynolds and Reynolds itself. The automotive tech community has filed regulatory complaints about Reynolds' integration restrictions, and the company has faced antitrust scrutiny over its access model. The approval process is not self-serve, has no published timeline, and requires re-authorization for each individual dealer.

Reynolds and Reynolds official site

How Integuru fills the gap

Integuru generates a production-ready HTTP API for Reynolds and Reynolds without a partner agreement. It maps the authenticated network requests the Reynolds and Reynolds web app already makes, handles the login flow including 2FA, covers the branching states real accounts hit, and keeps the API running with 24/7 on-call maintenance on production plans.

Planned endpoints

Actions Integuru could expose

Final scope is confirmed when the integration is built

list_vehicles

Return a paginated inventory of vehicles from the ERA-IGNITE platform with VIN, make, model, year, trim, and stock status

get_vehicle_detail

Retrieve the full record for a single vehicle including pricing, options, days on lot, and reconditioning status

update_vehicle_status

Update a vehicle's pricing, availability status, or inventory flag within ERA-IGNITE

list_deals

Return a list of active and closed deals filtered by date range, salesperson, and deal type

get_deal_detail

Retrieve the full deal record including customer, vehicle, F&I products, financing terms, and deal state

create_deal

Open a new deal record against an existing customer and vehicle within the ERA-IGNITE DMS

list_service_orders

Return open and closed repair orders filtered by date range, advisor, and vehicle

get_service_order_detail

Retrieve a single repair order with labor operations, parts lines, technician assignments, and completion status

create_service_order

Open a new repair order for a vehicle within ERA-IGNITE, assigning a service advisor and initial operation

list_customers

Return a paginated customer roster with contact details, vehicle ownership, and deal or service history

get_customer_detail

Retrieve the full customer record including contact information, purchase history, and open service items

create_customer

Create a new customer record in the ERA-IGNITE CRM layer with contact, address, and communication preference data

get_fi_menu

Retrieve the F&I product menu for an active deal including available products, pricing, and reserve structures

submit_fi_contract

Submit a signed F&I contract for an approved product against an active ERA-IGNITE deal record

...many more

These actions reflect what Integuru would generate based on the workflows Reynolds and Reynolds exposes through its web interface.

Need a different Reynolds and Reynolds action?

Tell us the workflows and accounts you need. Requested integrations are delivered to a sandbox you can test free before production.

Process

What happens after you book a call

1Tell us the Reynolds and Reynolds workflows you need
Book a call and list the actions, account types and call volume. There is no separate build fee to start.
2Integuru builds the API in days
The team maps the authenticated requests Reynolds and Reynolds makes into a direct HTTP API, covering the edge cases you named, and delivers it to a sandbox you test free.
3Move to production, maintained
Call documented REST endpoints from your stack, and hand breakage to Integuru: production integrations are maintained around the clock, with auth auto-healing included.

Guide

Reynolds and Reynolds integration guide

Overview

Reynolds and Reynolds is the second-largest dealer management system vendor in North America, used by a significant share of franchised auto dealerships running the ERA-IGNITE platform. Its DMS covers inventory management, deal processing, service repair orders, finance and insurance, CRM, and accounting. Like CDK Global, Reynolds has the market concentration that makes it a required integration target for most automotive retail technology products: desking tools, AI pricing platforms, F&I compliance software, and CRM systems all encounter Reynolds at a meaningful portion of their dealer customer base.

Reynolds Connect, the dealer data program that controls all ERA-IGNITE API access, is the most restrictive integration model among major DMS vendors. Access requires authorization from the dealer AND a separate approval from Reynolds and Reynolds itself, applied individually to each integration. The approval process has no published timeline and is not self-serve at any stage. The automotive tech community has raised this access model in regulatory complaints and antitrust proceedings, characterizing the dual-authorization requirement as a mechanism for limiting competition from independent software vendors. These proceedings have attracted scrutiny but have not changed the Reynolds Connect access model. For automotive tech teams, this is the operating environment rather than a problem Reynolds is working to solve.

Integuru generates a production-ready HTTP API for ERA-IGNITE using direct HTTP requests against the same endpoints the ERA-IGNITE web application uses internally. Inventory records, deal data, service orders, customer CRM, and F&I workflows are all reachable without Reynolds Connect enrollment or Reynolds approval. The Production plan includes 24/7 on-call maintenance to handle session management, authentication flows, and endpoint changes before they affect your production calls.

Why Teams Need This Integration

ERA-IGNITE's market share among franchised dealers makes it a hard dependency for automotive retail platforms, and the Reynolds Connect dual-authorization requirement makes even starting the integration a multi-party negotiation.

AI desking and deal management tools. Products that automate the deal desk, recommend financing structures, or generate buyer worksheets need list_deals, get_deal_detail, and create_deal to read and write the ERA-IGNITE deal layer. A desking tool that has to wait for Reynolds Connect approval before it can test against a real deal record is measuring its go-to-market timeline in months rather than weeks.

Inventory aggregators and pricing platforms. list_vehicles and get_vehicle_detail return the live ERA-IGNITE inventory with VIN, pricing, trim, and reconditioning status. Inventory syndication platforms and AI pricing engines that run across multiple DMS vendors need ERA-IGNITE alongside CDK and Tekion to cover the market; the Reynolds Connect barrier makes it the last one to get integrated and the one dealers most frequently cite as a blockers when requesting platform-specific features.

Service lane and repair order automation. AI service advisors, digital inspection tools, and repair order tracking platforms need list_service_orders, get_service_order_detail, and create_service_order to read the current state of the service drive and push back updated repair data. create_service_order lets a service AI tool open a new repair order when a customer arrives without a pre-booked appointment, which is the scenario these tools exist to handle.

F&I technology and compliance platforms. Finance and insurance products that track product penetration, generate compliance documentation, or surface product recommendations during deal structuring need get_fi_menu and submit_fi_contract. ERA-IGNITE is the deal-of-record for a large share of F&I-heavy franchised dealerships, and F&I tech platforms that cannot integrate with it are leaving a meaningful portion of the market unserved.

DMS Workflows This Integration Covers

The fourteen planned actions cover the ERA-IGNITE operational loop across inventory, deals, service, CRM, and F&I:

Inventory management: list_vehicles and get_vehicle_detail surface the live inventory with VIN, pricing, options, and reconditioning status. update_vehicle_status gives downstream tools write access to update pricing and availability.
Deal management: list_deals and get_deal_detail return active and closed deal records with customer, vehicle, financing terms, and F&I data. create_deal opens new deal records for desking and sales tools.
Service orders: list_service_orders and get_service_order_detail cover the repair order layer with labor, parts, and technician assignments. create_service_order gives external service automation tools write access to the ERA-IGNITE service drive.
CRM and customer data: list_customers, get_customer_detail, and create_customer support CRM sync, customer engagement platforms, and lead intake tools that need a live, writable customer roster tied to ERA-IGNITE deal and service history.
F&I processing: get_fi_menu retrieves available F&I products and pricing for an active deal. submit_fi_contract pushes signed contracts back for compliance and contracting automation.

Adjacent Integrations

Integuru does not currently have live automotive-specific integrations. The approach Integuru uses has been proven across enterprise platforms with comparable authentication complexity and data sensitivity. The Modmed integration covers 21 live actions on a cloud EHR platform requiring multi-session management and strict data access controls. The NextGen integration delivers 10 live actions for a large healthcare platform serving multi-location practices, the same multi-rooftop access pattern that dealer groups running ERA-IGNITE across locations require. The eClinicalWorks integration handles a major enterprise platform with complex session lifecycle requirements, directly analogous to ERA-IGNITE's authenticated request architecture.

The Workeasy integration and HomeBase integration provide workforce scheduling and employee management data for service department operations that run alongside the ERA-IGNITE DMS.

Live in Other

Integuru already supports these platforms in the same vertical

Live, production-ready integrations, not requests

Workforce & Scheduling

WorkeasyLive