Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.signa.so/llms.txt

Use this file to discover all available pages before exploring further.

You are an IP litigation associate responsible for monitoring 30 active TTAB (Trademark Trial and Appeal Board) proceedings for your firm’s clients. Some of your clients are opponents; others are respondents. You need to track proceeding status changes, flag new oppositions filed against your clients’ marks, and maintain an overview of all active cases. This guide shows how to build an opposition monitoring system using the Signa API.

​
Prerequisites

  • A Signa API key with trademarks:read scope
  • Client owner IDs or a list of marks to monitor
1

Find all proceedings involving your clients

Start by querying proceedings where your client appears as a party — either as the opponent (your client filed the opposition) or the respondent (someone opposed your client’s mark).
# Find proceedings where your client is the respondent (someone opposed their mark)
curl "https://api.signa.so/v1/proceedings?party_owner_id=own_client01&party_role=respondent&status=pending&limit=50" \
  -H "Authorization: Bearer $SIGNA_API_KEY"

# Find proceedings where your client is the opponent (they filed the opposition)
curl "https://api.signa.so/v1/proceedings?party_owner_id=own_client01&party_role=opponent&status=pending&limit=50" \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Expected output:
{
  "object": "list",
  "data": [
    {
      "id": "prc_op001",
      "proceeding_type": "opposition",
      "proceeding_number": "91278456",
      "status": "pending",
      "office_code": "uspto",
      "filed_date": "2026-01-10",
      "decision_date": null,
      "parties": [
        { "owner_id": "own_other99", "name": "Apex Global Corp", "role": "opponent" },
        { "owner_id": "own_client01", "name": "Meridian Labs Inc.", "role": "respondent" }
      ],
      "contested_classes": [9, 42],
      "trademark_id": "tm_merid01"
    }
  ]
}
2

Get details on the contested marks

For each proceeding, fetch the full trademark detail to understand what is at stake.
# Get the contested trademark
curl https://api.signa.so/v1/trademarks/tm_merid01 \
  -H "Authorization: Bearer $SIGNA_API_KEY"
3

Surface marks most exposed to opposition

Pull each client’s pending and published marks — the stages most vulnerable to opposition — so you know which applications to watch most closely.
curl -G "https://api.signa.so/v1/owners/own_client01/trademarks" \
  -H "Authorization: Bearer $SIGNA_API_KEY" \
  --data-urlencode "status_stage=examining,published,opposition_period,pending_opposition" \
  --data-urlencode "limit=100"
Focus on marks in the published, opposition_period, and examining stages — these are the ones most vulnerable to new proceedings. Registered marks can still face cancellation petitions but the risk is lower.
4

Check prosecution history for contested marks

Review the event timeline of a contested mark to understand how the opposition fits into the prosecution history.
curl "https://api.signa.so/v1/trademarks/tm_merid01/history?limit=20&sort=-event_date" \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Expected output:
Prosecution timeline:
  2026-01-10 | opposition           | OPPOSITION FILED
             Status -> pending_opposition
  2025-11-15 | publication          | PUBLISHED FOR OPPOSITION
             Status -> published
  2025-09-20 | examination          | APPROVED FOR PUBLICATION
  2025-06-01 | filing               | NEW APPLICATION FILED
             Status -> filed
5

Track proceeding outcomes and filter by type

Query proceedings by type and status to build different views of your case docket.
# All opposition proceedings (any party, any status)
curl "https://api.signa.so/v1/proceedings?party_owner_id=own_client01&proceeding_type=opposition&limit=50" \
  -H "Authorization: Bearer $SIGNA_API_KEY"

# Cancellation proceedings only
curl "https://api.signa.so/v1/proceedings?party_owner_id=own_client01&proceeding_type=cancellation&limit=50" \
  -H "Authorization: Bearer $SIGNA_API_KEY"

# Decided proceedings (to review outcomes)
curl "https://api.signa.so/v1/proceedings?party_owner_id=own_client01&status=decided_granted&limit=50" \
  -H "Authorization: Bearer $SIGNA_API_KEY"
6

Detect proceeding status changes by polling history

Poll Trademark History on each contested mark to catch status transitions. Run this hourly from your job scheduler and compare the most recent event against the last one you saw.
const watchedMarkIds = new Set(allProceedings.map((p) => p.trademark_id));

for (const markId of watchedMarkIds) {
  const history = await signa.trademarks.history(markId, {
    limit: 5,
    sort: "-event_date",
  });

  const latest = history.data[0];
  if (!latest) continue;

  if (latest.event_type === "status_changed") {
    console.log(
      `[ALERT] ${markId}: ${latest.details?.from_stage} -> ${latest.details?.to_stage} (${latest.event_date})`,
    );
  }
}
A status change from pending_opposition to registered means the opposition was resolved in your client’s favor — the mark proceeded to registration. A change to abandoned or refused would indicate the opposite outcome.

​
Proceeding status reference

StatusMeaning
pendingActive, awaiting decision
decided_grantedDecided in favor of the petitioner/opponent
decided_rejectedDecided in favor of the respondent
withdrawnPetitioner/opponent withdrew the proceeding
settledParties reached a settlement
suspendedProceeding paused (often pending related litigation)
partialMixed outcome — some grounds sustained, others denied
otherCatch-all for unusual outcomes

​
What’s next

Trademark Clearance

Run clearance searches to avoid triggering oppositions before you file.

Competitor Intelligence

Track competitor filing patterns to anticipate potential opposition actions.

Renewal Management

Ensure contested marks do not lapse during proceedings by tracking their deadlines.