Opposition · USPTO

Opposition 91235324

OtherUSPTO

Opposition 91235324 at USPTO between Apple Inc. and Apple to Oyster LLC, over the mark APPLE TO OYSTER, filed Jun 28, 2017. Status in the office record: other.

Status
Other
Result
Other
Filed
Jun 28, 2017
Marks involved
22
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Apple to Oyster LLC

Timeline

How the case has moved

Dates from the USPTO record and the APPLE TO OYSTER filing.

  1. APPLE TO OYSTER filed

    Application 87183062 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91235324 at USPTO against APPLE TO OYSTER.
Marks

Marks involved

1 contested mark, 21 marks the challenger relies on.

MarkRoleApplicationOffice
APPLE TO OYSTERContested87183062USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on73162799USPTO
APPLERelied on74527910USPTO
APPLERelied on74660120USPTO
APPLE STORERelied on75857151USPTO
THE APPLE STORERelied on75857191USPTO
APPLE STORERelied on76400649USPTO
[Design mark]Relied on76426501USPTO
APPLERelied on77172511USPTO
APPLE STORERelied on77388365USPTO
APPLERelied on77388864USPTO

+10 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_40949068-0c90-4f32-85b8-5605f582d033
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_40949068-0c90-4f32-85b8-5605f582d033",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91235324",
  "status": "other",
  "office_code": "US",
  "filed_date": "2017-06-28",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Apple to Oyster LLC",
      "role": "respondent"
    }
  ]
}