Opposition 91246113
OtherUSPTO
Opposition 91246113 at USPTO between Argus Media Limited and Argos Global Partner Services LTDA, over the mark ARGOS GLOBAL PARTNER SERVICES, filed Jan 29, 2019. Status in the office record: other.
- Status
- Other
- Result
- Other
- Filed
- Jan 29, 2019
- Marks involved
- 8
Parties
Who is involved
The parties as named in the office record.
Opponent
Argus Media Limited
Respondent
Argos Global Partner Services LTDA
Timeline
How the case has moved
Dates from the USPTO record and the ARGOS GLOBAL PARTNER SERVICES filing.
ARGOS GLOBAL PARTNER SERVICES filed
Application 87546985 filed at the USPTO.Opposition filed
Argus Media Limited started opposition 91246113 at USPTO against ARGOS GLOBAL PARTNER SERVICES.
Marks
Marks involved
1 contested mark, 7 marks the challenger relies on.
| Mark | Role | Application | Office |
|---|---|---|---|
| ARGOS GLOBAL PARTNER SERVICES | Contested | 87546985 | USPTO |
| ARGUS AIR DAILY | Relied on | 77279887 | USPTO |
| ARGUS MEDIA | Relied on | 78621675 | USPTO |
| ARGUS | Relied on | 78649426 | USPTO |
| ARGUS | Relied on | 79071887 | USPTO |
| ARGUS | Relied on | 79071888 | USPTO |
| ARGUS OPEN MARKETS | Relied on | 79176708 | USPTO |
| ARGUS DIRECT | Relied on | 79179111 | USPTO |
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_d8d55ed3-2eba-4ec1-a579-8721bdfdab83
curl https://api.signa.so/v1/proceedings/$ID \
-H "Authorization: Bearer $SIGNA_API_KEY"Response
{
"id": "prc_d8d55ed3-2eba-4ec1-a579-8721bdfdab83",
"object": "proceeding",
"proceeding_type": "opposition",
"proceeding_number": "91246113",
"status": "other",
"office_code": "US",
"filed_date": "2019-01-29",
"parties": [
{
"name": "Argus Media Limited",
"role": "opponent"
},
{
"name": "Argos Global Partner Services LTDA",
"role": "respondent"
}
]
}