Current trademark status
Case-level state reported by USPTO for an application or registration. Read it with the status date and official text.
USPTO TSDR API Guide
TSDR API Status Codes: What Trademark and HTTP Codes Mean
Separate trademark lifecycle classifications from API transport errors. Learn how to read a current USPTO case state alongside its underlying prosecution events.
TSDR case workflow
- 1Known serial number
- 2Status + document lookup
- 3Source-backed verification
Data company workflowNormalize / qualify / verify / deliver
On this page
Direct answer
Two different types of 'status code'
When developers ask about TSDR API status codes, they often mean one of two unrelated fields: a USPTO trademark case status code inside the returned case data, or an HTTP response code describing whether the API request succeeded. A trademark status describes a legal and procedural state in an application or registration lifecycle. An HTTP status describes transport or gateway behavior.
For example, an HTTP 200 response can successfully deliver a record whose trademark status is abandoned, registered or otherwise inactive. Conversely, an HTTP 404 or 429 does not establish that the trademark itself is dead. Treat these as separate dimensions in every database, report and user interface.
Do not confuse HTTP response codes with trademark codes
| Code in the response | What to check |
|---|---|
| HTTP 200 | The request succeeded as a transport operation; inspect the returned serial and legal case status separately. |
| HTTP 401 / 403 | Access or authentication failure. Check required API-key header, valid authorization, permissions and route. |
| HTTP 404 | Endpoint or identifier/path unavailable; confirm the requested resource before declaring that the mark is dead. |
| HTTP 429 | Rate control / too many requests; use the published quota limits and controlled retries. |
| HTTP 500 / 502 / 503 | Possible temporary upstream/server failure; log and retry conservatively only where appropriate. |
| USPTO status 641 | Historic trademark STATUS/EVENT: Non-final action mailed. It is not an HTTP 641 response. Recheck current case status and event date. |
| Trademark DEAD | Case-level status/lifecycle description: not a synonym for network failures or automatic legal availability. |
Trademark status versus HTTP response
Case history event
A prior action such as an Office Action, applicant response, publication, registration or abandonment entry. History is not the same as the present state.
HTTP 200
A successful API transport response. It does not confirm a mark is live, available to use or legally valid in all contexts.
HTTP 401 or 403
The gateway is declining a request. Review credential status, authorization, endpoint and the response body before assigning a cause.
HTTP 404
The requested API resource may be missing or the identifier/path wrong; investigate before claiming that no trademark exists.
HTTP 429
The request may be rate-limited. Adjust the request queue and honor applicable retry instructions.
How to interpret case status correctly
Identify the record
Capture the serial or registration number and confirm that the returned record is the intended application or registration.
Read the current status
Use the official current status description and code where available, not only the newest text event.
Capture the status date
Store the date associated with the state and distinguish it from filing or document mailing dates.
Inspect the event history
Review relevant events and documents to understand how the state was reached and whether a newer filing changes interpretation.
Cross-check underlying evidence
For Office Actions or other event-specific prospects, examine the actual public document before describing its legal significance.
Record retrieval freshness
Save the retrieval timestamp and avoid presenting an old snapshot as real-time information.
Examples of incorrect versus careful interpretation
Incorrect: any Office Action means the case is currently under an Office Action
Careful: an Office Action may be part of history while the current status has since changed. Confirm the present case state and most recent documents.
Incorrect: DEAD means the mark is free for anyone to use
Careful: USPTO 'dead' reflects federal application/registration status and does not resolve common-law rights, confusing similarity or availability.
Incorrect: an application is abandoned because a deadline appears old
Careful: official abandonment state and timing require current USPTO evidence; a calendar estimate alone is not definitive.
Incorrect: HTTP 403 proves a permanently banned key
Careful: authentication, permissions, endpoint configuration or access controls can each produce an authorization failure.
Direct answer
Using status codes in prospect monitoring
A commercially useful lead or monitoring system often needs more than a one-code filter. It may need current status, the event that triggered interest, its date, goods/services, classes, representation information and a link back to the source record. A status-code query is a starting point for research, not a complete qualification decision.
Avoid automatically treating public correspondence fields as verified business contacts. A mailing address or attorney-of-record entry can refer to different people and roles. If you are identifying prospects, describe the source data accurately and verify relevant facts before outreach.
Case status is not legal advice
Trademark status codes describe USPTO records and processes. They are not a substitute for a trademark clearance search, legal review or examination of relevant rights. Use the USPTO's official explanations and current record as the authority.
Trademark status codes describe USPTO records and processes. They are not a substitute for a trademark clearance search, legal review or examination of relevant rights. Use the USPTO's official explanations and current record as the authority.
Questions about TSDR status codes
Does a status code tell me whether a trademark is live or dead?
A case-status record may contain a live/dead indication and descriptive state. Review the code together with the official text, date and case history.
Does HTTP 404 mean the application is abandoned?
No. HTTP 404 concerns retrieval of a resource, not the trademark lifecycle state.
Can I build alerts on status changes?
Yes, a monitoring workflow can compare recorded case snapshots over time when use of the API is authorized and rate-limited appropriately.
Can an old event be the basis for an outreach claim?
Not without confirming present relevance. Always distinguish historical events from current facts.
Should I interpret status codes without reviewing documents?
For broad preliminary analysis, a status field may help, but legal/procedural claims should be checked against the underlying record and applicable source documents.
Is code 641 an HTTP error?
No. 641 is a historic USPTO trademark status/event code, describing a non-final action mailed; it should not be confused with HTTP transport errors such as 429.
Does HTTP 200 mean the trademark application is live?
No. HTTP 200 means that the network/API request succeeded. The returned record may indicate a dead, abandoned, registered or otherwise specific trademark status.
Need programmatic USPTO case access?
For public TSDR case-status, document and image retrieval, our reviewed API-key access request starts at $20 per key. Describe your use case before payment details are provided.