Opposition 91272364
OtherUSPTO
Opposition 91272364 at USPTO between Apple Inc. and Cruze Distribution, over the mark APL, filed Oct 18, 2021. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Oct 18, 2021
- Marks involved
- 13
Parties
Who is involved
The parties as named in the office record.
Respondent
Cruze Distribution
Timeline
How the case has moved
Dates from the USPTO record and the APL filing.
APL filed
Application 88939213 filed at the USPTO.Opposition filed
Apple Inc. started opposition 91272364 at USPTO against APL.
Marks
Marks involved
1 contested mark, 12 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| APL | Contested | 88939213 | USPTO |
| [Design mark] | Relied on | 76426501 | USPTO |
| APPLE | Relied on | 77172511 | USPTO |
| [Design mark] | Relied on | 78156920 | USPTO |
| [Design mark] | Relied on | 78943482 | USPTO |
| APPLE WATCH | Relied on | 86389914 | USPTO |
| APPLE WATCH | Relied on | 86390028 | USPTO |
| WATCH | Relied on | 86390778 | USPTO |
| WATCH | Relied on | 86390818 | USPTO |
| [Design mark] | Relied on | 87570036 | USPTO |
| CONNECTS TO APPLE WATCH | Relied on | 87730536 | USPTO |
| CONNECT TO APPLE WATCH | Relied on | 87730728 | USPTO |
+1 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_3e3e5d37-cad4-4285-8d0e-9f996c4273e7
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_3e3e5d37-cad4-4285-8d0e-9f996c4273e7",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91272364",
"status": "other",
"office_code": "US",
"filed_date": "2021-10-18",
"parties": [
{
"name": "Apple Inc.",
"role": "opponent"
},
{
"name": "Cruze Distribution",
"role": "respondent"
}
]
}