What is Status Codes?

API & Technical5 min readUpdated Mar 25, 2026

Standardized HTTP response codes and trademark lifecycle codes that communicate request outcomes and mark registration states in API interactions.

Status codes in the context of a trademark API operate on two levels. HTTP status codes are standardized three-digit codes returned with every API response to indicate the outcome of the request (success, client error, server error). Trademark status codes are domain-specific values that represent the current lifecycle stage of a trademark record (filed, published, registered, expired, abandoned, cancelled). Both types of status codes are essential for building reliable integrations with trademark data services.

HTTP status codes are organized into five categories. 2xx codes indicate success: 200 OK means the request was processed successfully, 201 Created means a new resource was created, and 204 No Content means the request was successful but there is no response body. 3xx codes indicate redirection. 4xx codes indicate client errors: 400 Bad Request means the request was malformed, 401 Unauthorized means authentication is missing or invalid, 403 Forbidden means the client lacks permission, 404 Not Found means the requested resource does not exist, and 429 Too Many Requests means the rate limit has been exceeded. 5xx codes indicate server errors: 500 Internal Server Error means an unexpected condition occurred, and 503 Service Unavailable means the server is temporarily unable to handle requests.

Trademark status codes represent where a mark stands in its lifecycle. While each trademark office uses its own status taxonomy, normalized trademark data services map these office-specific codes to a standardized set of values. Common normalized statuses include Filed (application submitted), Examined (under review by the office), Published (open for opposition), Registered (granted registration), Renewed (registration extended), Abandoned (applicant ceased prosecution), Expired (registration not renewed), and Cancelled (registration removed from the register).

Why It Matters

Correct handling of status codes is fundamental to building robust API integrations. An application that ignores HTTP status codes and blindly processes every response as if it were successful will display incorrect data, miss errors, and behave unpredictably. Conversely, an application that handles status codes properly can implement retry logic for transient errors, display meaningful error messages to users, and degrade gracefully when the API is unavailable.

HTTP status codes enable several important operational patterns. Rate limit management depends on detecting 429 responses and implementing appropriate backoff strategies. Authentication error handling depends on distinguishing 401 (invalid credentials, which require re-authentication) from 403 (insufficient permissions, which require a scope or plan upgrade). Client error handling depends on detecting 400 responses and parsing the error details to identify and fix the problematic parameter.

Trademark status codes are equally important because they determine what actions are available and appropriate for each mark. A mark with "Published" status is in its opposition window, requiring immediate attention from monitoring systems. A mark with "Registered" status has achieved full protection and may be approaching renewal deadlines. A mark with "Abandoned" status no longer blocks other applications in the same class. The status code drives the logic of portfolio management, monitoring, and enforcement systems.

The mapping between office-specific status codes and normalized values is a significant technical challenge. The USPTO uses over 100 distinct status codes, many with subtle distinctions that matter to practitioners. The EUIPO, WIPO, and other offices each have their own taxonomies. A reliable normalization must preserve the information content of these specific codes while providing a manageable set of standard values for cross-jurisdictional analysis.

How Signa Helps

Signa addresses both the HTTP and the trademark dimension. On the HTTP side, the API uses standard status codes consistently across endpoints, and every error shares one JSON format: an error object with a stable type (such as validation_error, not_found or rate_limited), a short title, the HTTP status, a detail message, a suggestion for fixing it, and retryable and retry_after fields, plus a top-level request_id. Validation errors list each problem in errors[].

The API uses specific codes deliberately. A search with no matches returns 200 with an empty data array, not 404. A request for a trademark ID that does not exist returns 404. A request with an invalid parameter returns 400 with details. A 429 carries a Retry-After header, and a 410 means a record was merged into another. Failed requests never consume credits.

On the trademark side, Signa maps each office's status codes into a structured status with four parts. status.primary is pending, active, inactive or unknown. status.stage gives the lifecycle position, such as filed, examining, published, opposition_period, registered, abandoned, refused, cancelled or expired. status.reason explains why a mark reached its state, and status.challenges lists pending proceedings such as opposition_pending. An office code Signa cannot map yet is reported as unknown, with the office's original code and label kept in status.raw.

Signa's monitoring watches can alert on status changes. Alerts are evaluated after each office sync, so a status change reaches you after the office publishes it and Signa ingests it.

Example

A law firm's automation system uses Signa's API to keep its portfolio tracking database current. Each night it refreshes the status of every mark in its clients' portfolios with batch retrieval, 100 marks per request.

Its error handling is built on the HTTP status codes. On 200 it updates the local records, and IDs returned in not_found are flagged for manual review. On 429 it waits for the time in the Retry-After header. On a 5xx response with retryable: true, it retries after a delay.

For trademark status, the system tracks changes over time. When a mark's status.stage moves from registered to expired, it alerts the responsible attorney and opens a task to check whether the renewal was skipped on purpose. When a mark moves to published, it records the opposition deadline in the firm's docketing calendar. Because the status fields are the same for every office, these rules work across all the offices Signa covers.