Cancellation 92074252
OtherUSPTO
Cancellation 92074252 at USPTO between Golo, LLC and Goli Nutrition Inc., over the mark GOLI, filed May 18, 2020. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- May 18, 2020
- Marks involved
- 16
Parties
Who is involved
The parties as named in the office record.
Timeline
How the case has moved
Dates from the USPTO record and the GOLI filing.
GOLI filed
Application 88976287 filed at the USPTO.GOLI registered
Cancellation filed
Golo, LLC started cancellation 92074252 at USPTO against GOLI.
Marks
Marks involved
1 contested mark, 15 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| GOLI | Contested | 88976287 | USPTO |
| GOLO | Relied on | 85374201 | USPTO |
| GOLO FOR LIFE | Relied on | 85380655 | USPTO |
| GOLO | Relied on | 87075500 | USPTO |
| GOLO METABOLIC MATRIX | Relied on | 87076404 | USPTO |
| GOLO FOODS | Relied on | 87076407 | USPTO |
| MYGOLO | Relied on | 87076408 | USPTO |
| GOLO FUEL INDEX | Relied on | 87077503 | USPTO |
| GOLO SUPERFUEL | Relied on | 87088637 | USPTO |
| GOLO SMART CARD | Relied on | 87088646 | USPTO |
| GOLO LIFECARDS | Relied on | 87088659 | USPTO |
| GOLO RESCUE PLAN | Relied on | 87088674 | USPTO |
+4 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_a24d44e1-1814-4e1e-9af6-09db29fc25cd
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_a24d44e1-1814-4e1e-9af6-09db29fc25cd",
"object": "proceeding",
"proceeding_type": "cancellation",
"proceeding_number": "92074252",
"status": "other",
"office_code": "US",
"filed_date": "2020-05-18",
"parties": [
{
"name": "GOLO, LLC",
"role": "petitioner"
},
{
"name": "Goli Nutrition Inc.",
"role": "respondent"
}
]
}