API Related FAQs
- 24 Articles
- Published on Aug 28, 2026
Claim.MD provides an API service that allows you to generate an ANSI X12 5010 837 file containing claims that were transmitted through Claim.MD on a specified date. What claims can be downloaded? You can retrieve transmitted claims in the follow...
- Updated on Oct 29, 2026
- Published on Aug 21, 2026
What does Reset API Download do in View ERA? For accounts that retrieve Electronic Remittance Advice (ERA) through the API, the Reset API Download option in View ERA works similarly to Send to SFTP . It allows an ERA to be made available for ...
- Published on Aug 20, 2026
Organizations often run an existing SFTP-based vendor integration alongside a new API integration during system transitions. The following FAQs explain how ERA retrieval, claim submission, identifiers, and API key management work when multiple syste...
- Updated on Aug 20, 2026
- Published on Aug 20, 2026
1. Are the API endpoints different in production? No. All API URLs are the same for both test and production accounts. There is no separate production host. Continue using: https://svc.claim.md The existing API service paths also remain the sa...
- Updated on Mar 10, 2026
- Published on Mar 10, 2026
Question: Is there any API method we can use to differentiate on our end whether the ERA payment was issued by check, ACH, EFT, or another payment type? Answer: Yes. The Claim.MD ERA API returns a field called payment_method that identifies...
- Published on Jan 5, 2026
Question: How can I trigger webhook events to test my development or staging endpoint? Answer: To generate test webhook events, you can use the provider enrollment workflow through the Claim.MD API: Submit a provider enrollment request usi...
- Updated on Feb 10, 2026
- Published on Feb 10, 2026
1. Are test eligibility responses mocked? Yes. In the test environment, the Eligibility API always returns the same sample response, regardless of the payer or the member data submitted. This behavior is intentional and is designed to allow you t...
- Updated on Feb 4, 2026
- Published on Feb 4, 2026
Not directly. While Claim.MD does provide an API-driven enrollment workflow, the enrollment URLs generated by the API are intentionally short-lived and are not designed to be emailed or stored for later use . This distinction is especial...
- Published on Jan 14, 2026
Question: In the API payer list, why do some payers show an average ERA enrollment time of 0 days? Answer: An average ERA enrollment time of 0 days means that Claim.MD does not yet have enough historical data to calculate a reliable estim...
- Published on Jan 14, 2026
Question: In ERA responses, each claim includes a status_code . Where can I find the definitions for these values, and what do they represent? Answer: The status_code field returned at the claim level in ERA API responses indicates the pay...
- Published on Jan 5, 2026
Question: How should I interpret the avg_era_enroll_days value returned in the Claim.MD API payer list? Answer: The avg_era_enroll_days field represents the average number of days it typically takes for Electronic Remittance Advice (ERA) ...
- Published on Jan 5, 2026
Question: Is it possible to archive claims through the Claim.MD API, and what information is required? Answer: Yes. Claims can be archived using the Claim.MD API, which is designed to communicate with Claim.MD through a custom-built application...
- Published on Jan 5, 2026
Question: Is it possible to retrieve all data from an 835 Electronic Remittance Advice in CSV format using the Claim.MD API? Answer: No. At this time, there is no method to capture all data from an 835 file in CSV format through the Claim.M...
- Published on Jan 5, 2026
Question: Does Claim.MD provide a separate API endpoint for sending secondary claims? Answer: No. Claim.MD does not offer a separate API specifically for submitting secondary claims. Secondary claims are submitted the same way as primary claim...
- Updated on Jan 13, 2026
- Published on Jan 5, 2026
Question: Do providers need to be pre-enrolled in Claim.MD before submitting eligibility requests through the API? Answer: No. Providers do not need to be pre-enrolled in Claim.MD in order to submit eligibility requests through the API. Eligib...
- Published on Jan 5, 2026
Question: How are Remittance Advice Remark Codes (RARC) represented in Claim.MD API responses? Answer: In Claim.MD API responses returned in JSON or XML format, RARC codes are included at the claim level within the claim array. Each RARC...
- Published on Jan 5, 2026
Question: Does Claim.MD support X12 transactions such as 276, 277, 278, or 999 through the API? Answer: Claim.MD handles claim status and acknowledgments differently than traditional X12 workflows: 276 (Claim Status Request): A 276 request...
- Published on Jan 5, 2026
Question: Is the Claim.MD API intended to function as a remote or embedded version of the Claim.MD user interface? Answer: No. The Claim.MD API is not designed to replicate or replace the Claim.MD user interface. Instead, the API provides a da...
- Published on Jan 5, 2026
Question: Is there an API endpoint for starting a provider enrollment from my application? Answer: Yes. The Enrollment Request API is designed specifically to initiate provider enrollments through your application. Using this endpoint, you s...
- Published on Jan 5, 2026
Question: Can I use the Claim.MD webhook to receive Electronic Remittance Advice (ERA) events? Answer: No. The Claim.MD webhook currently returns events related only to enrollment and appeals . ERA events are not included in webhook notifica...
- Updated on Jan 13, 2026
- Published on Jan 5, 2026
Question: Can I submit real-time eligibility requests in a batch, or should each patient be submitted individually? Answer: For real-time eligibility using the Claim.MD API, each eligibility inquiry should be submitted one patient at a time . ...
- Updated on Jan 13, 2026
- Published on Jan 5, 2026
Question: What does remote_chgid represent in the Claim.MD API, and how should it be formatted? Answer: remote_chgid Overview The remote_chgid (charge ID) is a value you supply in your JSON claim submission to unique...
Why don’t I receive benefits when submitting multiple service codes in a single eligibility request?
- Updated on Jan 5, 2026
- Published on Jan 2, 2026
Question: Can I include more than one benefit or service code in a single eligibility request using the Claim.MD API? Answer: Yes, the Claim.MD API supports including multiple benefit or service codes in a single eligibility request, and those ...
- Published on Jan 5, 2026
Question: How can I tell from the eligibility response whether a deductible applies to a specific benefit? Answer: In an eligibility response, each benefit can include its own deductible indicators . Deductible information is returned at the i...