Opposition · USPTO

Opposition 91227303

OtherUSPTO

Opposition 91227303 at USPTO between Groupon, Inc. and Eventa Global, Inc., over the mark GROUPONOMICS, filed Apr 11, 2016. Status in the office record: other.

View GROUPONOMICSGet this data via the API
Status
Other
Result
Other
Filed
Apr 11, 2016
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Groupon, Inc.

Company trademarks
Respondent

Eventa Global, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the GROUPONOMICS filing.

  1. GROUPONOMICS filed

    Application 86638062 filed at the USPTO.

  2. Opposition filed

    Groupon, Inc. started opposition 91227303 at USPTO against GROUPONOMICS.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
GROUPONOMICSContested86638062USPTO
GROUPONRelied on77687604USPTO
GROUPONWORKSRelied on85136402USPTO
GROUPONLIVERelied on85222076USPTO
GROUPONICUSRelied on85228084USPTO
GROUPON NOWRelied on85273141USPTO
GROUPONRelied on85668357USPTO
GROUPONRelied on85668414USPTO
GROUPONRelied on85979543USPTO
GROUPONRelied on86240902USPTO
GROUPONRelied on86961190USPTO
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_a495fa3d-f8d1-443e-a7ea-2825e4805718
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_a495fa3d-f8d1-443e-a7ea-2825e4805718",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91227303",
  "status": "other",
  "office_code": "US",
  "filed_date": "2016-04-11",
  "parties": [
    {
      "name": "Groupon, Inc.",
      "role": "opponent"
    },
    {
      "name": "Eventa Global, Inc.",
      "role": "respondent"
    }
  ]
}