Opposition · USPTO

Opposition 91284557

OtherUSPTO

Opposition 91284557 at USPTO between Ridestore Holding AB and DopeENOUGH, over the mark DOPEENOUGH, filed Apr 19, 2023. Status in the office record: other.

View DOPEENOUGHGet this data via the API
Status
Other
Result
Other
Filed
Apr 19, 2023
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Ridestore Holding AB

Respondent

DopeENOUGH

Timeline

How the case has moved

Dates from the USPTO record and the DOPEENOUGH filing.

  1. DOPEENOUGH filed

    Application 97395826 filed at the USPTO.

  2. Opposition filed

    Ridestore Holding AB started opposition 91284557 at USPTO against DOPEENOUGH.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
DOPEENOUGHContested97395826USPTO
DOPERelied on79300325USPTO
DOPERelied on85375315USPTO
DOPERelied on85841683USPTO
DOPESTRelied on85930325USPTO
DOPERelied on86293042USPTO
DOPE SPORTRelied on87222632USPTO
DOPE DENIMRelied on87222671USPTO
DOPERelied on88000969USPTO
DOPE COUTURERelied on90333319USPTO
DOPERelied on90333343USPTO
DOPERelied on90333365USPTO

+2 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_36a03ad4-fbd5-418a-92b5-b7bdc6f1e2f7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_36a03ad4-fbd5-418a-92b5-b7bdc6f1e2f7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91284557",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-04-19",
  "parties": [
    {
      "name": "Ridestore Holding AB",
      "role": "opponent"
    },
    {
      "name": "DopeENOUGH",
      "role": "respondent"
    }
  ]
}