Opposition · USPTO

Opposition 91205757

OtherUSPTO

Opposition 91205757 at USPTO between Mattel, Inc. and Barbierawk, LLC, over the mark BARBIERAWK, filed Jun 25, 2012. Status in the office record: other.

View BARBIERAWKGet this data via the API
Status
Other
Result
Other
Filed
Jun 25, 2012
Marks involved
43
Parties

Who is involved

The parties as named in the office record.

Opponent

Mattel, Inc.

Company trademarks
Respondent

Barbierawk, LLC

Timeline

How the case has moved

Dates from the USPTO record and the BARBIERAWK filing.

  1. BARBIERAWK filed

    Application 85489886 filed at the USPTO.

  2. Opposition filed

    Mattel, Inc. started opposition 91205757 at USPTO against BARBIERAWK.
Marks

Marks involved

1 contested mark, 42 marks the challenger relies on.

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

+31 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_679c5480-9305-4ee9-9954-7d7d53160485
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_679c5480-9305-4ee9-9954-7d7d53160485",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91205757",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-06-25",
  "parties": [
    {
      "name": "Mattel, Inc.",
      "role": "opponent"
    },
    {
      "name": "Barbierawk, LLC",
      "role": "respondent"
    }
  ]
}