---
title: "Using SFTP and API Integrations on the Same Claim.MD Account"
slug: "using-sftp-and-api-integrations-on-the-same-claim-md-account"
updated: 2026-08-20T16:15:58Z
published: 2026-08-20T16:15:58Z
canonical: "docs.claim.md/using-sftp-and-api-integrations-on-the-same-claim-md-account"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claim.md/llms.txt
> Use this file to discover all available pages before exploring further.

# Using SFTP and API Integrations on the Same Claim.MD Account

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 systems share the same Claim.MD account.

---

## Can an SFTP vendor and an API integration both retrieve ERAs from the same account?

- Yes, both can operate at the same time.
- API ERA downloads do **not** affect SFTP-delivered ERA files.
- Each method works independently:
  - SFTP vendor continues receiving ERA files as usual
  - API system can also retrieve the same ERAs
- No ERAs are removed or blocked by API retrieval

---

## How can an API integration start retrieving ERAs without pulling full history?

- Use one of the following approaches to set a starting point:
  - **Option 1: Claim.MD Web Portal**
    - Open a recent ERA
    - Hover over the check number
    - Copy the `view=######` value
    - Use that as the starting `ERAID`
  - **Option 2: API ****`eralist`**** with date filter**
    - Use `ReceivedAfterDate` to limit results
    - Select an ERAID from the returned list
- After initial setup:
  - Store `last_eraid`
  - Pass it in the next `eralist` request
  - Only ERAs with a higher ERAID will be returned
- This enables incremental ERA retrieval going forward
- API docs: [https://api.claim.md](https://api.claim.md/)
- Endpoint: `eralist`

---

## Can two systems submit claims during a cutover on the same account?

- Yes, both systems can submit claims independently
- Each submission is treated as a unique claim with its own response
- Claim.MD does not flag duplicates based on submitting system alone
- Important considerations:
  - Payers may still deny or flag duplicate services (same patient/date/CPT)
  - ERAs will include claims from both systems without separation
  - A clear cutover date is strongly recommended to avoid overlap
- Reference: [https://docs.claim.md/docs/how-to-use-two-software-systems-with-the-same-claimmd-account](https://docs.claim.md/docs/how-to-use-two-software-systems-with-the-same-claimmd-account)

---

## Is `remote_chgid` returned on ERA/835 service lines?

- In most cases, yes:
  - The payer returns the submitted `remote_chgid` on the matching 835 line
- However:
  - Some payers may not return it consistently
  - It should not be the only matching method used
- Recommended fallback matching:
  - Claim ID
  - CPT/procedure codes
  - Service line/charge details
- References:
  - [https://docs.claim.md/docs/test-account-quickstart-guide](https://docs.claim.md/docs/test-account-quickstart-guide)
  - [https://docs.claim.md/docs/what-is-remote-chgid-and-are-there-formatting-requirements](https://docs.claim.md/docs/what-is-remote-chgid-and-are-there-formatting-requirements)

---

## Can the API key be rotated without affecting an SFTP vendor?

- API key rotation is supported, but requires coordination
- Key points:
  - SFTP itself is not directly impacted
  - Vendors may still rely on the API key for other functions (e.g., eligibility)
  - Claim.MD supports **one API key per account**
  - Rotating the key replaces the existing credential
- Before rotating:
  - Confirm whether any vendor or system uses the API key
  - Update all affected systems immediately after rotation