Opposition · USPTO

Opposition 91178684

OtherUSPTO

Opposition 91178684 at USPTO between CIT Group Inc. and Logiology, Inc., over the mark C-IT, filed Aug 1, 2007. Status in the office record: other.

View C-ITGet this data via the API
Status
Other
Result
Other
Filed
Aug 1, 2007
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

CIT Group Inc.

Company trademarks
Respondent

Logiology, Inc.

Timeline

How the case has moved

Dates from the USPTO record and the C-IT filing.

  1. C-IT filed

    Application 78592698 filed at the USPTO.

  2. Opposition filed

    CIT Group Inc. started opposition 91178684 at USPTO against C-IT.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
C-ITContested78592698USPTO
THE CIT GROUPRelied on73597685USPTO
THE CIT GROUPRelied on73597826USPTO
CITRelied on75934301USPTO
CITRelied on75934458USPTO
CIT.COMRelied on75938758USPTO
C IT SOARRelied on76487227USPTO
C IT ROLLRelied on76487228USPTO
C IT SUCCEEDRelied on76487300USPTO
C IT INSPIRE.Relied on76487301USPTO
C ITRelied on76487303USPTO
C IT EDUCATERelied on76487304USPTO

+3 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_22b96159-883b-4b56-859b-464d73909a24
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_22b96159-883b-4b56-859b-464d73909a24",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91178684",
  "status": "other",
  "office_code": "US",
  "filed_date": "2007-08-01",
  "parties": [
    {
      "name": "CIT Group Inc.",
      "role": "opponent"
    },
    {
      "name": "Logiology, Inc.",
      "role": "respondent"
    }
  ]
}