Opposition · USPTO

Opposition 91252816

OtherUSPTO

Opposition 91252816 at USPTO between Reply S.p.A. and Dylan Delancey, over the mark BUY REPLY, filed Dec 10, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Dec 10, 2019
Marks involved
27
Parties

Who is involved

The parties as named in the office record.

Opponent

Reply S.p.A.

Company trademarks
Respondent

Dylan Delancey

Timeline

How the case has moved

Dates from the USPTO record and the BUY REPLY filing.

  1. BUY REPLY filed

    Application 88423115 filed at the USPTO.
  2. Opposition filed

    Reply S.p.A. started opposition 91252816 at USPTO against BUY REPLY.
Marks

Marks involved

1 contested mark, 26 marks the challenger relies on.

MarkRoleApplicationOffice
BUY REPLYContested88423115USPTO
SIDEUP REPLYRelied on79097293USPTO
CLICK REPLYRelied on79100876USPTO
REPLYRelied on79100877USPTO
HI REPLYRelied on79104581USPTO
DEFINIO REPLYRelied on79131323USPTO
DISCOVERY REPLYRelied on79131831USPTO
REPLY XCHANGERelied on79134374USPTO
REPLY BREEDRelied on79173179USPTO
REPLY TRIPLESENSERelied on79187157USPTO
APPHEAL REPLYRelied on79197746USPTO
TICURO REPLYRelied on79197927USPTO

+15 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_66238509-5283-4f14-ba43-0202c281ed8f
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_66238509-5283-4f14-ba43-0202c281ed8f",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91252816",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-12-10",
  "parties": [
    {
      "name": "Reply S.p.A.",
      "role": "opponent"
    },
    {
      "name": "Dylan Delancey",
      "role": "respondent"
    }
  ]
}