Cancellation · USPTO

Cancellation 92090694

OtherUSPTO

Cancellation 92090694 at USPTO between Lyft, Inc. and PostMerchant LLC, over the mark LIFT, filed Jan 22, 2026. Status in the office record: other.

View LIFTGet this data via the API
Status
Other
Result
Other
Filed
Jan 22, 2026
Marks involved
37
Parties

Who is involved

The parties as named in the office record.

Petitioner

Lyft, Inc.

Company trademarks
Respondent

PostMerchant LLC

Timeline

How the case has moved

Dates from the USPTO record and the LIFT filing.

  1. LIFT filed

    Application 97933731 filed at the USPTO.

  2. LIFT registered

  3. Cancellation filed

    Lyft, Inc. started cancellation 92090694 at USPTO against LIFT.
Marks

Marks involved

1 contested mark, 36 marks the challenger relies on.

MarkRoleApplicationOffice
LIFTContested97933731USPTO
LYFTRelied on85743120USPTO
LYFTRelied on86183222USPTO
LYFTRelied on86183253USPTO
LYFTRelied on86183891USPTO
LYFTRelied on86183906USPTO
LYFTRelied on87254350USPTO
LYFT SCOOTERSRelied on88041722USPTO
LYFTRelied on88041743USPTO
LYFTRelied on88355902USPTO
LYFT DIRECTRelied on88356643USPTO
LYFT CONCIERGERelied on88435433USPTO

+25 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_a3bbc127-9fa0-4329-9222-05fc9838fdeb
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a3bbc127-9fa0-4329-9222-05fc9838fdeb",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92090694",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-01-22",
  "parties": [
    {
      "name": "Lyft, Inc.",
      "role": "petitioner"
    },
    {
      "name": "PostMerchant LLC",
      "role": "respondent"
    }
  ]
}