Opposition · USPTO

Opposition 91212353

OtherUSPTO

Opposition 91212353 at USPTO between The Echo Design Group, Inc. and Gilt Groupe, Inc., over the mark HOOK & ECHO, filed Sep 6, 2013. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 6, 2013
Marks involved
29
Parties

Who is involved

The parties as named in the office record.

Opponent

The Echo Design Group, Inc.

Respondent

Gilt Groupe, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the HOOK & ECHO filing.

  1. HOOK & ECHO filed

    Application 85742510 filed at the USPTO.
  2. Opposition filed

    The Echo Design Group, Inc. started opposition 91212353 at USPTO against HOOK & ECHO.
Marks

Marks involved

1 contested mark, 28 marks the challenger relies on.

MarkRoleApplicationOffice
HOOK & ECHOContested85742510USPTO
ECHORelied on71553860USPTO
ECHO ORIGINATIONSRelied on71670197USPTO
ECHORelied on73284808USPTO
ECHORelied on73413346USPTO
ECHORelied on73539065USPTO
SIGNATURE ECHORelied on73588825USPTO
ECHORelied on74158398USPTO
ECHORelied on74594566USPTO
ECHORelied on74594567USPTO
ECHO SOFTRelied on75422278USPTO
ECHORelied on75654255USPTO

+17 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 /v1/proceedings/{id}
ID=prc_6017542c-4d24-4966-a2d5-0a6ae51fb643
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_6017542c-4d24-4966-a2d5-0a6ae51fb643",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91212353",
  "status": "other",
  "office_code": "US",
  "filed_date": "2013-09-06",
  "parties": [
    {
      "name": "The Echo Design Group, Inc.",
      "role": "opponent"
    },
    {
      "name": "Gilt Groupe, Inc.",
      "role": "respondent"
    }
  ]
}