Opposition · USPTO

Opposition 91292428

OtherUSPTO

Opposition 91292428 at USPTO between Hugo Boss AG and James Lindsay, over the mark BOSSCOIN, filed Jul 1, 2024. Status in the office record: other.

View BOSSCOINGet this data via the API
Status
Other
Result
Other
Filed
Jul 1, 2024
Marks involved
50
Parties

Who is involved

The parties as named in the office record.

Opponent

Hugo Boss AG

Company trademarks
Respondent

James Lindsay

Timeline

How the case has moved

Dates from the USPTO record and the BOSSCOIN filing.

  1. BOSSCOIN filed

    Application 90793706 filed at the USPTO.

  2. Opposition filed

    Hugo Boss AG started opposition 91292428 at USPTO against BOSSCOIN.
Marks

Marks involved

1 contested mark, 49 marks the challenger relies on.

MarkRoleApplicationOffice
BOSSCOINContested90793706USPTO
BOSSRelied on73036140USPTO
BOSSRelied on73569217USPTO
BOSSRelied on73665340USPTO
BOSSRelied on73665341USPTO
HUGO BOSSRelied on73665342USPTO
BOSSRelied on73665343USPTO
HUGO BOSSRelied on73665364USPTO
BOSS HUGO BOSSRelied on73665965USPTO
HUGO BOSSRelied on73674099USPTO
BOSS HUGO BOSSRelied on73747911USPTO
BOSSRelied on74074962USPTO

+38 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_185ae713-1c28-48f1-a16f-9bc5287073f9
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_185ae713-1c28-48f1-a16f-9bc5287073f9",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91292428",
  "status": "other",
  "office_code": "US",
  "filed_date": "2024-07-01",
  "parties": [
    {
      "name": "Hugo Boss AG",
      "role": "opponent"
    },
    {
      "name": "James Lindsay",
      "role": "respondent"
    }
  ]
}