Opposition · USPTO

Opposition 91247638

OtherUSPTO

Opposition 91247638 at USPTO between Target Brands, Inc. and DueDil, over the mark DUEDIL, filed Apr 17, 2019. Status in the office record: other.

Status
Other
Result
Other
Filed
Apr 17, 2019
Marks involved
20
Parties

Who is involved

The parties as named in the office record.

Opponent

Target Brands, Inc.

Company trademarks
Respondent

DueDil

Timeline

How the case has moved

Dates from the USPTO record and the DUEDIL filing.

  1. DUEDIL filed

    Application 86941882 filed at the USPTO.
  2. Opposition filed

    Target Brands, Inc. started opposition 91247638 at USPTO against DUEDIL.
Marks

Marks involved

1 contested mark, 19 marks the challenger relies on.

MarkRoleApplicationOffice
DUEDILContested86941882USPTO
[Design mark]Relied on72425130USPTO
[Design mark]Relied on76052624USPTO
[Design mark]Relied on76379844USPTO
[Design mark]Relied on76379845USPTO
[Design mark]Relied on76379846USPTO
[Design mark]Relied on76379848USPTO
[Design mark]Relied on76379849USPTO
[Design mark]Relied on76379949USPTO
[Design mark]Relied on76387394USPTO
[Design mark]Relied on76418295USPTO
[Design mark]Relied on77982272USPTO

+8 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_549388f2-6f64-4db0-bec9-f244fc10e7bf
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_549388f2-6f64-4db0-bec9-f244fc10e7bf",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91247638",
  "status": "other",
  "office_code": "US",
  "filed_date": "2019-04-17",
  "parties": [
    {
      "name": "Target Brands, Inc.",
      "role": "opponent"
    },
    {
      "name": "DueDil",
      "role": "respondent"
    }
  ]
}