Opposition · USPTO

Opposition 91183941

OtherUSPTO

Opposition 91183941 at USPTO between Head Technology GmbH, Head Sport AG and Long, Kip, over the mark HEADER, filed May 7, 2008. Status in the office record: other.

View HEADERGet this data via the API
Status
Other
Result
Other
Filed
May 7, 2008
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Head Technology GmbH, Head Sport AG

Respondent

Long, Kip

Timeline

How the case has moved

Dates from the USPTO record and the HEADER filing.

  1. HEADER filed

    Application 77256315 filed at the USPTO.

  2. Opposition filed

    Head Technology GmbH, Head Sport AG started opposition 91183941 at USPTO against HEADER.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
HEADERContested77256315USPTO
HEADRelied on72052492USPTO
HEADRelied on72282900USPTO
HEADRelied on73027528USPTO
HEADRelied on74103151USPTO
HEADRelied on74103153USPTO
HEADRelied on74289486USPTO
HEADRelied on74691268USPTO
HEADRelied on75894791USPTO
HEADRelied on75982456USPTO
HEAD GAMESRelied on76312901USPTO
HEAD PERFORMANCERelied on79026912USPTO
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_0f58dee8-cdaa-48b8-9f1b-4b14fe426730
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0f58dee8-cdaa-48b8-9f1b-4b14fe426730",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91183941",
  "status": "other",
  "office_code": "US",
  "filed_date": "2008-05-07",
  "parties": [
    {
      "name": "Head Technology GmbH, Head Sport AG",
      "role": "opponent"
    },
    {
      "name": "Long, Kip",
      "role": "respondent"
    }
  ]
}