Opposition · USPTO

Opposition 91291736

OtherUSPTO

Opposition 91291736 at USPTO between Apple Inc. and Apple Industries, Inc., over the mark [Design Mark], filed May 28, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
May 28, 2024
Marks involved
49
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Apple Industries, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the [Design Mark] filing.

  1. [Design Mark] filed

    Application 90671848 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91291736 at USPTO against [Design Mark].
Marks

Marks involved

1 contested mark, 48 marks the challenger relies on.

MarkRoleApplicationOffice
[Design mark]Contested90671848USPTO
APPLERelied on73120444USPTO
APPLE STORERelied on76400649USPTO
[Design mark]Relied on76432525USPTO
[Design mark]Relied on76432531USPTO
APPLE TVRelied on77152380USPTO
TVRelied on77154348USPTO
APPLERelied on77172511USPTO
APPLE STORERelied on77388365USPTO
APPLERelied on77428980USPTO
APPLECARERelied on77499829USPTO
[Design mark]Relied on77648705USPTO

+37 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_8b8f5730-eba7-4f4a-864f-f4e241ff95a0
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8b8f5730-eba7-4f4a-864f-f4e241ff95a0",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91291736",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-05-28",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Apple Industries, Inc.",
      "role": "respondent"
    }
  ]
}