Opposition · USPTO

Opposition 91271701

OtherUSPTO

Opposition 91271701 at USPTO between Apple Inc. and Guilherme Marques Da Silva, over the mark PINEAPPLE LIVE, filed Sep 15, 2021. Status in the office record: other.

Status
Other
Result
Other
Filed
Sep 15, 2021
Marks involved
15
Parties

Who is involved

The parties as named in the office record.

Opponent

Apple Inc.

Company trademarks
Respondent

Guilherme Marques Da Silva

Timeline

How the case has moved

Dates from the USPTO record and the PINEAPPLE LIVE filing.

  1. PINEAPPLE LIVE filed

    Application 90272801 filed at the USPTO.
  2. Opposition filed

    Apple Inc. started opposition 91271701 at USPTO against PINEAPPLE LIVE.
Marks

Marks involved

1 contested mark, 14 marks the challenger relies on.

MarkRoleApplicationOffice
PINEAPPLE LIVEContested90272801USPTO
APPLERelied on73120444USPTO
APPLERelied on74693839USPTO
[Design mark]Relied on76426501USPTO
APPLE TVRelied on77152380USPTO
APPLERelied on77172511USPTO
APPLERelied on77428980USPTO
[Design mark]Relied on77648705USPTO
APPLERelied on78430230USPTO
APPLE MUSICRelied on86658508USPTO
APPLE MUSICRelied on86659491USPTO
MUSICRelied on86663157USPTO

+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 /v1/proceedings/{id}
ID=prc_3b19c673-e192-4f9b-a85f-0532c29ee0e2
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_3b19c673-e192-4f9b-a85f-0532c29ee0e2",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91271701",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-09-15",
  "parties": [
    {
      "name": "Apple Inc.",
      "role": "opponent"
    },
    {
      "name": "Guilherme Marques Da Silva",
      "role": "respondent"
    }
  ]
}