Seekapedia: API data sets

APIs / Cannabis License API

Cannabis License API

The same schema, checks and change feed as the Liquor License API, for state cannabis license records. Look up a license by number, search by name, check up to 500 at once, keep portfolios under watch, and get a webhook when a license changes. A license here is a state license only; federal law still treats cannabis as a controlled substance, and each state regulates it differently.

What you can do

  • Verify one license by state and number: status, expiration date, and whether that date has passed.
  • Verify in bulk: up to 500 licenses in one request.
  • Search by legal or trade name, optionally within one state.
  • Read changes: new licenses, status changes, renewals and removals from each daily sync.
  • Watch a license and receive a signed webhook when it changes, with delivery history, replay and test events.
  • Check a business by identifier or by name and address, and keep the result as saved evidence.
  • Monitor portfolios with an exception queue for anything that needs a person.
  • Apply your own policy, kept separate from the data result, in versioned rules.
  • Export whole snapshots, page by page, with signed cursors.

Endpoints

Look up

  • Turn a state and license number into a license record GET /v1/verify
  • Turn a list of up to 500 licenses into results POST /v1/verify/batch
  • Turn a business name into candidate licenses GET /v1/search

Check and keep evidence

  • Turn a business name and address into a saved check POST /v1/checks
  • Re-judge a saved check under another policy POST /v1/checks/{id}/reevaluate

Watch and monitor

  • Turn licenses into watches with signed webhooks POST /v1/watches
  • Turn a portfolio into a queue of exceptions GET /v1/portfolios/{id}/exceptions

History and change

  • See what changed in the latest update or since a time GET /v1/changes
  • Read the recorded history of one license GET /v1/history
  • See a license as it stood on a past date GET /v1/as-of

Free, no key

  • Coverage, record counts and freshness warnings GET /v1/health
  • Each agency source and whether it is current GET /v1/sources
  • Every daily update and what changed in it GET /v1/releases

Every endpoint is also an AI tool where it makes sense, and the full reference is in the docs.

Statuses

Each state words its statuses differently. We map them to one set: active, expired, suspended, cancelled, surrendered, pending, inactive and unknown, and always include the state's own wording too.

Reading an answer

Every answer comes with the evidence to judge it. Read these before relying on one:

  • status is our normalized word; status_raw is the state's own. Quote both.
  • expiration_passed is true when the expiration date is in the past, even if the state still shows the license as active. We report both and do not decide which is right.
  • freshness.state is current, overdue or unknown: whether the source was read and published on schedule. Overdue and unknown are warnings, not errors.
  • conflicts appear when two rows in the source disagree about the same license. We show the disagreement instead of picking one.
  • found: false is a normal answer with HTTP 200. It means not found in this data, never “not licensed”.

What an answer does not mean. An active status means the state's file lists the license as active on the data date. It does not confirm the person you are speaking to is the licensee, that local permits are in place, or that the business is compliant. Enforcement actions and license conditions are not covered.

Sources