Opposition · USPTO

Opposition 91223781

OtherUSPTO

Opposition 91223781 at USPTO between The Wonderful Company LLC and Minnie Blue LLC, over the mark MINNIE BLUE, THE MIGHTY WONDER, filed Sep 12, 2015. Status in the office record: other.

View MINNIE BLUE, THE MIGHTY WONDERGet this data via the API
Status
Other
Result
Other
Filed
Sep 12, 2015
Marks involved
6
Parties

Who is involved

The parties as named in the office record.

Opponent

The Wonderful Company LLC

Respondent

Minnie Blue LLC

Timeline

How the case has moved

Dates from the USPTO record and the MINNIE BLUE, THE MIGHTY WONDER filing.

  1. MINNIE BLUE, THE MIGHTY WONDER filed

    Application 86353285 filed at the USPTO.

  2. Opposition filed

    The Wonderful Company LLC started opposition 91223781 at USPTO against MINNIE BLUE, THE MIGHTY WONDER.
Marks

Marks involved

1 contested mark, 5 marks the challenger relies on.

MarkRoleApplicationOffice
MINNIE BLUE, THE MIGHTY WONDERContested86353285USPTO
WONDERFULRelied on85396734USPTO
WONDERFULRelied on85449191USPTO
WONDERFULRelied on85983500USPTO
WONDERFUL SWEET SCARLETTSRelied on86325011USPTO
WONDERFUL SWEET SCARLETTSRelied on86325020USPTO
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_8362e3d0-65b3-4a28-92a7-833dec95a0a9
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8362e3d0-65b3-4a28-92a7-833dec95a0a9",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91223781",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-09-12",
  "parties": [
    {
      "name": "The Wonderful Company LLC",
      "role": "opponent"
    },
    {
      "name": "Minnie Blue LLC",
      "role": "respondent"
    }
  ]
}