Opposition · USPTO

Opposition 91307688

OtherUSPTO

Opposition 91307688 at USPTO between Lyft Inc. and TD SYNNEX Corporation, over the mark SHYFT, filed May 28, 2026. Status in the office record: other.

View SHYFTGet this data via the API
Status
Other
Result
Other
Filed
May 28, 2026
Marks involved
35
Parties

Who is involved

The parties as named in the office record.

Opponent

Lyft Inc.

Company trademarks
Respondent

TD SYNNEX Corporation

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SHYFT filing.

  1. SHYFT filed

    Application 97661871 filed at the USPTO.

  2. Opposition filed

    Lyft Inc. started opposition 91307688 at USPTO against SHYFT.
Marks

Marks involved

1 contested mark, 34 marks the challenger relies on.

MarkRoleApplicationOffice
SHYFTContested97661871USPTO
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

+23 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_5f2a5c9d-7116-4042-a4e2-7da537085ed7
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5f2a5c9d-7116-4042-a4e2-7da537085ed7",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91307688",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-05-28",
  "parties": [
    {
      "name": "Lyft Inc.",
      "role": "opponent"
    },
    {
      "name": "TD SYNNEX Corporation",
      "role": "respondent"
    }
  ]
}