Opposition · USPTO

Opposition 91287790

OtherUSPTO

Opposition 91287790 at USPTO between Helix, Inc. and Infosys Limited, over the mark INFOSYS HELIX, filed Oct 20, 2023. Status in the office record: other.

View INFOSYS HELIXGet this data via the API
Status
Other
Result
Other
Filed
Oct 20, 2023
Marks involved
18
Parties

Who is involved

The parties as named in the office record.

Opponent

Helix, Inc.

Respondent

Infosys Limited

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the INFOSYS HELIX filing.

  1. INFOSYS HELIX filed

    Application 97494114 filed at the USPTO.

  2. Opposition filed

    Helix, Inc. started opposition 91287790 at USPTO against INFOSYS HELIX.
Marks

Marks involved

1 contested mark, 17 marks the challenger relies on.

MarkRoleApplicationOffice
INFOSYS HELIXContested97494114USPTO
HELIXRelied on78311374USPTO
HELIXRelied on87539083USPTO
HELIXRelied on87539089USPTO
HELIXRelied on87539101USPTO
HELIXRelied on87573883USPTO
HELIXRelied on88134331USPTO
HELIXRelied on88950481USPTO
HELIXRelied on88950502USPTO
HELIXRelied on88950523USPTO
HELIXRelied on88950541USPTO
HELIXRelied on88950556USPTO

+6 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_fdd1bb0e-716c-45cd-a4b5-52cbe0e0f725
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_fdd1bb0e-716c-45cd-a4b5-52cbe0e0f725",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91287790",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-10-20",
  "parties": [
    {
      "name": "Helix, Inc.",
      "role": "opponent"
    },
    {
      "name": "Infosys Limited",
      "role": "respondent"
    }
  ]
}