Opposition · USPTO

Opposition 91216086

OtherUSPTO

Opposition 91216086 at USPTO between Karisma Hotels & Resorts Corporation, Ltd. and Riviera Mi Vida, S. de R.L., over the mark CABO AZUL, filed Apr 25, 2014. Status in the office record: other.

View CABO AZULGet this data via the API
Status
Other
Result
Other
Filed
Apr 25, 2014
Marks involved
7
Parties

Who is involved

The parties as named in the office record.

Opponent

Karisma Hotels & Resorts Corporation, Ltd.

Company trademarks
Respondent

Riviera Mi Vida, S. de R.L.

Timeline

How the case has moved

Dates from the USPTO record and the CABO AZUL filing.

  1. CABO AZUL filed

    Application 86077476 filed at the USPTO.

  2. Opposition filed

    Karisma Hotels & Resorts Corporation, Ltd. started opposition 91216086 at USPTO against CABO AZUL.
Marks

Marks involved

1 contested mark, 6 marks the challenger relies on.

MarkRoleApplicationOffice
CABO AZULContested86077476USPTO
AZUL FIVES HOTELRelied on77440062USPTO
AZULRelied on85533556USPTO
AZULRelied on85536726USPTO
AZUL BEACHRelied on85611529USPTO
AZUL VILLA CAROLARelied on85611531USPTO
AZUL FIVESRelied on85611536USPTO
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 API keyView docs
GET /v1/proceedings/{id}
ID=prc_4be493a7-4833-4c30-a928-abf1117909ef
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4be493a7-4833-4c30-a928-abf1117909ef",
  "object": "proceeding",
  "proceeding_type": "opposition",
  "proceeding_number": "91216086",
  "status": "other",
  "office_code": "US",
  "filed_date": "2014-04-25",
  "parties": [
    {
      "name": "Karisma Hotels & Resorts Corporation, Ltd.",
      "role": "opponent"
    },
    {
      "name": "Riviera Mi Vida, S. de R.L.",
      "role": "respondent"
    }
  ]
}