Opposition · USPTO

Opposition 91270800

Decided: rejectedUSPTO

Opposition 91270800 at USPTO, over the mark X, filed Jul 31, 2021. Status in the office record: decided: rejected (Opposition Dismissed).

View XGet this data via the API
Status
Decided: rejected
Result
Challenger lost
Filed
Jul 31, 2021
Decidedafter 866 days
Dec 14, 2023
Parties

Who is involved

The parties as named in the office record.

Respondent

Vaporous Technologies, LLC

Timeline

How the case has moved

Dates from the USPTO record and the X filing.

  1. X filed

    Application 90192180 filed at the USPTO.

  2. Opposition filed

    Started opposition 91270800 at USPTO against X.

  3. Challenger lost

    Office record: Opposition Dismissed.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
XContested90192180USPTO
FUENTE FUENTE OPUS "X"Relied on74550044USPTO
FUENTE OPUS XRelied on75030336USPTO
FUENTE OPUS X FFRelied on75069035USPTO
XRelied on75749265USPTO
FUENTE OPUSXRelied on75857912USPTO
X TO THE THIRD POWERRelied on75859380USPTO
FORBIDDENXRelied on75982386USPTO
XRelied on76290310USPTO
XRelied on77064649USPTO
XRelied on78524998USPTO
XXXRelied on78525491USPTO

+7 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_8bb6c3fd-b560-4062-8f5e-db4b927efb00
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_8bb6c3fd-b560-4062-8f5e-db4b927efb00",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91270800",
  "status": "decided_rejected",
  "office_code": "US",
  "filed_date": "2021-07-31",
  "parties": [
    {
      "name": "Vaporous Technologies, LLC",
      "role": "respondent"
    }
  ]
}