USCIS case data guide
USCIS API Check: How to Get and Read Your Case Data
To check your own USCIS account data, sign in on myUSCIS, open a case-data link for a receipt associated with that account, then copy the JSON into the free reader. This website does not sign in or fetch case records for you.
Official sources and what they support
- USCIS — Contact Center: online accounts and case assistance ↗
Account support, case-linking assistance and official case-information channels.
- USCIS — Case Status Online ↗
Official case-status verification for a receipt; not a specification of account JSON or event codes.
- USCIS — Torch API Developer Portal ↗
The official Case Status API and developer onboarding; distinct from our user-import workflow.
Our import steps, field checks and timestamp calculations describe this product. These sources do not certify our software or provide an official mapping of internal account endpoints.
Which USCIS API check do I need?
Applicants often use “USCIS API” to mean data loaded by their own account. Developers may mean the separate official Torch API. These have different access arrangements. This guide covers the applicant workflow; use the API comparison guide for developer access.
How do I get my own case data?
Use the same browser for myUSCIS and the data links. The reader provides a link builder for IOE receipts; it sends your browser directly to the official host. Availability depends on your account, receipt and the current account interface.
- Sign in at my.uscis.gov and confirm the case is associated with your account.
- Open the free reader and enter your own IOE receipt in the case-data guide.
- Choose Status data. In the official tab, copy the complete JSON response, including its enclosing braces.
- Return to the reader and choose Paste my data, or paste manually and select Analyze free preview.
- Optionally add Case events and Documents for this same case. Confirm matching receipts before combining exports.
Which export goes in which input?
Status data can be pasted into the main input for a recognized status and history. The optional Case events input adds events, filing context and record timestamps. If you start with Case data instead, use the optional Status & office input. Documents can add supported categories and dates. These are complementary exports of the same application.
A missing field means this export does not supply it. It does not prove there are no notices, no requests or no case activity. Never fill gaps by copying another person’s case.
Why do I see null, a login page or an error?
First check that your account is still signed in, the receipt is correct and the case is linked to that account. A login page is HTML, not case JSON. A null response cannot be analyzed as an empty case.
Account endpoints are not a published stable developer contract. Their paths or responses can change. If a link stops working, use the normal account interface and official notices; do not share cookies, passwords or access tokens to obtain help.
Can I do this on a phone?
Yes, when the browser displays the response as selectable text. Copy the complete response and return to the reader in another tab. If selection is difficult or the response is a sign-in screen, use a desktop browser or the official account interface instead. No extension is required by this reader.
What should I review after analysis?
Start with the recognized status and action flag, then inspect dated events and missing-data warnings. Event labels describe recorded operations, not guaranteed present status. A report can add cross-field checks and an earlier-export comparison, but it cannot create missing agency data.
The endpoint structure is documented in first-hand community observations linked below. That reference is not an official USCIS guarantee that these links work for every case.
Additional technical references
Official resources control case instructions. Community schema observations describe a limited observed format and are identified separately.