Opposition · USPTO

Opposition 91215710

OtherUSPTO

Opposition 91215710 at USPTO between Mattel, Inc. and Bass Walk, Inc., over the mark BAD BARBIE, filed Apr 2, 2014. Status in the office record: other.

View BAD BARBIEGet this data via the API
Status
Other
Result
Other
Filed
Apr 2, 2014
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

Mattel, Inc.

Company trademarks
Respondent

Bass Walk, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the BAD BARBIE filing.

  1. BAD BARBIE filed

    Application 85971026 filed at the USPTO.

  2. Opposition filed

    Mattel, Inc. started opposition 91215710 at USPTO against BAD BARBIE.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
BAD BARBIEContested85971026USPTO
BARBIERelied on72055200USPTO
BARBIERelied on72106619USPTO
BARBIERelied on72106620USPTO
BARBIERelied on72152228USPTO
BARBIERelied on72166825USPTO
BARBIERelied on72179913USPTO
BARBIERelied on72209525USPTO
BARBIERelied on72210579USPTO
BARBIERelied on72210889USPTO
BARBIERelied on72211370USPTO
BARBIERelied on72211371USPTO

+38 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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_57e4ab28-3527-4bcb-a4bd-7b872c71e102
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_57e4ab28-3527-4bcb-a4bd-7b872c71e102",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91215710",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-04-02",
  "parties": [
    {
      "name": "Mattel, Inc.",
      "role": "opponent"
    },
    {
      "name": "Bass Walk, Inc.",
      "role": "respondent"
    }
  ]
}