Opposition · USPTO

Opposition 91304936

OtherUSPTO

Opposition 91304936 at USPTO between New York Yankees Partnership and Who's Holding Happy Munkey, LLC, over the mark HM, filed Feb 4, 2026. Status in the office record: other.

View HMGet this data via the API
Status
Other
Result
Other
Filed
Feb 4, 2026
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

New York Yankees Partnership

Respondent

Who's Holding Happy Munkey, LLC

Timeline

How the case has moved

Dates from the USPTO record and the HM filing.

  1. HM filed

    Application 98186377 filed at the USPTO.

  2. Opposition filed

    New York Yankees Partnership started opposition 91304936 at USPTO against HM.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
HMContested98186377USPTO
NYRelied on73097286USPTO
NYRelied on73222037USPTO
NYRelied on73746676USPTO
NYRelied on73764426USPTO
NYRelied on74294048USPTO
NYRelied on76213615USPTO
NYRelied on78637641USPTO
NYRelied on78637642USPTO
NYRelied on78637644USPTO
NYRelied on78637647USPTO
NYRelied on78637651USPTO

+2 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_38222fdd-021c-4638-9d9c-fa3c182a85e9
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_38222fdd-021c-4638-9d9c-fa3c182a85e9",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91304936",
  "status": "other",
  "office_code": "US",
  "filed_date": "2026-02-04",
  "parties": [
    {
      "name": "New York Yankees Partnership",
      "role": "opponent"
    },
    {
      "name": "Who's Holding Happy Munkey, LLC",
      "role": "respondent"
    }
  ]
}