Opposition · USPTO

Opposition 91215474

OtherUSPTO

Opposition 91215474 at USPTO between McDonald's Corporation and Happy Products, Inc., over the mark HAPPY, filed Apr 29, 2015. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 29, 2015
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

McDonald's Corporation

Company trademarks
Respondent

Happy Products, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the HAPPY filing.

  1. HAPPY filed

    Application 85910957 filed at the USPTO.
  2. Opposition filed

    McDonald's Corporation started opposition 91215474 at USPTO against HAPPY.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
HAPPYContested85910957USPTO
HAPPY MEALRelied on73148046USPTO
MCHAPPY DAYRelied on73373321USPTO
HAPPY MEALRelied on73391997USPTO
MRelied on74054688USPTO
HAPPY MEALRelied on77305070USPTO
HAPPY MEALRelied on77305079USPTO
HAPPY KIDS HAPPY MOMSRelied on77367655USPTO
MCHAPPY DAYRelied on77690295USPTO
[Design mark]Relied on85828805USPTO
[Design mark]Relied on85828819USPTO
[Design mark]Relied on85966777USPTO
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 /v1/proceedings/{id}
ID=prc_bf49af8f-0ada-43c0-af05-dad41750730e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_bf49af8f-0ada-43c0-af05-dad41750730e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91215474",
  "status": "other",
  "office_code": "US",
  "filed_date": "2015-04-29",
  "parties": [
    {
      "name": "McDonald's Corporation",
      "role": "opponent"
    },
    {
      "name": "Happy Products, Inc.",
      "role": "respondent"
    }
  ]
}