Opposition · USPTO

Opposition 91220382

OtherUSPTO

Opposition 91220382 at USPTO between Directed, LLC and Viper Innovative Products, LLC, over the mark VIPER, filed Jan 28, 2015. Status in the office record: other.

View VIPERGet this data via the API
Status
Other
Result
Other
Filed
Jan 28, 2015
Marks involved
16
Parties

Who is involved

The parties as named in the office record.

Opponent

Directed, LLC

Respondent

Viper Innovative Products, LLC

Timeline

How the case has moved

Dates from the USPTO record and the VIPER filing.

  1. VIPER filed

    Application 86150703 filed at the USPTO.

  2. Opposition filed

    Directed, LLC started opposition 91220382 at USPTO against VIPER.
Marks

Marks involved

1 contested mark, 15 marks the challenger relies on.

MarkRoleApplicationOffice
VIPERContested86150703USPTO
VIPERRelied on73775611USPTO
VIPERRelied on74293318USPTO
VIPERRelied on74296002USPTO
VIPERRelied on74622208USPTO
VIPERRelied on74633911USPTO
VIPERRelied on74690070USPTO
VIPERRelied on75125165USPTO
VIPERRelied on75455751USPTO
VIPERRelied on76076478USPTO
VIPERRelied on76528057USPTO
VIPER SMARTSTARTRelied on77798847USPTO

+4 more marks in this case

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_5b7bcd4d-624e-4bb9-81b9-74d6695d1a0a
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5b7bcd4d-624e-4bb9-81b9-74d6695d1a0a",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91220382",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-01-28",
  "parties": [
    {
      "name": "Directed, LLC",
      "role": "opponent"
    },
    {
      "name": "Viper Innovative Products, LLC",
      "role": "respondent"
    }
  ]
}