Opposition · USPTO

Opposition 91224449

OtherUSPTO

Opposition 91224449 at USPTO between Energizer Brands, LLC and Energette, LLC, over the mark ENERGETTE, filed Oct 20, 2015. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 20, 2015
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Energizer Brands, LLC

Company trademarks
Respondent

Energette, LLC

Timeline

How the case has moved

Dates from the USPTO record and the ENERGETTE filing.

  1. ENERGETTE filed

    Application 86616025 filed at the USPTO.
  2. Opposition filed

    Energizer Brands, LLC started opposition 91224449 at USPTO against ENERGETTE.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
ENERGETTEContested86616025USPTO
ENERGIZERRelied on73703628USPTO
ENERGIZERRelied on77415351USPTO
ENERGIZERRelied on77516512USPTO
ENERGIZERRelied on77776326USPTO
ENERGIZERRelied on77776592USPTO
ENERGIZERRelied on77809100USPTO
ENERGISTICKRelied on77871066USPTO
ENERGIZERRelied on78161513USPTO
ENERGIZERRelied on78697159USPTO
ENERGIZERRelied on85026478USPTO
ENERGIZERRelied on85035379USPTO

+2 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_2a203b22-dcdf-48de-b35e-05e1cfc366bf
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2a203b22-dcdf-48de-b35e-05e1cfc366bf",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91224449",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-10-20",
  "parties": [
    {
      "name": "Energizer Brands, LLC",
      "role": "opponent"
    },
    {
      "name": "Energette, LLC",
      "role": "respondent"
    }
  ]
}