Opposition 91278386
OtherUSPTO
Opposition 91278386 at USPTO between Salesforce, Inc. and Farmforce AS, over the mark FARMFORCE, filed Aug 29, 2022. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Aug 29, 2022
- Marks involved
- 22
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 FARMFORCE filing.
FARMFORCE filed
Application 79306789 filed at the USPTO.Opposition filed
Salesforce, Inc. started opposition 91278386 at USPTO against FARMFORCE.
Marks
Marks involved
1 contested mark, 21 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| FARMFORCE | Contested | 79306789 | USPTO |
| SALESFORCE.COM | Relied on | 75836332 | USPTO |
| SALESFORCE | Relied on | 76575119 | USPTO |
| FINANCIALFORCE.COM | Relied on | 77804901 | USPTO |
| FINANCIALFORCE | Relied on | 77804904 | USPTO |
| DREAMFORCE | Relied on | 78509506 | USPTO |
| SALESFORCE | Relied on | 78713215 | USPTO |
| SALESFORCE | Relied on | 78713221 | USPTO |
| SALESFORCE | Relied on | 78713222 | USPTO |
| FORCE | Relied on | 85046219 | USPTO |
| SURVEY FORCE | Relied on | 85140341 | USPTO |
| DEVELOPERFORCE | Relied on | 85146763 | USPTO |
+10 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_1e6fd000-44b8-4de0-a960-795f5e5f478f
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_1e6fd000-44b8-4de0-a960-795f5e5f478f",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91278386",
"status": "other",
"office_code": "US",
"filed_date": "2022-08-29",
"parties": [
{
"name": "Salesforce, Inc.",
"role": "opponent"
},
{
"name": "Farmforce AS",
"role": "respondent"
}
]
}