Opposition 91246317
OtherUSPTO
Opposition 91246317 at USPTO between Lyft, Inc. and First Class Campaigns, LLC, over the mark LIFT THE VOTE, filed Feb 8, 2019. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Feb 8, 2019
- Marks involved
- 17
Parties
Who is involved
The parties as named in the office record.
Respondent
First Class Campaigns, LLC
Timeline
How the case has moved
Dates from the USPTO record and the LIFT THE VOTE filing.
LIFT THE VOTE filed
Application 88090396 filed at the USPTO.Opposition filed
Lyft, Inc. started opposition 91246317 at USPTO against LIFT THE VOTE.
Marks
Marks involved
1 contested mark, 16 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| LIFT THE VOTE | Contested | 88090396 | USPTO |
| LYFT | Relied on | 85743120 | USPTO |
| LYFT | Relied on | 86183222 | USPTO |
| LYFT | Relied on | 86183253 | USPTO |
| LYFT | Relied on | 86183891 | USPTO |
| LYFT | Relied on | 86183906 | USPTO |
| LYFT | Relied on | 86982665 | USPTO |
| UNDERCOVER LYFT | Relied on | 87182313 | USPTO |
| LYFTCARE | Relied on | 87227300 | USPTO |
| LYFT | Relied on | 87254350 | USPTO |
| SKILYFT | Relied on | 87580936 | USPTO |
| LYFT | Relied on | 87913906 | USPTO |
+5 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 /v1/proceedings/{id}
ID=prc_b1bc5001-fb5e-4178-9505-5535318d1774
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_b1bc5001-fb5e-4178-9505-5535318d1774",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91246317",
"status": "other",
"office_code": "US",
"filed_date": "2019-02-08",
"parties": [
{
"name": "Lyft, Inc.",
"role": "opponent"
},
{
"name": "First Class Campaigns, LLC",
"role": "respondent"
}
]
}