Opposition · USPTO

Opposition 91212803

OtherUSPTO

Opposition 91212803 at USPTO between Top Tobacco, L.P. and Black Diamond Tobacco, Inc., over the mark TOP SECRET, filed Oct 3, 2013. Status in the office record: other.

View TOP SECRETGet this data via the API
Status
Other
Result
Other
Filed
Oct 3, 2013
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Top Tobacco, L.P.

Company trademarks
Respondent

Black Diamond Tobacco, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the TOP SECRET filing.

  1. TOP SECRET filed

    Application 85910359 filed at the USPTO.

  2. Opposition filed

    Top Tobacco, L.P. started opposition 91212803 at USPTO against TOP SECRET.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
TOP SECRETContested85910359USPTO
TOPRelied on75393869USPTO
TOPRelied on76033943USPTO
TOPRelied on76074182USPTO
TOPRelied on76074186USPTO
TOP-O-MATICRelied on76570303USPTO
TOPRelied on77980954USPTO
TOPRelied on78849003USPTO
TOPRelied on78849174USPTO
TOPRelied on78979712USPTO
TOPRelied on78981165USPTO
TOPRelied on78981172USPTO
API

Get this data via the API

Every fact on this page comes from the Signa API. Track oppositions and cancellations on any mark with one request.

  • GET/v1/proceedings/{id}

    Parties, dates, outcome and every mark in the case

  • GET/v1/proceedings?trademark_id={trademark_id}

    Every proceeding on a mark

Get API keyView docs
GET /v1/proceedings/{id}
ID=prc_51cc7c16-83eb-4c3b-a707-d06fd9838fda
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_51cc7c16-83eb-4c3b-a707-d06fd9838fda",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91212803",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-10-03",
  "parties": [
    {
      "name": "Top Tobacco, L.P.",
      "role": "opponent"
    },
    {
      "name": "Black Diamond Tobacco, Inc.",
      "role": "respondent"
    }
  ]
}