Opposition · USPTO

Opposition 91222850

OtherUSPTO

Opposition 91222850 at USPTO between Levi Strauss & Co. and Joshua Steinbock, over the mark LEVIL, filed Jul 17, 2015. Status in the office record: other.

View LEVILGet this data via the API
Status
Other
Result
Other
Filed
Jul 17, 2015
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Levi Strauss & Co.

Company trademarks
Respondent

Joshua Steinbock

Timeline

How the case has moved

Dates from the USPTO record and the LEVIL filing.

  1. LEVIL filed

    Application 85438093 filed at the USPTO.

  2. Opposition filed

    Levi Strauss & Co. started opposition 91222850 at USPTO against LEVIL.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
LEVILContested85438093USPTO
LEVI'SRelied on71248368USPTO
LEVI'SRelied on71556108USPTO
LEVI'SRelied on71638273USPTO
LEVI'SRelied on72257497USPTO
LEVI'SRelied on73120559USPTO
LEVI'SRelied on73180144USPTO
LEVI'SRelied on73210408USPTO
LEVI'SRelied on75449347USPTO
LEVI'SRelied on75493759USPTO
LEVI'SRelied on75562738USPTO
LEVI'SRelied on76193799USPTO

+3 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_f389b8bf-c4a6-4ff2-831e-b87c10cf7f59
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_f389b8bf-c4a6-4ff2-831e-b87c10cf7f59",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91222850",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-07-17",
  "parties": [
    {
      "name": "Levi Strauss & Co.",
      "role": "opponent"
    },
    {
      "name": "Joshua Steinbock",
      "role": "respondent"
    }
  ]
}