Opposition · USPTO

Opposition 91203299

OtherUSPTO

Opposition 91203299 at USPTO between Zynga Inc. and James McGibney, over the mark CUPIDVILLE, filed Jan 9, 2012. Status in the office record: other.

View CUPIDVILLEGet this data via the API
Status
Other
Result
Other
Filed
Jan 9, 2012
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Opponent

Zynga Inc.

Company trademarks
Respondent

James McGibney

Timeline

How the case has moved

Dates from the USPTO record and the CUPIDVILLE filing.

  1. CUPIDVILLE filed

    Application 85268276 filed at the USPTO.

  2. Opposition filed

    Zynga Inc. started opposition 91203299 at USPTO against CUPIDVILLE.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
CUPIDVILLEContested85268276USPTO
YOVILLERelied on77678316USPTO
FARMVILLE BY ZYNGARelied on77798840USPTO
FARMVILLERelied on77804837USPTO
FISHVILLERelied on77842158USPTO
FRONTIERVILLERelied on77894903USPTO
CITYVILLERelied on77920777USPTO
PETVILLERelied on77979543USPTO
CITYVILLERelied on85187572USPTO
FRONTIERVILLERelied on85187815USPTO
FARMVILLERelied on85187825USPTO
VILLERelied on85326925USPTO
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_eec7514a-c88a-441a-8fdc-ba9cb53e1964
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_eec7514a-c88a-441a-8fdc-ba9cb53e1964",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91203299",
  "status": "other",
  "office_code": "US",
  "filed_date": "2012-01-09",
  "parties": [
    {
      "name": "Zynga Inc.",
      "role": "opponent"
    },
    {
      "name": "James McGibney",
      "role": "respondent"
    }
  ]
}