Opposition · USPTO

Opposition 91220887

OtherUSPTO

Opposition 91220887 at USPTO between Caterpillar Inc. and Let's Party Traction, over the mark CAT PARTY, filed Mar 3, 2015. Status in the office record: other.

Status
Other
Result
Other
Filed
Mar 3, 2015
Marks involved
22
Parties

Who is involved

The parties as named in the office record.

Opponent

Caterpillar Inc.

Company trademarks
Respondent

Let's Party Traction

Timeline

How the case has moved

Dates from the USPTO record and the CAT PARTY filing.

  1. CAT PARTY filed

    Application 86391234 filed at the USPTO.
  2. Opposition filed

    Caterpillar Inc. started opposition 91220887 at USPTO against CAT PARTY.
Marks

Marks involved

1 contested mark, 21 marks the challenger relies on.

MarkRoleApplicationOffice
CAT PARTYContested86391234USPTO
CATRelied on73392831USPTO
CATERPILLARRelied on73392834USPTO
CATRelied on74451720USPTO
CATERPILLARRelied on74451721USPTO
CATERPILLARRelied on75205497USPTO
CATRelied on75205498USPTO
CAT THE RENTAL STORERelied on75270839USPTO
CATERPILLARRelied on75296699USPTO
CATRelied on75296705USPTO
THE CAT RENTAL STORERelied on75296724USPTO
CATRelied on75455116USPTO

+10 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_354646e1-894f-470a-b70a-7ff204c93df8
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_354646e1-894f-470a-b70a-7ff204c93df8",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91220887",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-03-03",
  "parties": [
    {
      "name": "Caterpillar Inc.",
      "role": "opponent"
    },
    {
      "name": "Let's Party Traction",
      "role": "respondent"
    }
  ]
}