Opposition · USPTO

Opposition 91289640

OtherUSPTO

Opposition 91289640 at USPTO between Chapter 4 Corp. and Primary (Shenzhen) Technology Co., LTD, over the mark SUPMAGIC, filed Feb 7, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Feb 7, 2024
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Chapter 4 Corp.

Respondent

Primary (Shenzhen) Technology Co., LTD

Timeline

How the case has moved

Dates from the USPTO record and the SUPMAGIC filing.

  1. SUPMAGIC filed

    Application 97854599 filed at the USPTO.
  2. Opposition filed

    Chapter 4 Corp. started opposition 91289640 at USPTO against SUPMAGIC.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
SUPMAGICContested97854599USPTO
SUPREMERelied on85424627USPTO
SUPREMERelied on85424722USPTO
SUPREMERelied on85868093USPTO
SUPREMERelied on85868116USPTO
SUPREMERelied on86225786USPTO
SUPREMERelied on86225846USPTO
SUPREMERelied on86225879USPTO
SUPREMERelied on86225910USPTO
SUPREMERelied on86691471USPTO
SUPREMERelied on86691492USPTO
SUPRelied on87208480USPTO

+8 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_496662aa-9aa3-4e5c-bcbf-f6932978b7ff
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_496662aa-9aa3-4e5c-bcbf-f6932978b7ff",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91289640",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-02-07",
  "parties": [
    {
      "name": "Chapter 4 Corp.",
      "role": "opponent"
    },
    {
      "name": "Primary (Shenzhen) Technology Co., LTD",
      "role": "respondent"
    }
  ]
}