Opposition · USPTO

Opposition 91272726

OtherUSPTO

Opposition 91272726 at USPTO between Apple Inc. and Aaron Ingram, over the mark AYE! PLUS, filed Nov 3, 2021. Status in the office record: other.

View AYE! PLUSGet this data via the API
Status
Other
Result
Other
Filed
Nov 3, 2021
Marks involved
36
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Aaron Ingram

Timeline

How the case has moved

Dates from the USPTO record and the AYE! PLUS filing.

  1. AYE! PLUS filed

    Application 90159445 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91272726 at USPTO against AYE! PLUS.
Marks

Marks involved

1 contested mark, 35 marks the challenger relies on.

MarkRoleApplicationOffice
AYE! PLUSContested90159445USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
[Design mark]Relied on74693680USPTO
APPLERelied on74693839USPTO
[Design mark]Relied on76426501USPTO
APPLE TVRelied on77152380USPTO
TVRelied on77154348USPTO
APPLERelied on77172511USPTO
[Design mark]Relied on77648705USPTO
IPHONERelied on77976400USPTO
APPLERelied on78430230USPTO

+24 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_181bccb7-2c37-4291-b4d7-17d0776ffc04
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_181bccb7-2c37-4291-b4d7-17d0776ffc04",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91272726",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-11-03",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Aaron Ingram",
      "role": "respondent"
    }
  ]
}