Opposition · USPTO

Opposition 91232419

OtherUSPTO

Opposition 91232419 at USPTO between Dr Pepper/Seven Up, Inc. and Asmodus Inc., over the mark CRUSH FRUITS, filed Jan 24, 2017. Status in the office record: other.

View CRUSH FRUITSGet this data via the API
Status
Other
Result
Other
Filed
Jan 24, 2017
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Dr Pepper/Seven Up, Inc.

Respondent

Asmodus Inc.

Timeline

How the case has moved

Dates from the USPTO record and the CRUSH FRUITS filing.

  1. CRUSH FRUITS filed

    Application 87024647 filed at the USPTO.

  2. Opposition filed

    Dr Pepper/Seven Up, Inc. started opposition 91232419 at USPTO against CRUSH FRUITS.
Marks

Marks involved

2 contested marks, 10 marks the challenger relies on.

MarkRoleApplicationOffice
CRUSH FRUITSContested87024647USPTO
CRUSH FRUITSContested87024711USPTO
CRUSHRelied on71156594USPTO
CRUSHRelied on73592383USPTO
CRUSHRelied on75576146USPTO
CRUSHRelied on75639221USPTO
CRUSHRelied on75639222USPTO
CRUSHRelied on77602920USPTO
CRUSHRelied on78314308USPTO
CRUSHRelied on78928155USPTO
CRUSHRelied on78978696USPTO
CRUSHRelied on85615496USPTO
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_35b906ab-c1c0-4280-89e4-fbef460c85d6
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_35b906ab-c1c0-4280-89e4-fbef460c85d6",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91232419",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-01-24",
  "parties": [
    {
      "name": "Dr Pepper/Seven Up, Inc.",
      "role": "opponent"
    },
    {
      "name": "Asmodus Inc.",
      "role": "respondent"
    }
  ]
}