Opposition · USPTO

Opposition 91280946

OtherUSPTO

Opposition 91280946 at USPTO between BlackBerry Limited and Colaberry Inc., over the mark COLABERRY, filed Oct 5, 2022. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 5, 2022
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

BlackBerry Limited

Company trademarks
Respondent

Colaberry Inc.

Timeline

How the case has moved

Dates from the USPTO record and the COLABERRY filing.

  1. COLABERRY filed

    Application 88931395 filed at the USPTO.
  2. Opposition filed

    BlackBerry Limited started opposition 91280946 at USPTO against COLABERRY.
Marks

Marks involved

2 contested marks, 10 marks the challenger relies on.

MarkRoleApplicationOffice
COLABERRYContested88931395USPTO
COLABERRYContested88931445USPTO
BLACKBERRYRelied on87754054USPTO
BLACKBERRY SPARKRelied on88111165USPTO
BLACKBERRY SHIELDRelied on88159374USPTO
BLACKBERRY SHIELDRelied on88159379USPTO
BLACKBERRY SHIELDRelied on88159382USPTO
BLACKBERRYRelied on88530399USPTO
BLACKBERRYRelied on88530445USPTO
BLACKBERRYRelied on88530497USPTO
BLACKBERRY IVYRelied on90545424USPTO
BLACKBERRY IVYRelied on90560567USPTO
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 /v1/proceedings/{id}
ID=prc_2fabf0d0-26d1-4356-96f2-3b47cdc2c0ed
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_2fabf0d0-26d1-4356-96f2-3b47cdc2c0ed",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91280946",
  "status": "other",
  "office_code": "US",
  "filed_date": "2022-10-05",
  "parties": [
    {
      "name": "BlackBerry Limited",
      "role": "opponent"
    },
    {
      "name": "Colaberry Inc.",
      "role": "respondent"
    }
  ]
}