Opposition · USPTO

Opposition 91224679

OtherUSPTO

Opposition 91224679 at USPTO between Threshold Enterprises Ltd. and Nutramax Laboratories, Inc., over the mark NMX WELLNESS INNOVATIONS, filed Nov 2, 2015. Status in the office record: other.

View NMX WELLNESS INNOVATIONSGet this data via the API
Status
Other
Result
Other
Filed
Nov 2, 2015
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

Threshold Enterprises Ltd.

Respondent

Nutramax Laboratories, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the NMX WELLNESS INNOVATIONS filing.

  1. NMX WELLNESS INNOVATIONS filed

    Application 86510850 filed at the USPTO.

  2. Opposition filed

    Threshold Enterprises Ltd. started opposition 91224679 at USPTO against NMX WELLNESS INNOVATIONS.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
NMX WELLNESS INNOVATIONSContested86510850USPTO
WELLNESS FORMULARelied on74524068USPTO
WELLNESS FIZZRelied on77685678USPTO
WELLNESS SHOTSRelied on78601833USPTO
WELLNESS SHOTRelied on85628552USPTO
WELLNESS ON THE GORelied on85628585USPTO
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_ee26bb1f-09e1-410e-bff2-fd72d2401d82
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ee26bb1f-09e1-410e-bff2-fd72d2401d82",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91224679",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-11-02",
  "parties": [
    {
      "name": "Threshold Enterprises Ltd.",
      "role": "opponent"
    },
    {
      "name": "Nutramax Laboratories, Inc.",
      "role": "respondent"
    }
  ]
}