Opposition · USPTO

Opposition 91179712

OtherUSPTO

Opposition 91179712 at USPTO between Johnson & Johnson and Heidi Cortez, over the mark HEIDI'S BEDTIME STORIES, filed Sep 26, 2007. Status in the office record: other.

View HEIDI'S BEDTIME STORIESGet this data via the API
Status
Other
Result
Other
Filed
Sep 26, 2007
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Johnson & Johnson

Company trademarks
Respondent

Heidi Cortez

Timeline

How the case has moved

Dates from the USPTO record and the HEIDI'S BEDTIME STORIES filing.

  1. HEIDI'S BEDTIME STORIES filed

    Application 78966171 filed at the USPTO.

  2. Opposition filed

    Johnson & Johnson started opposition 91179712 at USPTO against HEIDI'S BEDTIME STORIES.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
HEIDI'S BEDTIME STORIESContested78966171USPTO
BEDTIME BATHRelied on76136926USPTO
BEDTIME BATHRelied on76136927USPTO
BEDTIME LOTIONRelied on76173615USPTO
BEDTIME LOTIONRelied on76173616USPTO
BEDTIME CREAM WASHRelied on76606813USPTO
BEDTIME CREAMRelied on76633752USPTO
BEDTIME CREAMRelied on78459650USPTO
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_e645d586-bb1c-4ebd-a6bb-f75bb124b19e
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_e645d586-bb1c-4ebd-a6bb-f75bb124b19e",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91179712",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-09-26",
  "parties": [
    {
      "name": "Johnson & Johnson",
      "role": "opponent"
    },
    {
      "name": "Heidi Cortez",
      "role": "respondent"
    }
  ]
}