Opposition · USPTO

Opposition 91221836

OtherUSPTO

Opposition 91221836 at USPTO between 4Life Trademarks, LLC and Live4Life LLC, over the mark LIVE4LIFE HEALTH, filed May 6, 2015. Status in the office record: other.

View LIVE4LIFE HEALTHGet this data via the API
Status
Other
Result
Other
Filed
May 6, 2015
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

4Life Trademarks, LLC

Company trademarks
Respondent

Live4Life LLC

Timeline

How the case has moved

Dates from the USPTO record and the LIVE4LIFE HEALTH filing.

  1. LIVE4LIFE HEALTH filed

    Application 86297243 filed at the USPTO.

  2. Opposition filed

    4Life Trademarks, LLC started opposition 91221836 at USPTO against LIVE4LIFE HEALTH.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
LIVE4LIFE HEALTHContested86297243USPTO
4LIFERelied on75889052USPTO
4LIFERelied on76235208USPTO
HEALTHY 4LIFERelied on76249220USPTO
FLEX4LIFERelied on76322894USPTO
4LIFERelied on76351280USPTO
TEA4LIFERelied on76373143USPTO
4LIFERelied on76456704USPTO
4LIFERelied on76456705USPTO
4LIFE TRANSFER FACTORRelied on78344235USPTO
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_ecdb02a9-8779-4528-87dc-3801aeb1d552
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_ecdb02a9-8779-4528-87dc-3801aeb1d552",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91221836",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-05-06",
  "parties": [
    {
      "name": "4Life Trademarks, LLC",
      "role": "opponent"
    },
    {
      "name": "Live4Life LLC",
      "role": "respondent"
    }
  ]
}