Opposition · USPTO

Opposition 91242628

OtherUSPTO

Opposition 91242628 at USPTO between Energizer Brands, LLC and YING Meizhen, over the mark PINKY BUNNY, filed Jul 19, 2018. Status in the office record: other.

Status
Other
Result
Other
Filed
Jul 19, 2018
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Energizer Brands, LLC

Respondent

YING Meizhen

Timeline

How the case has moved

Dates from the USPTO record and the PINKY BUNNY filing.

  1. PINKY BUNNY filed

    Application 87759667 filed at the USPTO.
  2. Opposition filed

    Energizer Brands, LLC started opposition 91242628 at USPTO against PINKY BUNNY.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
PINKY BUNNYContested87759667USPTO
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_9ef53d42-cab6-48c9-b3e3-140e400d06ec
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9ef53d42-cab6-48c9-b3e3-140e400d06ec",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91242628",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-07-19",
  "parties": [
    {
      "name": "Energizer Brands, LLC",
      "role": "opponent"
    },
    {
      "name": "YING Meizhen",
      "role": "respondent"
    }
  ]
}