Opposition · USPTO

Opposition 91201877

OtherUSPTO

Opposition 91201877 at USPTO between Apple Inc. and Devon Brooks, over the mark APPLERT, filed Sep 14, 2011. Status in the office record: other.

View APPLERTGet this data via the API
Status
Other
Result
Other
Filed
Sep 14, 2011
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Devon Brooks

Timeline

How the case has moved

Dates from the USPTO record and the APPLERT filing.

  1. APPLERT filed

    Application 85132731 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91201877 at USPTO against APPLERT.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
APPLERTContested85132731USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
APPLERelied on74660120USPTO
APPLE STORERelied on75857151USPTO
APPLE STORERelied on76400649USPTO
[Design mark]Relied on76426501USPTO
APPLE TVRelied on77152380USPTO
APPLERelied on77172511USPTO
APPLE STORERelied on77388365USPTO
[Design mark]Relied on77648705USPTO
IPHONERelied on77976400USPTO

+5 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_2c76f459-f809-4861-bcb9-c3453bf541ee
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2c76f459-f809-4861-bcb9-c3453bf541ee",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91201877",
  "status": "other",
  "office_code": "US",
  "filed_date": "2011-09-14",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Devon Brooks",
      "role": "respondent"
    }
  ]
}