Opposition · USPTO

Opposition 91196962

OtherUSPTO

Opposition 91196962 at USPTO between Kellogg North America Company and Humane Treats, LLC, over the mark SHARETREAT, filed Oct 18, 2010. Status in the office record: other.

View SHARETREATGet this data via the API
Status
Other
Result
Other
Filed
Oct 18, 2010
Marks involved
8
Parties

Who is involved

The parties as named in the office record.

Opponent

Kellogg North America Company

Respondent

Humane Treats, LLC

Timeline

How the case has moved

Dates from the USPTO record and the SHARETREAT filing.

  1. SHARETREAT filed

    Application 77734627 filed at the USPTO.

  2. Opposition filed

    Kellogg North America Company started opposition 91196962 at USPTO against SHARETREAT.
Marks

Marks involved

1 contested mark, 7 marks the challenger relies on.

MarkRoleApplicationOffice
SHARETREATContested77734627USPTO
RICE KRISPIES TREATSRelied on73647011USPTO
KRISPIES TREATSRelied on73750544USPTO
RICE KRISPIES TREATSRelied on74295992USPTO
TREATS SHEETRelied on74693167USPTO
RICE KRISPIES TREATSRelied on75031312USPTO
RICE KRISPIES TREATSRelied on75134277USPTO
MARSHMALLOW TREATSRelied on78828503USPTO
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_5872c86e-2e65-4989-9d1c-c89964ac1127
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_5872c86e-2e65-4989-9d1c-c89964ac1127",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91196962",
  "status": "other",
  "office_code": "US",
  "filed_date": "2010-10-18",
  "parties": [
    {
      "name": "Kellogg North America Company",
      "role": "opponent"
    },
    {
      "name": "Humane Treats, LLC",
      "role": "respondent"
    }
  ]
}