Opposition · USPTO

Opposition 91249776

OtherUSPTO

Opposition 91249776 at USPTO between Fox Head, Inc. and Castro, Antonio, over the mark FOX FLEX, filed Jul 26, 2019. Status in the office record: other.

View FOX FLEXGet this data via the API
Status
Other
Result
Other
Filed
Jul 26, 2019
Marks involved
19
Parties

Who is involved

The parties as named in the office record.

Opponent

Fox Head, Inc.

Respondent

Castro, Antonio

Timeline

How the case has moved

Dates from the USPTO record and the FOX FLEX filing.

  1. FOX FLEX filed

    Application 88344917 filed at the USPTO.

  2. Opposition filed

    Fox Head, Inc. started opposition 91249776 at USPTO against FOX FLEX.
Marks

Marks involved

1 contested mark, 18 marks the challenger relies on.

MarkRoleApplicationOffice
FOX FLEXContested88344917USPTO
FOXRelied on73401867USPTO
[Design mark]Relied on73771424USPTO
[Design mark]Relied on75169847USPTO
FOXRelied on75170440USPTO
FOX DENIMRelied on76440489USPTO
FOX FOOTWEARRelied on76440528USPTO
FOXGIRLRelied on76443623USPTO
FOXRelied on77744940USPTO
FOXTECHRelied on77912395USPTO
FOXRelied on78774602USPTO
FOX DELUXERelied on78894684USPTO

+7 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_86b2a28b-5b78-4bba-b633-ccf4caeb46d4
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_86b2a28b-5b78-4bba-b633-ccf4caeb46d4",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91249776",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-07-26",
  "parties": [
    {
      "name": "Fox Head, Inc.",
      "role": "opponent"
    },
    {
      "name": "Castro, Antonio",
      "role": "respondent"
    }
  ]
}