Understanding API status codes and their meanings

I came across some useful resources that help decode what different API status codes actually mean for your case, even when the main website doesn’t show any changes yet.

There are two main resources that work together. First, there’s a documentation page that lists all the possible status codes with their definitions. Second, there’s an API endpoint that shows current case information including these status codes.

Here’s how it works: when you check your case through the API, you’ll see something like "statusCode": "AB" in the response. You can then look up what “AB” means by finding it in the documentation. For instance, if you see "statusCode": "AB" in your API response, searching for “AB” in the docs might show you it means “APPLICATION RECEIVED AND UNDER REVIEW”.

This method is really helpful because sometimes your case status changes internally before it gets updated on the public website. The API often reflects these changes faster.

Thought this might be useful for others trying to track their case progress more accurately.

Been using this for eight months - definitely worth it. The API saved me from calling support constantly when my case looked stuck on the website. Some status codes show when documents are actually being reviewed vs just sitting in queue. The timing difference is huge - sometimes weeks between internal updates and what you see on the portal. Fair warning: not all codes are explained in the docs, so you’ll hit cryptic ones that need detective work or forum hunting. Don’t go crazy with API calls though - too many requests might flag your case for weird activity.

Wow, didn’t know this existed - thanks for sharing! Just tried it and my case shows a different code than what’s on the website. I’m kinda nervous tho - is it safe to keep checking the API or could it mess with my app? Also having trouble finding some newer codes in the docs. Seems like they add new ones but don’t update the docs right away.

This is a game changer if you’re stuck with slow processing times. Found this method six months ago when my case sat for weeks with zero updates on the main portal. The API showed I’d actually moved through three internal stages during that time. Just heads up - some status codes are temporary and vanish within hours or days. Got burned when I celebrated a good-looking code that disappeared overnight. Check periodically but don’t obsess over every tiny change. The docs are pretty technical at first, but you’ll get the hang of how codes work. Remember that internal changes don’t always mean you need to do anything right away.

This topic was automatically closed 4 days after the last reply. New replies are no longer allowed.