Opposition · USPTO

Opposition 91276203

OtherUSPTO

Opposition 91276203 at USPTO between Monster Energy Company and Mashup LLC, over the mark [Design Mark], filed May 13, 2022. Status in the office record: other.

View [Design Mark]Get this data via the API
Status
Other
Result
Other
Filed
May 13, 2022
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Monster Energy Company

Respondent

Mashup LLC

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 90496166 filed at the USPTO.

  2. Opposition filed

    Monster Energy Company started opposition 91276203 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested90496166USPTO
MRelied on77274643USPTO
MRelied on77274662USPTO
M MONSTER ENERGYRelied on77705822USPTO
MRelied on78246564USPTO
MRelied on85094340USPTO
MRelied on85094343USPTO
MRelied on85094362USPTO
MRelied on85094364USPTO
MRelied on86048362USPTO
MRelied on86300585USPTO
M MONSTER ARMYRelied on86906378USPTO

+6 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_8417ab3b-17dc-457e-9bd8-c39deb09396d
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8417ab3b-17dc-457e-9bd8-c39deb09396d",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91276203",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-05-13",
  "parties": [
    {
      "name": "Monster Energy Company",
      "role": "opponent"
    },
    {
      "name": "Mashup LLC",
      "role": "respondent"
    }
  ]
}