What is Classification Endpoint?
An API endpoint that provides Nice Classification data, helping users identify the correct trademark classes for their goods and services.
A classification endpoint is an API endpoint that provides access to trademark classification data, primarily the Nice Classification system, which is the international standard for categorizing goods and services in trademark registrations. The endpoint enables users to look up classification codes, search for appropriate classes based on product or service descriptions, retrieve detailed class descriptions, and understand the relationships between different goods and services categories.
The Nice Classification system, maintained by the World Intellectual Property Organization (WIPO), divides all goods and services into 45 classes: Classes 1 through 34 cover goods, and Classes 35 through 45 cover services. Each class contains a list of general descriptions and specific items that fall within that class. For example, Class 9 covers "computers, software, electronic instruments" among other items, while Class 25 covers "clothing, footwear, headgear."
A classification endpoint typically supports several operations. Class lookup retrieves the description and scope of a specific class number. Class search identifies relevant classes based on a text description of goods or services (for example, entering "mobile application" would return Class 9 and potentially Class 42). Goods and services search finds specific items within classes and returns the class number and official description. Class relationship analysis identifies classes that are frequently filed together or that courts have found to be related for likelihood of confusion purposes.
Why It Matters
Correct classification is fundamental to trademark registration and enforcement. A trademark application that specifies the wrong classes may fail to protect the goods or services the applicant actually offers, leaving gaps in protection. Conversely, an application that covers too many classes increases filing costs and may attract unnecessary oppositions. Identifying the right classes requires understanding the nuanced distinctions within the Nice Classification system, which is not always intuitive.
Classification also plays a critical role in clearance analysis and conflict assessment. Two marks that are identical in text may coexist peacefully if they are registered in completely unrelated classes. Two marks that are only moderately similar may be found confusingly similar if they are registered in the same or related classes. Understanding class relationships is therefore essential for accurately assessing trademark conflict risk.
The Nice Classification system is updated annually through periodic revisions that add new items, reorganize existing items, and modify class boundaries. These updates reflect changes in technology, commerce, and industry. For example, recent revisions have added specific descriptions for cryptocurrency, artificial intelligence, and other emerging technologies. Staying current with these changes is important for accurate classification.
For developers building trademark applications, the classification endpoint eliminates the need to maintain a local copy of the Nice Classification database. By accessing classification data through the API, applications always have access to the most current class descriptions and can provide classification guidance to users without the complexity of managing and updating classification data locally.
How Signa Helps
Signa's classification endpoints give access to the 45 Nice classes and to a catalog of accepted goods and services terms, with each term's acceptance at the offices Signa covers. Design codes for figurative elements are available through the same reference data.
Class suggestion accepts a plain-language description of goods, services or a business and returns ranked Nice classes with a confidence and a short rationale. For example, "cloud-based project management software" would typically point to Class 9 (downloadable software) and Class 42 (software as a service). Suggestions are a starting point, not a filing decision.
For drafting, Signa can produce a goods and services specification from a description, using only accepted terms, and can validate your own wording for one class: which terms each office accepts, the nearest accepted substitute for those it does not, and the character count.
For developers, the classification endpoints return the same consistent JSON format used across Signa's API, with pagination on the list endpoints.
Example
A startup accelerator builds a brand readiness tool for its portfolio companies. Founders describe their product in plain language, and the tool suggests the Nice classes for their trademark application.
When a founder enters "AI-powered fitness coaching app with personalized workout plans," the tool calls Signa's class suggestion endpoint, which might return Class 9 (downloadable mobile applications), Class 42 (software as a service) and Class 41 (fitness training services), each with a confidence and a rationale.
The tool then runs a search for the founder's proposed name in the suggested classes and lists any potential conflicts. It recommends professional legal review before filing: the classification suggestions and the search results are a starting point for that conversation, not a clearance opinion.