Cancellation · USPTO

Cancellation 92076806

OtherUSPTO

Cancellation 92076806 at USPTO between Yeti Coolers, LLC and Nathan Seitz, over the mark YETI CAVE, filed Mar 30, 2021. Status in the office record: other.

View YETI CAVEGet this data via the API
Status
Other
Result
Other
Filed
Mar 30, 2021
Marks involved
12
Parties

Who is involved

The parties as named in the office record.

Petitioner

Yeti Coolers, LLC

Respondent

Nathan Seitz

Timeline

How the case has moved

Dates from the USPTO record and the YETI CAVE filing.

  1. YETI CAVE filed

    Application 86756556 filed at the USPTO.

  2. YETI CAVE registered

  3. Cancellation filed

    Yeti Coolers, LLC started cancellation 92076806 at USPTO against YETI CAVE.
Marks

Marks involved

1 contested mark, 11 marks the challenger relies on.

MarkRoleApplicationOffice
YETI CAVEContested86756556USPTO
YETIRelied on78846876USPTO
YETIRelied on78975433USPTO
YETI TANKRelied on85896774USPTO
YETIRelied on85984098USPTO
YETIRelied on86161672USPTO
YETIRelied on86161730USPTO
YETIRelied on86161746USPTO
YETI HOPPERRelied on86162495USPTO
YETI COLSTERRelied on86408640USPTO
YETIRelied on86982760USPTO
YETIRelied on86982761USPTO
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_4aa81268-2f16-40fb-bc01-aca592a49723
curl https://api.signa.so/v1/proceedings/$ID \
  -H "Authorization: Bearer $SIGNA_API_KEY"
Response
{
  "id": "prc_4aa81268-2f16-40fb-bc01-aca592a49723",
  "object": "proceeding",
  "proceeding_type": "cancellation",
  "proceeding_number": "92076806",
  "status": "other",
  "office_code": "US",
  "filed_date": "2021-03-30",
  "parties": [
    {
      "name": "Yeti Coolers, LLC",
      "role": "petitioner"
    },
    {
      "name": "Nathan Seitz",
      "role": "respondent"
    }
  ]
}