Opposition · USPTO

Opposition 91293381

OtherUSPTO

Opposition 91293381 at USPTO between Apple Inc. and Mattel, Inc., over the mark APPLES TO APPLES, filed Aug 19, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Aug 19, 2024
Marks involved
31
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Mattel, Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the APPLES TO APPLES filing.

  1. APPLES TO APPLES filed

    Application 97797243 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91293381 at USPTO against APPLES TO APPLES.
Marks

Marks involved

1 contested mark, 30 marks the challenger relies on.

MarkRoleApplicationOffice
APPLES TO APPLESContested97797243USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
APPLE TVRelied on77152380USPTO
TVRelied on77154348USPTO
APPLERelied on77172511USPTO
APPLERelied on77428980USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78943482USPTO
APPLE MUSICRelied on86658508USPTO
APPLE MUSICRelied on86659491USPTO
APPLE MUSICRelied on86659908USPTO

+19 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_61ef5b7e-8c4e-4131-a39b-7a944919756e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_61ef5b7e-8c4e-4131-a39b-7a944919756e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91293381",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-08-19",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Mattel, Inc.",
      "role": "respondent"
    }
  ]
}