Opposition · USPTO

Opposition 91241441

OtherUSPTO

Opposition 91241441 at USPTO between Apple Inc. and Neharia, Inc., over the mark AS APPLE PIE, filed May 29, 2018. Status in the office record: other.

View AS APPLE PIEGet this data via the API
Status
Other
Result
Other
Filed
May 29, 2018
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Neharia, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the AS APPLE PIE filing.

  1. AS APPLE PIE filed

    Application 87318526 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91241441 at USPTO against AS APPLE PIE.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
AS APPLE PIEContested87318526USPTO
APPLE TVRelied on77152380USPTO
TVRelied on77154348USPTO
APPLERelied on77172511USPTO
APPLERelied on77428980USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78157042USPTO
[Design mark]Relied on78943482USPTO
APPLE MUSICRelied on86658508USPTO
APPLE MUSICRelied on86659491USPTO
MUSICRelied on86663005USPTO
MUSICRelied on86663019USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_7c86b2c2-bfc7-4f02-aeb5-77d2ca1696f0
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7c86b2c2-bfc7-4f02-aeb5-77d2ca1696f0",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91241441",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-05-29",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Neharia, Inc.",
      "role": "respondent"
    }
  ]
}