Opposition · USPTO

Opposition 91290981

OtherUSPTO

Opposition 91290981 at USPTO between Magic Leap, Inc. and Dapper Labs Inc., over the mark MAGIC, filed Apr 17, 2024. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 17, 2024
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Magic Leap, Inc.

Company trademarks
Respondent

Dapper Labs Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the MAGIC filing.

  1. MAGIC filed

    Application 97373339 filed at the USPTO.
  2. Opposition filed

    Magic Leap, Inc. started opposition 91290981 at USPTO against MAGIC.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
MAGICContested97373339USPTO
MAGIC LEAPRelied on86609716USPTO
MAGIC LEAPRelied on87427526USPTO
MAGIC LEAP ONERelied on87673335USPTO
MAGIC KITRelied on87798793USPTO
MAGIC LEAP LIVERelied on87897670USPTO
MAGIC LEAPRelied on87983117USPTO
MAGICVERSERelied on88040764USPTO
MAGIC LEAPRelied on88060768USPTO
MAGICSCRIPTRelied on88146564USPTO
MAGICVERSERelied on88251609USPTO
MAGIC LEAP 1Relied on88725374USPTO

+1 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_e305ed09-03a0-437a-84fc-0a4a7ff43fef
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e305ed09-03a0-437a-84fc-0a4a7ff43fef",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91290981",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-04-17",
  "parties": [
    {
      "name": "Magic Leap, Inc.",
      "role": "opponent"
    },
    {
      "name": "Dapper Labs Inc.",
      "role": "respondent"
    }
  ]
}