Suggest Classifications
Classifications
Suggest Classifications
Suggest Nice classes for a description of goods, services, or a business — classes only, no wording
POST
Suggest Classifications
Overview
Turn a description of goods, services, or a business into ranked Nice classification classes with confidence and rationale — ideal when you just need to know which classes apply (for filter UIs, watch setup, clearance pre-screening, or portfolio analysis). Works for company descriptions (“SaaS tool for HR teams”), product listings (“men’s athletic running shoes, cushioned sole”), service offerings (“on-site SEO audits”), and anything in between. Ambiguous inputs like “coffee company” come back with anambiguous flag, a clarifying question, and classes for every plausible interpretation, so you can surface the question to your user and re-submit.
Need paste-ready goods/services wording per class for a filing? Use Suggest Goods & Services instead — same input, but returns each class with grounded
accepted_terms from the pre-approved catalog.Body Parameters
Description of the goods, services, or business (3-500 characters). Natural-language, no special format.
Nice Classification is a WIPO international standard — the 45 classes are the same in every member jurisdiction, so this endpoint deliberately takes no jurisdiction hint. If you need jurisdiction-biased goods/services wording, use Suggest Goods & Services, which accepts an optional
jurisdiction_code that influences term selection (not the class list).Response
Always
classification_suggestion.The description you submitted, echoed back.
Version tag of the classifier that produced this response.
Ranked suggested classes. Each class contains the fields below.
Nice class number (1-45).
Canonical class title.
One of
high, medium, or low.1-indexed position in the returned ordering.
One of
core, conditional, or adjacent.When
recommendation_type is conditional, the condition under which this class applies. May be null.Short explanation of why this class was suggested.
true when the description has two or more materially different filing strategies.When
ambiguous is true, a question to ask the user. May be null.Billing
Billed as 1 unit (search endpoint type).
Code Examples
Errors
| Status | Type | Description |
|---|---|---|
| 400 | validation_error | description missing, shorter than 3, or longer than 500 chars |
| 401 | unauthorized | Missing or invalid API key |
| 403 | forbidden | API key lacks trademarks:read scope |
| 502 | upstream_error | Classification service temporarily unavailable |
Related Endpoints
- Suggest Goods & Services — same input, returns classes with filing-ready wording
- List Goods & Services — browse/search the pre-approved terms catalog
- List Classifications
- Get Classification