Control numbers are now deprecated for JSON eligibility and claim status APIs

The controlNumber request body field is now deprecated in the following JSON API endpoints:

• JSON Real-Time Eligibility Check

• Batch Eligibility Check

• JSON Real-Time Claim Status Check

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.