---
title: "Download and update the developer kit"
section: "Developer Platform"
canonical_url: "https://support.buildwithhq.com/api/choose-your-developer-kit.html"
reviewed_at: "2026-09-14"
authority: Official
---

# Download and update the developer kit

Use one portable Developer Kit, then synchronize authorized account contracts inside its workspace.

## In brief

- **Developer kit:** 1.20.70
- **Account sync:** Generated live
- **Credentials:** External only

There is one canonical BuildWithHQ / API43 Developer Kit. Use it to build a website, trusted backend integration, or custom frontend for your SaaS, then run its account-sync tool when you need one account’s current pages, presentation, bindings, compatibility data, Lego catalogs and tenant route metadata in the same working directory.

## Download the current Developer Kit

The current release is **1.20.70**. [Download Developer Kit 1.20.70](../downloads/BuildWithHQ-API43-Developer-Kit-1.20.70.zip). Download its [SHA-256 checksum](../downloads/BuildWithHQ-API43-Developer-Kit-1.20.70.zip.sha256)  and verify the ZIP before extracting it. The public ZIP requires no tenant-admin permission to download. The archive includes OpenAPI, the SDK, React and Puck examples, API instructions, executable integration examples, and `tools/sync_account_overlay.py`. It contains no database credentials or API tokens. Calling protected APIs requires the appropriate key, identity, scopes and record-level permissions.

## Configure draft and live keys on your server

Create separate `bwk_draft_` and `bwk_live_` API clients, then store both credentials in a backend secret manager. Never put either credential in React, a `VITE_*` variable, page JSON, source control, or the downloaded ZIP. Existing kit tools read `BWHQ_API_CREDENTIAL` for the current operation: point it at the draft credential for unpublished page work and at the live credential only for reviewed live operations.

The account overlay contains tenant-specific information. Its sync uses a short-lived bearer from the real tenant sign-in flow and requires owner access or delegated Developer Kit and design capabilities; a long-lived app key alone does not authorize it. Set `BWHQ_TENANT_ORIGIN` and `BWHQ_TENANT_ACCESS_TOKEN`, then run `python tools/sync_account_overlay.py`. The tool verifies every manifest hash before atomically writing `account-overlay/` and never stores the token.

## Read version numbers as separate parts

Versions use `major.minor.patch`, not decimal numbers. Version `1.20.70` is later than `1.9` and `1.2`: minor version 20 comes after 9 and 2. Old release notes deliberately retain their original versions; they do not identify the latest download.

## Synchronize account-specific files

The generated account overlay contains the published capability and tenant-operation catalogs available to the authorized account, plus current pages, menus, bindings, compatibility data, ID-addressed Lego catalogs, React starters, and Contacts and Work Orders composite samples. Use the generated manifest and [API Map](api-map.html)  for the current inventory; the public kit and the live account overlay can reflect different release dates. Built-in capabilities are not hidden merely because they are not pinned to a menu. The direct **Admin → Developer kit** ZIP download remains available for compatibility and can be verified and expanded with the tool’s `--archive` option. See [Account administration](../end-user/account-administration.html)  for its contents and setup.

## Upgrade without losing your customizations

1. Read the [release notes](../changelog/index-notes.html)  and keep your existing project in source control.
2. Extract the new ZIP into a separate directory. Compare its OpenAPI, manifest, SDK, and examples with the version you use.
3. Merge relevant changes into your project; do not overwrite custom pages or configuration with sample files.
4. Run the checks documented in the kit and verify your integration against your test account before deployment.

The kit version identifies the downloadable package. API URLs still use their documented `/v1/` prefix; a new ZIP does not change the route version. See [API operating contracts](api-operating-contracts.html)  for contract fingerprints and compatibility.

## Start with your task

- [Make your first API request](quickstart.html).
- [Sign up customer organizations from your website](customer-organization-website-signup.html).
- [Customize React, CSS, and page design](../builder-guide/tailadmin-template-design-and-react-customization.html).
- [Receive webhooks and poll background jobs](webhook-receiver-and-background-jobs.html).

---

Capability review: 2026-09-14. [View the canonical guide](https://support.buildwithhq.com/api/choose-your-developer-kit.html).