What is API and can it help track my case?
Maybe the most frustrating thing about having a case pending with USCIS is the waiting. Even “fast cases” take months to adjudicate, but the vast majority are often much, much longer…sometimes even stretching on for years. So it natural that you want to know what is going on with your case and where it’s at in it’s life cycle. Enter API, or Application Programming Interface. API is a tool developers use to allow two separate programs to “speak” to each other and share information. For USCIS and case updates, API lets 3rd party applications have access to specific entries USCIS uses to let applicants know when there’s an update. Let’s talk some about what API means for USCIS tracking.
The API updates correspond to internal USCIS History Action Codes or HACs. A HAC is used for many purposes in the agency; for example, it can trigger an action such as card production or provide an history marker for an officer to see where a case is located at. HACs are also used to move cases around various processing queues and a lot are completely automated in how and when they are placed. Each application type (I-485s, I-765s, ect) have their own set of HACs and while some can be used for multiple types, others are specific for the case type and even a specific sub-category (e.g. Employment-Based I-485s may have their own HACs separate from Family-Based I-485s). There are also specific HACs for individual adjudication systems a case is processed in. The two most common systems are an older system (CLAIMS3) and a new one (ELIS). CLAIMS3 cases will have a three letter start to their receipt number (e.g. MSCxxx) while ELIS has IOE at the start of the receipt number. More HACs are automated in ELIS than CLAIMS3. As you can imagine, there are hundreds and hundreds of HACs and even for experienced officers, it can be hard to keep track of each HAC and when and how it is used.
So for an applicant, how useful is it to know or track API updates. In truth, not very useful at all. API only updates what is publicly available to an applicant; so essentially only case status updates the applicant would normally get. The vast majority of HACs aren’t visible to developers to update their 3rd party apps. And even if they were, it’s not likely most applicants would understand what specific action gets taken on their case. When I was an officer in the customer service division of the National Benefits Center, I would sometimes not understand what a specific HAC meant or why it was entered when it was….even with having our own list and definitions! There are also times when a system or an officer/analyst will enter a HAC by mistake or out of order, causing additional confusion or issues with a case.
My best advice: pay attention to your USCIS case status when you get notifications and don’t try to guess what is going on with your case by tracking API.
