/uspto_trademarks/marks/search

POST /api/uspto_trademarks/marks/search

Price: 5 credits

Search the U.S. trademark register by keyword, with status and class filters

How to use it

Search the U.S. federal trademark register (USPTO) by keyword matched against the wordmark. Filter by status (live, dead, registered, pending, abandoned, cancelled) and by international/Nice class, and order by relevance, filing date, registration date, or serial number. Advanced search mode also matches owner name, translation, and goods/services. Each result includes the serial and registration numbers, wordmark, status, filing/registration/abandonment dates, mark type and design codes, classes, goods and services, owner details, and the mark image for stylized/design marks.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (matched against the wordmark) (minLength: 1)
• count integer required — Max number of results (min: 1)
• status string nullable — Filter by trademark status — live, dead, registered, pending (live but not yet registered), abandoned, or cancelled (one of: "live", "dead", "registered", "pending", "abandoned", "cancelled")
• nice_class string nullable — Filter by international (Nice) class, or 200 for US collective membership marks (one of: "001", "002", "003", "004", "005", "006", "007", "008", "009", "010", "011", "012", "013", "014", "015", "016", "017", "018", "019", "020", "021", "022", "023", "024", "025", "026", "027", "028", "029", "030", "031", "032", "033", "034", "035", "036", "037", "038", "039", "040", "041", "042", "043", "044", "045", "200")
• sort string — Result ordering (default: "relevance"; one of: "relevance", "filing_date_desc", "filing_date_asc", "registration_date_desc", "registration_date_asc", "serial_number_asc", "serial_number_desc")
• search_mode string — Search scope — basic matches the wordmark, advanced also matches owner name, translation, and goods/services (default: "basic"; one of: "basic", "advanced")

Response

• @type string (default: "UsptoTrademarksSearchResult")
• serial_number string required
• registration_number string nullable
• wordmark string nullable
• status_code integer nullable
• status_description string nullable
• is_alive boolean nullable
• is_registered boolean nullable
• filing_date string nullable
• registration_date string nullable
• abandon_date string nullable
• cancel_date string nullable
• first_use_date string nullable
• first_use_in_commerce_date string nullable
• mark_type array (default: [])
• mark_description array (default: [])
• is_standard_char_claimed boolean nullable
• drawing_code string nullable
• design_codes array (default: [])
• international_classes array (default: [])
• us_classes array (default: [])
• goods_and_services array (default: [])
• disclaimer string nullable
• current_basis array (default: [])
• owner_name array (default: [])
• owner_entity array (default: [])
• owner_citizenship array (default: [])
• owner_type array (default: [])
• image string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.