Opposition · USPTO

Opposition 91245688

OtherUSPTO

Opposition 91245688 at USPTO between Snap Inc. and Snatch Group Limited, over the mark SNATCHAPP, filed Jan 4, 2019. Status in the office record: other.

View SNATCHAPPGet this data via the API
Status
Other
Result
Other
Filed
Jan 4, 2019
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Snap Inc.

Respondent

Snatch Group Limited

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SNATCHAPP filing.

  1. SNATCHAPP filed

    Application 79223352 filed at the USPTO.

  2. Opposition filed

    Snap Inc. started opposition 91245688 at USPTO against SNATCHAPP.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
SNATCHAPPContested79223352USPTO
SNAP INTERACTIVERelied on85368307USPTO
SNAPRelied on85368311USPTO
SNAPRelied on85639822USPTO
SNAPCHATRelied on85800506USPTO
SNAP ONERelied on85894380USPTO
SNAPRelied on85946296USPTO
SNAPCHATRelied on86335306USPTO
SNAPRelied on86526355USPTO
SNAPRelied on86559807USPTO
SNAPCHATRelied on86619184USPTO
SNAPCODERelied on86619662USPTO

+3 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_0d52aef9-6f82-4b79-9157-3e91e927d267
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_0d52aef9-6f82-4b79-9157-3e91e927d267",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91245688",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-01-04",
  "parties": [
    {
      "name": "Snap Inc.",
      "role": "opponent"
    },
    {
      "name": "Snatch Group Limited",
      "role": "respondent"
    }
  ]
}