Opposition · USPTO

Opposition 91180123

OtherUSPTO

Opposition 91180123 at USPTO between Assurant, Inc. and Medtronic Vascular, Inc., over the mark ASSURANT COBALT, filed Oct 17, 2007. Status in the office record: other.

View ASSURANT COBALTGet this data via the API
Status
Other
Result
Other
Filed
Oct 17, 2007
Marks involved
9
Parties

Who is involved

The parties as named in the office record.

Opponent

Assurant, Inc.

Company trademarks
Respondent

Medtronic Vascular, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the ASSURANT COBALT filing.

  1. ASSURANT COBALT filed

    Application 77042348 filed at the USPTO.

  2. Opposition filed

    Assurant, Inc. started opposition 91180123 at USPTO against ASSURANT COBALT.
Marks

Marks involved

1 contested mark, 8 marks the challenger relies on.

MarkRoleApplicationOffice
ASSURANT COBALTContested77042348USPTO
ASSURANTRelied on75769638USPTO
ASSURANT GROUPRelied on78123668USPTO
ASSURANT PRENEEDRelied on78326622USPTO
ASSURANT HEALTHRelied on78328787USPTO
ASSURANTRelied on78349997USPTO
ASSURANTRelied on78350081USPTO
ASSURANTRelied on78396894USPTO
ASSURANT EMPLOYEE BENEFITSRelied on78565836USPTO
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_311b1b6f-579d-46ee-9722-fca32d257ea5
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_311b1b6f-579d-46ee-9722-fca32d257ea5",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91180123",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-10-17",
  "parties": [
    {
      "name": "Assurant, Inc.",
      "role": "opponent"
    },
    {
      "name": "Medtronic Vascular, Inc.",
      "role": "respondent"
    }
  ]
}