Opposition · USPTO

Opposition 91290376

OtherUSPTO

Opposition 91290376 at USPTO between Playboy Enterprises International, Inc. and Cade G Whitcomb, over the mark PRAYBOY, filed Mar 18, 2024. Status in the office record: other.

View PRAYBOYGet this data via the API
Status
Other
Result
Other
Filed
Mar 18, 2024
Marks involved
10
Parties

Who is involved

The parties as named in the office record.

Opponent

Playboy Enterprises International, Inc.

Respondent

Cade G Whitcomb

Timeline

How the case has moved

Dates from the USPTO record and the PRAYBOY filing.

  1. PRAYBOY filed

    Application 97822804 filed at the USPTO.

  2. Opposition filed

    Playboy Enterprises International, Inc. started opposition 91290376 at USPTO against PRAYBOY.
Marks

Marks involved

1 contested mark, 9 marks the challenger relies on.

MarkRoleApplicationOffice
PRAYBOYContested97822804USPTO
PLAYBOYRelied on72238954USPTO
PLAYBOYRelied on73264124USPTO
PLAYBOYRelied on73341544USPTO
PLAYBOYRelied on77834415USPTO
PLAYBOYRelied on78515459USPTO
MR. PLAYBOYRelied on86198220USPTO
PLAYBOYRelied on86506030USPTO
PLAYBOYRelied on87037226USPTO
PLAYBOYRelied on98447463USPTO
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_e812e055-1b1b-4578-8fa4-332e2864f7af
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e812e055-1b1b-4578-8fa4-332e2864f7af",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91290376",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-03-18",
  "parties": [
    {
      "name": "Playboy Enterprises International, Inc.",
      "role": "opponent"
    },
    {
      "name": "Cade G Whitcomb",
      "role": "respondent"
    }
  ]
}