Opposition · USPTO

Opposition 91272214

OtherUSPTO

Opposition 91272214 at USPTO between Sage Software Inc. and SageSure Insurance Managers LLC, over the mark SAGESURE, filed Oct 11, 2021. Status in the office record: other.

View SAGESUREGet this data via the API
Status
Other
Result
Other
Filed
Oct 11, 2021
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

Sage Software Inc.

Respondent

SageSure Insurance Managers LLC

Timeline

How the case has moved

Dates from the USPTO record and the SAGESURE filing.

  1. SAGESURE filed

    Application 90240630 filed at the USPTO.

  2. Opposition filed

    Sage Software Inc. started opposition 91272214 at USPTO against SAGESURE.
Marks

Marks involved

3 contested marks, 8 marks the challenger relies on.

MarkRoleApplicationOffice
SAGESUREContested90240630USPTO
SAGESUREContested90240635USPTO
MYSAGESUREContested90240640USPTO
SAGERelied on75420104USPTO
SAGERelied on75590576USPTO
SAGERelied on76412073USPTO
SAGE 50Relied on85653174USPTO
SAGE 100Relied on85653212USPTO
SAGE 300Relied on85653250USPTO
SAGE ADVISORRelied on85676457USPTO
SAGE VIEWRelied on86470820USPTO
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_22c385e6-5227-4c08-ac2e-1e2749e3bbab
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_22c385e6-5227-4c08-ac2e-1e2749e3bbab",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91272214",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-10-11",
  "parties": [
    {
      "name": "Sage Software Inc.",
      "role": "opponent"
    },
    {
      "name": "SageSure Insurance Managers LLC",
      "role": "respondent"
    }
  ]
}