Opposition 91277899
OtherUSPTO
Opposition 91277899 at USPTO between Amazon Technologies, Inc. and Shenzhen Yehai Technology Co., Ltd., over the mark AMZLOGO, filed Aug 10, 2022. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Aug 10, 2022
- Marks involved
- 11
Parties
Who is involved
The parties as named in the office record.
Respondent
Shenzhen Yehai Technology Co., Ltd.
Timeline
How the case has moved
Dates from the USPTO record and the AMZLOGO filing.
AMZLOGO filed
Application 97001053 filed at the USPTO.Opposition filed
Amazon Technologies, Inc. started opposition 91277899 at USPTO against AMZLOGO.
Marks
Marks involved
1 contested mark, 10 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| AMZLOGO | Contested | 97001053 | USPTO |
| AMAZON | Relied on | 75981644 | USPTO |
| AMAZON | Relied on | 77572206 | USPTO |
| AMAZON | Relied on | 77572552 | USPTO |
| AMAZON BASICS | Relied on | 77983416 | USPTO |
| AMAZON | Relied on | 78005143 | USPTO |
| AMAZON BASICS | Relied on | 86086382 | USPTO |
| AMAZON | Relied on | 86315391 | USPTO |
| AMAZON | Relied on | 86315405 | USPTO |
| AMAZON BASICS | Relied on | 86508762 | USPTO |
| AMAZON | Relied on | 86983875 | USPTO |
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_1bead92b-dfa7-4876-ba9a-f8b6dd112568
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_1bead92b-dfa7-4876-ba9a-f8b6dd112568",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91277899",
"status": "other",
"office_code": "US",
"filed_date": "2022-08-10",
"parties": [
{
"name": "Amazon Technologies, Inc.",
"role": "opponent"
},
{
"name": "Shenzhen Yehai Technology Co., Ltd.",
"role": "respondent"
}
]
}