Opposition 91241347
OtherUSPTO
Opposition 91241347 at USPTO between EPOD America, LLC and Dope Era, LLC, over the mark DOPE ERA, filed May 23, 2018. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- May 23, 2018
- Marks involved
- 17
Parties
Who is involved
The parties as named in the office record.
Opponent
EPOD America, LLC
Respondent
Dope Era, LLC
Timeline
How the case has moved
Dates from the USPTO record and the DOPE ERA filing.
DOPE ERA filed
Application 87713376 filed at the USPTO.Opposition filed
EPOD America, LLC started opposition 91241347 at USPTO against DOPE ERA.
Marks
Marks involved
1 contested mark, 16 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| DOPE ERA | Contested | 87713376 | USPTO |
| AUDACITY OF DOPE | Relied on | 77652171 | USPTO |
| DOPE COUTURE | Relied on | 77951263 | USPTO |
| DOPE | Relied on | 85375315 | USPTO |
| DOPEST | Relied on | 85621895 | USPTO |
| DOPE | Relied on | 85763811 | USPTO |
| DOPE | Relied on | 85773190 | USPTO |
| DOPE | Relied on | 85777601 | USPTO |
| DOPE | Relied on | 85841683 | USPTO |
| DOPE | Relied on | 85846862 | USPTO |
| DOPE COUTURE | Relied on | 85846891 | USPTO |
| DOPEST | Relied on | 85930325 | USPTO |
+5 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 /v1/proceedings/{id}
ID=prc_7583677b-39a2-4a9a-bf82-9f19593975c9
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_7583677b-39a2-4a9a-bf82-9f19593975c9",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91241347",
"status": "other",
"office_code": "US",
"filed_date": "2018-05-23",
"parties": [
{
"name": "EPOD America, LLC",
"role": "opponent"
},
{
"name": "Dope Era, LLC",
"role": "respondent"
}
]
}