What is Bulk Search?

API & Technical5 min readUpdated Mar 25, 2026

An API operation that processes multiple trademark search queries in a single request, enabling efficient large-scale trademark screening.

Bulk search is an API operation that allows clients to submit multiple trademark search queries in a single API request and receive aggregated results. Rather than making individual API calls for each search term, which consumes rate limit quota and introduces latency from multiple round trips, bulk search consolidates these operations into a single request-response cycle. This approach is essential for applications that need to screen large numbers of brand names, product listings, or other trademark-sensitive content efficiently.

A bulk search request typically includes an array of search terms along with shared parameters such as target jurisdictions, Nice Classification codes, similarity thresholds, and result limits. The API processes all queries against the specified parameters and returns a structured response that maps results to each input query. Some implementations process bulk queries in parallel on the server side, achieving total processing times that are substantially less than the sum of individual query times.

Bulk search operations may be synchronous or asynchronous depending on the volume. Small batches of 10 to 50 queries may return results in a single synchronous response. Larger batches of hundreds or thousands of queries may be submitted as asynchronous jobs, with the client receiving a job identifier that can be used to check status and retrieve results when processing is complete.

Why It Matters

The need for bulk trademark search arises in numerous practical scenarios. E-commerce platforms need to screen product listings for potential trademark conflicts before they go live. Brand consultancies conduct naming projects that require evaluating dozens of candidate names across multiple jurisdictions. IP departments perform periodic portfolio audits that require searching for all company brands and their variants. Brand protection services need to sweep the trademark register for potential infringements against a large portfolio of client marks.

In each of these scenarios, making individual API calls for each query is inefficient and often impractical. A naming project evaluating 50 candidate names across 10 jurisdictions would require 500 individual API calls. A product listing screening service processing 1,000 new listings per hour would need 1,000 calls per hour. A portfolio audit covering 300 brands across 50 jurisdictions would require 15,000 calls. Bulk search reduces these to a manageable number of requests.

The efficiency gains extend beyond rate limit conservation. Network latency, which adds 50 to 200 milliseconds per request, accumulates significantly across thousands of individual calls. Bulk search amortizes this overhead across all queries in the batch. Server-side processing can also be optimized for batch operations, leveraging parallel execution, shared index access, and result caching more efficiently than sequential individual queries.

For real-time applications like e-commerce screening, bulk search enables batch processing of newly listed items during periodic sweeps rather than requiring a synchronous check on every individual listing. This approach balances thoroughness with performance, ensuring that all listings are screened without introducing latency into the listing creation workflow.

How Signa Helps

Signa has no separate bulk search job. Large-scale work uses a few documented building blocks instead:

  • Several names in one search. The search endpoint accepts q as a list, such as every spelling of a mark you are screening. Up to 100 names fit when similarity is only identical and lookalike; with fuzzy, embedded or phonetic (including the default channels) the limit is 10 names. Matching marks come back in one ranked list, and match.terms names the names that found each one.
  • Batch retrieval. POST /v1/trademarks/batch resolves up to 100 trademark IDs or office identifiers in one request, returning matched records in data and the rest in not_found.
  • Reconciliation. POST /v1/reconcile compares up to 100 of your own records per call against the register, field by field.
  • Pagination. Larger result sets page through with a cursor at up to 100 results per page, and the TypeScript SDK follows the cursor for you.

Larger volumes are split into chunks on the client side and sent with controlled concurrency. Each plan has a per-minute rate limit (60 requests a minute on Free up to 3,000 on Scale for most endpoints), and every action draws credits from one pooled balance at its listed price. See the pricing page and the rate limits documentation for current figures.

Example

A brand consultancy is choosing a name for a client and has a shortlist of variants of one coined word: different spellings, a hyphenated form and a version with a common suffix. Instead of one search per variant, it sends the variants as a list in q, with the client's Nice classes and target jurisdictions as filters.

The single ranked result shows which existing marks resemble any of the variants, and match.terms shows which variant found each one. The consultancy's analyst reviews the hits, drops the variants with obvious conflicts, and passes the rest to a trademark attorney for a full clearance opinion. For a portfolio audit later in the project, the same team uses batch retrieval to refresh the client's own registrations 100 at a time.