Opposition · USPTO

Opposition 91255949

OtherUSPTO

Opposition 91255949 at USPTO between Symphony Holdings Limited and Skims Body, Inc., over the mark SKIMS, filed May 18, 2020. Status in the office record: other.

Status
Other
Result
Other
Filed
May 18, 2020
Marks involved
14
Parties

Who is involved

The parties as named in the office record.

Opponent

Symphony Holdings Limited

Respondent

Skims Body, Inc.

Company trademarks
Timeline

How the case has moved

Dates from the USPTO record and the SKIMS filing.

  1. SKIMS filed

    Application 88515219 filed at the USPTO.
  2. Opposition filed

    Symphony Holdings Limited started opposition 91255949 at USPTO against SKIMS.
Marks

Marks involved

5 contested marks, 9 marks the challenger relies on.

MarkRoleApplicationOffice
SKIMSContested88515219USPTO
SKIMS SOLUTIONSContested88515249USPTO
SKIMS SOLUTIONWEARContested88515278USPTO
SKIMS BODYContested88530317USPTO
SKIMSContested88592773USPTO
S SKINSRelied on77901530USPTO
S SKINSRelied on78972753USPTO
SKINSRelied on79218880USPTO
SKINSRelied on79237973USPTO
S SKINSRelied on86519020USPTO
S SKINSRelied on88885311USPTO
S SKINSRelied on88885314USPTO

+2 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 /v1/proceedings/{id}
ID=prc_c11585e6-9d33-4ff2-8205-d46a254c7980
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_c11585e6-9d33-4ff2-8205-d46a254c7980",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91255949",
  "status": "other",
  "office_code": "US",
  "filed_date": "2020-05-18",
  "parties": [
    {
      "name": "Symphony Holdings Limited",
      "role": "opponent"
    },
    {
      "name": "Skims Body, Inc.",
      "role": "respondent"
    }
  ]
}