Opposition · USPTO

Opposition 91288549

OtherUSPTO

Opposition 91288549 at USPTO between Helix, Inc. and Texas Medical Center, over the mark HELIX PARK, filed Dec 4, 2023. Status in the office record: other.

View HELIX PARKGet this data via the API
Status
Other
Result
Other
Filed
Dec 4, 2023
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Helix, Inc.

Respondent

Texas Medical Center

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the HELIX PARK filing.

  1. HELIX PARK filed

    Application 97410093 filed at the USPTO.

  2. Opposition filed

    Helix, Inc. started opposition 91288549 at USPTO against HELIX PARK.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
HELIX PARKContested97410093USPTO
HELIXRelied on87539083USPTO
HELIXRelied on87539089USPTO
HELIXRelied on87539101USPTO
HELIXRelied on87573883USPTO
HELIXRelied on88134331USPTO
HELIXRelied on88950481USPTO
HELIXRelied on88950502USPTO
HELIXRelied on88950523USPTO
HELIXRelied on88950541USPTO
HELIXRelied on88950556USPTO
HELIXRelied on88950564USPTO

+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_91de5a33-3b67-4d4d-addf-8805d864f1c0
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_91de5a33-3b67-4d4d-addf-8805d864f1c0",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91288549",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-12-04",
  "parties": [
    {
      "name": "Helix, Inc.",
      "role": "opponent"
    },
    {
      "name": "Texas Medical Center",
      "role": "respondent"
    }
  ]
}