Skip to main content

AK2 — Transaction Set Response Header

X12 AK2 in 997 acknowledgements: ties acceptance or rejection to a specific ST control number from your outbound document.

AK2 segment facts

  • AK202 must match the ST02 control number you assigned when posting the original outbound document.
  • Multiple AK2 loops can appear in one 997 when a functional group carried several transaction sets.
  • API status polling and webhooks key off AK2/ST correlation to mark individual documents accepted or rejected.

What the AK2 segment does

AK2 loops inside a 997 for each transaction set acknowledged. AK201 is the transaction set ID; AK202 matches your ST02.

Loop: Once per acknowledged transaction set

Common transaction sets: 997

Key elements

ElementNameDescription
AK201Transaction set ID850, 856, 810, etc.
AK202Transaction set control numberEchoes ST02 from the original document.

Example AK2 segment

AK2*850*0001~

Parse and validate samples with the free EDI validator or send JSON via the JSON→X12 mapping guide.

Related reference

Frequently asked questions

Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.

SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.

HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees

Operations teams

A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.

Healthcare billing

837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.

Developer teams

JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.

Preview case studies

© 2026 CCCM Consulting LLC. All rights reserved.