HubSpot app-hsmeta.json Structure Checklist

`app-hsmeta.json` is a key app schema file in Projects-based app workflows. Confirm the file exists in the expected project structure for the app path you are using, and review it together with `hsproject.json` rather than as an isolated JSON file.

Review app UID, auth fields, redirect URLs, scopes, and related feature configuration before upload or migration. If a developer changes identifiers casually, the project can become difficult to reason about during install testing or handoff.

Use official create-app, project command, and migration docs for exact structure. This page is a checklist for what to inspect, not a schema reference that replaces HubSpot's documentation.

If upload or local development fails, first confirm you are in the project root and that the expected config files are present. Then compare the app's current structure against the official docs for the selected platform version.

For OAuth apps, compare redirect URLs and scopes with the target account and install flow. For Marketplace apps, ensure public-facing support and privacy materials are ready before treating the technical config as complete.

For migrated apps, preserve a record of old and new identifiers, feature files, and platform-version changes. That record is often more useful to a second developer than a vague 'migration completed' note.

Do not infer official approval from a valid-looking `app-hsmeta.json`. Marketplace listing readiness and platform behavior must still be checked through official docs and the HubSpot review process.

Do not infer that every private app can be moved by copying the same file structure. Private app migration has separate limitations and may require manual planning.

Do not treat this file checklist as proof that an existing legacy public app stops functioning under the May/June creation sunset. That sunset is about creating new legacy public apps.