Opposition · USPTO

Opposition 91232008

OtherUSPTO

Opposition 91232008 at USPTO between Seattle Pacific Industries, Inc. and Unitybrand, LLC, over the mark 2015 U B UNITY BRAND, filed Dec 30, 2016. Status in the office record: other.

View 2015 U B UNITY BRANDGet this data via the API
Status
Other
Result
Other
Filed
Dec 30, 2016
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Seattle Pacific Industries, Inc.

Respondent

Unitybrand, LLC

Timeline

How the case has moved

Dates from the USPTO record and the 2015 U B UNITY BRAND filing.

  1. 2015 U B UNITY BRAND filed

    Application 87031715 filed at the USPTO.

  2. Opposition filed

    Seattle Pacific Industries, Inc. started opposition 91232008 at USPTO against 2015 U B UNITY BRAND.
Marks

Marks involved

3 contested marks, 6 marks the challenger relies on.

MarkRoleApplicationOffice
2015 U B UNITY BRANDContested87031715USPTO
U B UNITY BRANDContested87031747USPTO
U B UNITY BRANDContested87031766USPTO
UBRelied on75779195USPTO
UBRelied on75782690USPTO
UBRelied on75782691USPTO
UBRelied on75960328USPTO
UBRelied on75960544USPTO
UBRelied on77932052USPTO
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_263b0325-656b-4c0f-a113-884f0376c5df
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_263b0325-656b-4c0f-a113-884f0376c5df",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91232008",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-12-30",
  "parties": [
    {
      "name": "Seattle Pacific Industries, Inc.",
      "role": "opponent"
    },
    {
      "name": "Unitybrand, LLC",
      "role": "respondent"
    }
  ]
}