Opposition · USPTO

Opposition 91223376

OtherUSPTO

Opposition 91223376 at USPTO between Puma SE and Puma Energy International S.A., over the mark PUMA, filed Aug 18, 2015. Status in the office record: other.

View PUMAGet this data via the API
Status
Other
Result
Other
Filed
Aug 18, 2015
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Puma SE

Company trademarks
Respondent

Puma Energy International S.A.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the PUMA filing.

  1. PUMA filed

    Application 85889004 filed at the USPTO.

  2. Opposition filed

    Puma SE started opposition 91223376 at USPTO against PUMA.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
PUMAContested85889004USPTO
PUMARelied on72205343USPTO
PUMARelied on72343354USPTO
PUMARelied on73037072USPTO
PUMARelied on73037100USPTO
PUMARelied on73086445USPTO
PUMARelied on73269046USPTO
PUMARelied on73269236USPTO
PUMARelied on73292656USPTO
[Design mark]Relied on73292728USPTO
PUMARelied on73293657USPTO
PUMARelied on73293742USPTO

+8 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_500122b1-f89f-4afe-a9cc-f80d13521f52
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_500122b1-f89f-4afe-a9cc-f80d13521f52",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91223376",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-08-18",
  "parties": [
    {
      "name": "Puma SE",
      "role": "opponent"
    },
    {
      "name": "Puma Energy International S.A.",
      "role": "respondent"
    }
  ]
}