# T039 — Flock-Axon API Rupture vs NLRPD v3 Integration Path The LRPD corpus preserves dueling January-February 2025 vendor letters describing a broken Axon-Flock integration relationship and a cutoff for new mutual customers. NLRPD's later October 2025 email documents a new Flock API v3 route for sending hot alerts into Fusus after the legacy interface ended. The evidence may describe different customer cohorts, contract states, functions, or API versions, but the later record prevents reading the rupture as a universal technical shutdown. ## Statement A Flock CEO Garrett Langley told LRPD that "Axon will no longer support new mutual customers starting July 24, 2025. They may continue to support existing customers, but it's unclear to what degree" (`PDFOI-2026-1874`, `Emails 36-63.pdf`, p. 795). Axon CEO Rick Smith separately alleged that Flock was "flat out refusing to allow Axon Fusus customers to have ALPR Search integrations from their own Flock cameras" (`PDFOI-2026-1874`, `Emails 36-63.pdf`, p. 790). See [[Flock-Axon API Dispute and the Dual RTCC Stack]]. ## Statement B On October 14, 2025, Axon account executive [[Jasmine Norton]] told NLRPD that "Flock sunset their legacy API integration for sending hot alerts into the Fusus platform on September 30th" but "Flock has transitioned to a new API (v3)." She supplied an activation route and said turnaround was typically about 24 hours. Sgt. [[William G. Jones]] replied that he would work on getting the information to the helpdesk (`Fusus Flock Integration Update into Fusus.pdf`, pp. 1-2). See [[North Little Rock Flock-to-Fusus API v3 and Axon Drone Pitch]]. ## Why it matters The scope of the rupture determines what can defensibly be said about agency control, lock-in, and continuity. If existing mutual customers retained or regained hot-alert integration through v3, the dispute may have constrained new customers or particular search functions without terminating every existing feed. If NLRPD never activated v3, the message documents only an offered route. LRPD's own post-cutoff status remains unresolved. ## Resolution status **Open.** The records establish both the vendor rupture narrative and a later v3 migration path, but they do not identify NLRPD's contractual cohort, confirm activation, distinguish hot-alert delivery from ALPR search, or establish LRPD's own outcome. ## Discovery Discovered during the 2026-07-29 ingest of NLRPD `PDFOIA-2026-1331`, when the October 2025 v3 email was compared with the earlier LRPD vendor letters. ## Notes - "Hot alerts into Fusus" and "ALPR Search integrations" may be technically distinct capabilities. - "New mutual customers" leaves open how the vendors treated customers with an existing live or contracted deployment.