USCIS case data guide

USCIS Case Status API: Official Developer Access vs Account Data

USCIS operates an official Case Status API through its Torch Developer Portal. Applicants also use “USCIS API” for data visible through their own myUSCIS session. CaseStatusTracker reads data you provide; it does not sell official API access.

By CaseStatusTracker

Official sources and what they support

USCIS — Torch API Developer Portal ↗
The official Case Status API and developer onboarding; distinct from our user-import workflow.
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.

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.

What is the official USCIS Case Status API?

The USCIS Developer Portal lists a Case Status API for customers and representatives who need regular access to case-status information. Its published onboarding includes developer registration, app credentials, sandbox development and a production-access process.

Use the portal documentation for current authentication, limits and approval requirements. A key or sample from an unrelated website is not authorization to access the official service.

How is myUSCIS account data different?

The account website loads records for cases associated with a signed-in account. Community observers have documented JSON responses containing events, notices and status fields. These account routes are distinct from the documented Torch developer service.

A browser session is not a developer API credential. Do not send it to this website, place it in a script shared with others, or assume it authorizes access to unrelated receipts.

Which option fits my task?

For one person reading their own timeline, use the official account and an optional local JSON reader. For building an application that regularly requests public case-status information, start with the official developer onboarding.

This site currently offers a free supplied-data analysis and an optional one-time report. It does not offer a bulk API, automated USCIS polling, developer keys or an official USCIS integration.

Can either source prove an approval date in advance?

An API response can contain a recorded status or operation. It cannot establish a future decision date from an unexplained timestamp or code. Read the actual decision notice for the application concerned.

Fields present in an account export may be absent from another source. Compare what each source actually supplies rather than assuming that every API exposes the same record.

How should I handle access problems?

Developers should use the support and access process in the Torch portal. Applicants should use myUSCIS account support for login or case-linking issues. A JSON parsing problem can be reported to this site using only the field name and error message, without credentials or original case data.

What can I learn from my own case data?

Read your supplied status, supported event definitions and missing-data warnings for free. No sign-in is required for local analysis.

Analyze my case data ↗

The optional detailed report adds cross-field checks, evidence explanations and an earlier-export comparison when supplied. Review the complete fictional sample before deciding.

See the report sample ↗ · Review pricing and included features ↗

Additional technical references

Official resources control case instructions. Community schema observations describe a limited observed format and are identified separately.