Opposition · USPTO

Opposition 91250594

OtherUSPTO

Opposition 91250594 at USPTO between Bear USA, Inc. and Aaron A. Swift, over the mark BEAR-ABLE, filed Sep 3, 2019. Status in the office record: other.

View BEAR-ABLEGet this data via the API
Status
Other
Result
Other
Filed
Sep 3, 2019
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Bear USA, Inc.

Respondent

Aaron A. Swift

Timeline

How the case has moved

Dates from the USPTO record and the BEAR-ABLE filing.

  1. BEAR-ABLE filed

    Application 88302326 filed at the USPTO.

  2. Opposition filed

    Bear USA, Inc. started opposition 91250594 at USPTO against BEAR-ABLE.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
BEAR-ABLEContested88302326USPTO
BEARRelied on74625218USPTO
BEARRelied on74625219USPTO
BEAR U.S.A., INC.Relied on74802359USPTO
BEARRelied on75063344USPTO
BEARRelied on75063345USPTO
BEAR USARelied on75371191USPTO
BABY BEARRelied on75463798USPTO
BABY BEARRelied on75463799USPTO
BEAR MOUNTAINRelied on75472696USPTO
BABY BEARRelied on75978499USPTO
BEAR USARelied on75983105USPTO

+1 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_11364aac-83ae-46cf-a45f-318061ab4077
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_11364aac-83ae-46cf-a45f-318061ab4077",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91250594",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-09-03",
  "parties": [
    {
      "name": "Bear USA, Inc.",
      "role": "opponent"
    },
    {
      "name": "Aaron A. Swift",
      "role": "respondent"
    }
  ]
}