Opposition 91293513
OtherUSPTO
Opposition 91293513 at USPTO between Target Brands, Inc. and TargetingOne Corporation, over the mark TARGETINGONE, filed Aug 21, 2024. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Aug 21, 2024
- Marks involved
- 14
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 TARGETINGONE filing.
TARGETINGONE filed
Application 79343943 filed at the USPTO.Opposition filed
Target Brands, Inc. started opposition 91293513 at USPTO against TARGETINGONE.
Marks
Marks involved
1 contested mark, 13 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| TARGETINGONE | Contested | 79343943 | USPTO |
| TARGET | Relied on | 72276713 | USPTO |
| TARGET | Relied on | 72276714 | USPTO |
| TARGET | Relied on | 73495553 | USPTO |
| SUPER TARGET | Relied on | 74532774 | USPTO |
| TARGET | Relied on | 76418297 | USPTO |
| TARGET | Relied on | 76473313 | USPTO |
| TARGET | Relied on | 78897761 | USPTO |
| TARGET | Relied on | 85031149 | USPTO |
| TARGET STYLE | Relied on | 85230338 | USPTO |
| TARGET | Relied on | 86706187 | USPTO |
| TARGET | Relied on | 87850818 | USPTO |
+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_4de5f9ee-3812-4ed6-b593-a5a51c3dbd38
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_4de5f9ee-3812-4ed6-b593-a5a51c3dbd38",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91293513",
"status": "other",
"office_code": "US",
"filed_date": "2024-08-21",
"parties": [
{
"name": "Target Brands, Inc.",
"role": "opponent"
},
{
"name": "TargetingOne Corporation",
"role": "respondent"
}
]
}