Opposition · USPTO

Opposition 91246283

OtherUSPTO

Opposition 91246283 at USPTO between Uber Technologies, Inc. and Uber Pi, over the mark UBERPI, filed Feb 6, 2019. Status in the office record: other.

View UBERPIGet this data via the API
Status
Other
Result
Other
Filed
Feb 6, 2019
Marks involved
13
Parties

Who is involved

The parties as named in the office record.

Opponent

Uber Technologies, Inc.

Respondent

Uber Pi

Timeline

How the case has moved

Dates from the USPTO record and the UBERPI filing.

  1. UBERPI filed

    Application 87490138 filed at the USPTO.

  2. Opposition filed

    Uber Technologies, Inc. started opposition 91246283 at USPTO against UBERPI.
Marks

Marks involved

1 contested mark, 12 marks the challenger relies on.

MarkRoleApplicationOffice
UBERPIContested87490138USPTO
UBERRelied on85170655USPTO
UBERXRelied on86198791USPTO
UBERRUSHRelied on86250398USPTO
UBER EATSRelied on86541663USPTO
UBERPOOLRelied on86645284USPTO
UBERCOMMUTERelied on86765078USPTO
UBERPOOLRelied on86984102USPTO
UBER FREIGHTRelied on87195689USPTO
UBER ELEVATERelied on87217185USPTO
UBERRelied on87256010USPTO
UBER AIRRelied on87430754USPTO

+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_c0ebb3dc-8f45-4c7e-9436-19fa8e194f3c
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c0ebb3dc-8f45-4c7e-9436-19fa8e194f3c",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91246283",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-02-06",
  "parties": [
    {
      "name": "Uber Technologies, Inc.",
      "role": "opponent"
    },
    {
      "name": "Uber Pi",
      "role": "respondent"
    }
  ]
}