Opposition · USPTO

Opposition 91254393

OtherUSPTO

Opposition 91254393 at USPTO between Snap Inc. and Spicy Monkey Inc, over the mark SHATCHAT, filed Mar 2, 2020. Status in the office record: other.

View SHATCHATGet this data via the API
Status
Other
Result
Other
Filed
Mar 2, 2020
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Snap Inc.

Company trademarks
Respondent

Spicy Monkey Inc

Timeline

How the case has moved

Dates from the USPTO record and the SHATCHAT filing.

  1. SHATCHAT filed

    Application 88596935 filed at the USPTO.

  2. Opposition filed

    Snap Inc. started opposition 91254393 at USPTO against SHATCHAT.
Marks

Marks involved

1 contested mark, 13 marks the challenger relies on.

MarkRoleApplicationOffice
SHATCHATContested88596935USPTO
SNAPRelied on85368311USPTO
SNAPRelied on85639822USPTO
SNAPCHATRelied on85800506USPTO
SNAPCHATRelied on86335306USPTO
SNAPRelied on86559807USPTO
SNAPCHATRelied on86619184USPTO
SNAPCODERelied on86619662USPTO
SNAP ADSRelied on86721820USPTO
SNAPCHATRelied on86978618USPTO
SNAP PUBLISHERRelied on87693210USPTO
SNAP PIXELRelied on87726793USPTO

+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_1f42d233-47f1-4eca-a614-16ae2ceab9b4
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_1f42d233-47f1-4eca-a614-16ae2ceab9b4",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91254393",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-03-02",
  "parties": [
    {
      "name": "Snap Inc.",
      "role": "opponent"
    },
    {
      "name": "Spicy Monkey Inc",
      "role": "respondent"
    }
  ]
}