Opposition · USPTO

Opposition 91287580

OtherUSPTO

Opposition 91287580 at USPTO between ContextLogic Inc. and Jiangsu Medwish Network Technology Co., Ltd., over the mark MEDWISH, filed Oct 4, 2023. Status in the office record: other.

Status
Other
Result
Other
Filed
Oct 4, 2023
Marks involved
11
Parties

Who is involved

The parties as named in the office record.

Opponent

ContextLogic Inc.

Respondent

Jiangsu Medwish Network Technology Co., Ltd.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the MEDWISH filing.

  1. MEDWISH filed

    Application 79348213 filed at the USPTO.
  2. Opposition filed

    ContextLogic Inc. started opposition 91287580 at USPTO against MEDWISH.
Marks

Marks involved

1 contested mark, 10 marks the challenger relies on.

MarkRoleApplicationOffice
MEDWISHContested79348213USPTO
WISHRelied on85581397USPTO
WISHRelied on85581401USPTO
WISH - SHOPPING MADE FUNRelied on86539900USPTO
WISHRelied on88303185USPTO
WISH LOCALRelied on88524604USPTO
WISH PICKUPRelied on88558689USPTO
WISHRelied on88758910USPTO
WISHPOSTRelied on90337777USPTO
WISHPOSTRelied on90337783USPTO
WISH PARCELRelied on97063544USPTO
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 /v1/proceedings/{id}
ID=prc_52360fee-4c66-40a4-ae04-5c116d8d2693
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_52360fee-4c66-40a4-ae04-5c116d8d2693",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91287580",
  "status": "other",
  "office_code": "US",
  "filed_date": "2023-10-04",
  "parties": [
    {
      "name": "ContextLogic Inc.",
      "role": "opponent"
    },
    {
      "name": "Jiangsu Medwish Network Technology Co., Ltd.",
      "role": "respondent"
    }
  ]
}