Opposition · USPTO

Opposition 91284530

OtherUSPTO

Opposition 91284530 at USPTO between Apple Inc. and TOHJO Co., Ltd., over the mark M, filed Apr 12, 2023. Status in the office record: other.

View MGet this data via the API
Status
Other
Result
Other
Filed
Apr 12, 2023
Marks involved
41
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

TOHJO Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the M filing.

  1. M filed

    Application 79326335 filed at the USPTO.

  2. Opposition filed

    Apple Inc. started opposition 91284530 at USPTO against M.
Marks

Marks involved

1 contested mark, 40 marks the challenger relies on.

MarkRoleApplicationOffice
MContested79326335USPTO
APPLERelied on73120444USPTO
[Design mark]Relied on76426501USPTO
APPLE TVRelied on77152380USPTO
TVRelied on77154348USPTO
APPLERelied on77172511USPTO
[Design mark]Relied on77648705USPTO
[Design mark]Relied on78146716USPTO
[Design mark]Relied on78155188USPTO
[Design mark]Relied on78408365USPTO
[Design mark]Relied on85097331USPTO
APPLE WATCHRelied on86390028USPTO

+29 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_7c760ce5-7102-4d4a-ac04-26af9e17d6cb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_7c760ce5-7102-4d4a-ac04-26af9e17d6cb",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91284530",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-04-12",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "TOHJO Co., Ltd.",
      "role": "respondent"
    }
  ]
}