Opposition · USPTO

Opposition 91285119

OtherUSPTO

Opposition 91285119 at USPTO between Jemie B.V. and Alexander Respeto DBA Cannariculam, over the mark CANNARICULAM, filed May 21, 2023. Status in the office record: other.

View CANNARICULAMGet this data via the API
Status
Other
Result
Other
Filed
May 21, 2023
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Jemie B.V.

Company trademarks
Respondent

Alexander Respeto DBA Cannariculam

Timeline

How the case has moved

Dates from the USPTO record and the CANNARICULAM filing.

  1. CANNARICULAM filed

    Application 97443391 filed at the USPTO.

  2. Opposition filed

    Jemie B.V. started opposition 91285119 at USPTO against CANNARICULAM.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
CANNARICULAMContested97443391USPTO
CANNARelied on86640828USPTO
CANNARelied on86745098USPTO
CANNATALKRelied on86762679USPTO
CANNAZYMRelied on87395826USPTO
CANNABOOSTRelied on87395831USPTO
CANNA STARTRelied on87395839USPTO
CANNARelied on88115337USPTO
BIOCANNARelied on88158432USPTO
FUNDACIÓN CANNARelied on88521415USPTO
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_82a5b842-3ff1-49ce-adc3-7ff3632e35ed
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_82a5b842-3ff1-49ce-adc3-7ff3632e35ed",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91285119",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-05-21",
  "parties": [
    {
      "name": "Jemie B.V.",
      "role": "opponent"
    },
    {
      "name": "Alexander Respeto DBA Cannariculam",
      "role": "respondent"
    }
  ]
}