Opposition · USPTO

Opposition 91254801

OtherUSPTO

Opposition 91254801 at USPTO between Energizer Brands, LLC and Yong Cao, over the mark PINK BUNNY, filed Mar 20, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 20, 2020
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Energizer Brands, LLC

Company trademarks
Respondent

Yong Cao

Timeline

How the case has moved

Dates from the USPTO record and the PINK BUNNY filing.

  1. PINK BUNNY filed

    Application 88606679 filed at the USPTO.
  2. Opposition filed

    Energizer Brands, LLC started opposition 91254801 at USPTO against PINK BUNNY.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
PINK BUNNYContested88606679USPTO
ENERGIZERRelied on74708971USPTO
ENERGIZER BUNNYRelied on76367112USPTO
ENERGIZER BUNNYRelied on78200655USPTO
ENERGIZERRelied on85898597USPTO
ENERGIZERRelied on86078652USPTO
ENERGIZERRelied on86760047USPTO
ENERGIZERRelied on86760300USPTO
ENERGIZERRelied on86760872USPTO
ENERGIZERRelied on86872437USPTO
ENERGIZERRelied on86872444USPTO
ENERGIZERRelied on86872454USPTO

+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 /v1/proceedings/{id}
ID=prc_113cda5d-8da4-4a44-a7c5-b7151485e030
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_113cda5d-8da4-4a44-a7c5-b7151485e030",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91254801",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-03-20",
  "parties": [
    {
      "name": "Energizer Brands, LLC",
      "role": "opponent"
    },
    {
      "name": "Yong Cao",
      "role": "respondent"
    }
  ]
}