CCC ONE Export and API: What Collision AI Can Actually Read

Collision is the honest hard part of any automotive AI conversation. Mechanical repair, for all its chaos, usually has a shop-management API. Collision lives in an estimating platform the insurer already trusts. At Detail Driven that platform is CCC ONE. CCC Intelligent Solutions documents import and export of EMS assignments, EMS estimates, and workfile copies, and a File Export directory for CIECA EMS 2.01 estimates, EMS part price changes, AWF workfile copies, and Parts Trader XML. That is the door we used. It is not the door people wish existed.

CIECA (the Collision Industry Electronic Commerce Association) has spent decades making EMS a standard so estimating systems can hand a file to someone else without inventing a new language every year. EMS 2.01 is that language. It is an estimate file. It is not your schedule, your technician time clock, or your front-office chatter. Treating it as a complete picture of the body shop is how integrators get cute and then get stuck.

What CCC will export

In CCC ONE help, the shop configures export directories under Machine Settings → File Export. Export types include CIECA EMS 2.01 Estimate, EMS Part Price Change, Workfile Copy (AWF Estimate), and Part XML for Parts Trader. On cccone.com, CCC has also described exporting estimate EMS, importing EMS assignments, and importing part price changes, with options to include or redact customer information and the VIN. Locked estimates can prompt an export. Manual export exists for a workfile. The files land in a folder the shop already chose.

That folder is the bridge. Collectors watch it. New estimates and Final Bills become records the operator OS can see next to repair, detailing, and glass. Insurance work stays in CCC. We are not trying to become an estimating system. I-CAR training exists because collision work is a trade with a standard of care. An agent that rewrites an estimate is not a product. It is a liability.

The other door: CCC Secure Share

If you searched for a CCC ONE API, this is it. CCC Secure Share is CCC's network of cloud APIs for third-party apps. CCC describes it as a RESTful cloud service using the CIECA BMS standard, in JSON or XML, connecting cloud to cloud. App developers register, CCC reviews the application, and CCC assigns each app the BMS message that fits its business purpose. Registered developers get a dashboard with API documentation and samples. On the shop side, CCC says repairers can see which apps receive their data and turn access on or off, without setting up export paths or installing a data pump.

• File Export: EMS 2.01 files written to a folder on a shop machine the shop configures, documented in CCC ONE help under Machine Settings. Something local has to watch the folder.
• Secure Share: BMS messages over a cloud API. Needs a registered developer and CCC's approval of the app's purpose. The shop controls access from CCC's side.
• Neither one: the production schedule as a clean feed, or the full CCC ONE database. Ask what your shop actually gets before anyone quotes a build.

Which door is right depends on the shop and on what the agent needs to see. For a single location that already exports EMS, the folder is often the faster start. For an app that serves many shops, Secure Share is the route CCC built for that. Either way, the data is the estimate and its related messages, not everything that happens in the building.

What we did not get

The schedule. In this install, CCC would not give us the collision schedule as a clean feed. We did not scrape DATA.DAT to fake it. We did not sit a computer vision model on the planner wall. Quiet files (estimates and jobs that stopped moving) we can infer from the exports and from dates that stop changing. Who is painting what at 2 p.m. is still a person looking at the board. That constraint is in the case study because hiding it would be a lie.

• We read EMS estimates and Final Bills from the folder CCC already writes.
• We honor redaction settings the shop configured for PII and VIN.
• We do not scrape the CCC desktop database.
• We do not replace the writer, the insurer relationship, or the estimating platform.
• Uncollected finals and files that went quiet surface as exceptions on the operator dashboard.

Why scraping is not a strategy

There is always a consultant who knows a way into the local files. There is always a shop that will say yes because they are tired. Then CCC ships a patch, or a new workstation, or a cloud-only path, and the integration becomes folklore. NIST’s AI RMF is dry on this point and still right: if you cannot govern the data path, you cannot measure it, and you cannot manage it when it breaks. A folder CCC documents is governable. A reverse-engineered database is not.

The Bureau of Labor Statistics counted on the order of 109,000 automotive body and related repairers in repair and maintenance establishments in its 2025 occupational data. Those people do not need a clever scrape. They need the office to notice that a file has not moved, that a Final Bill was never collected, and that the customer has not had an update since the supplement fight started.

What an agent can watch on collision

Quiet files. Uncollected finals. Updates that never went to the owner of the vehicle. A morning exception list that includes collision next to repair instead of living in a separate brain. Follow-up drafts a person still sends. The collision view on the dashboard is a window into CCC exports, not a second CCC. If a future shop has a better API, the audit will use it. We will not pretend Detail Driven had one.

The bridge reads the folder CCC already writes. It does not scrape DATA.DAT.

What the collision audit looks like

Share the CCC export settings. Show us a locked estimate and whether a file landed. Show us a Final Bill that never got collected. Show us how the writer tells a vehicle owner the file moved. If EMS is not on, that is the first conversation, not an agent. If EMS is on and the folder is a junk drawer of ten years of estimates, that is a cleanup conversation. We would rather say that on minute twelve than discover it on day forty of a build.

If you run a collision center and you want to know what we can actually see in your CCC, that is an audit question. Bring the export settings. We will tell you what is there.