Opposition · USPTO

Opposition 91239983

OtherUSPTO

Opposition 91239983 at USPTO between Snap Inc. and Canonical Limited, over the mark SNAPPY, filed Mar 12, 2018. Status in the office record: other.

View SNAPPYGet this data via the API
Status
Other
Result
Other
Filed
Mar 12, 2018
Marks involved
17
Parties

Who is involved

The parties as named in the office record.

Opponent

Snap Inc.

Company trademarks
Respondent

Canonical Limited

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SNAPPY filing.

  1. SNAPPY filed

    Application 87189467 filed at the USPTO.

  2. Opposition filed

    Snap Inc. started opposition 91239983 at USPTO against SNAPPY.
Marks

Marks involved

1 contested mark, 16 marks the challenger relies on.

MarkRoleApplicationOffice
SNAPPYContested87189467USPTO
SNAPMOBILERelied on85175760USPTO
SNAPTVRelied on85176645USPTO
SNAP INTERACTIVERelied on85368307USPTO
SNAPRelied on85368311USPTO
SNAPRelied on85639822USPTO
SNAPCHATRelied on85800506USPTO
SNAP ONERelied on85894380USPTO
SNAPRelied on85946296USPTO
SNAPCHATRelied on86335306USPTO
SNAPRelied on86526355USPTO
SNAPRelied on86559807USPTO

+5 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_9b022a7d-45c4-4091-958d-12ca75989d48
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_9b022a7d-45c4-4091-958d-12ca75989d48",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91239983",
  "status": "other",
  "office_code": "US",
  "filed_date": "2018-03-12",
  "parties": [
    {
      "name": "Snap Inc.",
      "role": "opponent"
    },
    {
      "name": "Canonical Limited",
      "role": "respondent"
    }
  ]
}