Control numbers are now deprecated for JSON eligibility and claim status APIs
Sep 15, 2025
The controlNumber request body field is now deprecated in the following JSON API endpoints:
The controlNumber field is now optional. We don't recommend specifying the controlNumber field in requests.
About interchange control numbers
In the underlying X12, an interchange control number is used by payers to detect duplicate transaction submissions. Many payers enforce strict uniqueness rules for interchange control numbers.
When you use Stedi's JSON APIs – like those above – Stedi generates valid, unique interchange control numbers when we translate your JSON API request to X12. We ignore the controlNumber field in the JSON request.
For more information, see our Control numbers in X12 EDI blog.
The controlNumber request body field is now deprecated in the following JSON API endpoints:
The controlNumber field is now optional. We don't recommend specifying the controlNumber field in requests.
About interchange control numbers
In the underlying X12, an interchange control number is used by payers to detect duplicate transaction submissions. Many payers enforce strict uniqueness rules for interchange control numbers.
When you use Stedi's JSON APIs – like those above – Stedi generates valid, unique interchange control numbers when we translate your JSON API request to X12. We ignore the controlNumber field in the JSON request.
For more information, see our Control numbers in X12 EDI blog.
Get started with Stedi
Get started with Stedi
Automate healthcare transactions with developer-friendly APIs that support thousands of payers. Contact us to learn more and speak to the team.
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Get updates on what’s new at Stedi
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Developers
Resources
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.
Get updates on what’s new at Stedi
Backed by
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.