HubSpot API Validation Rules: What Version 2026-09 Breaks

Key takeaways
Since September 8, 2026, HubSpot API version 2026-09 enforces conditional required properties and required create record fields on integration writes. Portals without such rules see no change. Admins should list required fields per object, ask each vendor which API version it calls, and decide per rule whether the rule or the integration changes.

Since September 8, 2026, the required fields your admin set in HubSpot also bind every integration that writes through API version 2026-09. A form sync or an enrichment tool that skips one of those fields no longer creates a half-filled record. It gets a validation error, and the record never arrives.

That is the whole change behind the phrase “HubSpot API validation rules”: rules that used to stop only people in the HubSpot UI now stop integrations too. If your portal has no conditional required properties, no required fields on the create record form and no association permission limits, HubSpot says nothing changes for you. Everyone else needs one decision per rule.

What changed in HubSpot API validation rules

HubSpot’s developer changelog describes the change. Starting with the /2026-09/ API version, HubSpot enforces admin-configured rules on CRM API writes. Before that, the API ignored them.

  • Conditional required properties. A property that becomes required when another property has a certain value is now required for the API as well. A write without it returns a validation error.
  • Required fields on the create record form. Properties marked required in the object’s create record settings are enforced when an integration creates a record.
  • Edit Associations permission. For apps installed with user-level OAuth, association writes fail if the installing user lacks that permission. Portal-level app tokens are not affected.

One correction matters. On October 27, 2026, HubSpot updated the changelog: required associations are enforced only in the app UI, not on public API writes. Required properties from the create record settings are enforced. As of November 2026, the changelog ties enforcement to version 2026-09 and does not say how older versions behave, so ask each vendor which version their app calls.

Who this matters for

The change matters to the person who set the required fields and the person who owns the integration, and in most teams those are two different people. The admin or RevOps lead made a field required so that reps fill it in. The marketing ops lead or a vendor owns the form sync, the enrichment tool or the product data feed that creates contacts and deals.

Revenue leaders feel it later. A rejected write leaves no record at all, and a lead that is not in the CRM does not get routed, followed up or counted in the pipeline report.

What to check in your portal

  1. Open the create record settings for each object you sync. Per the HubSpot Knowledge Base, go to Settings, then Data Management, then Objects, and choose the object. Under the Creating section, click the link to customize the create form.
  2. Write down every property marked required on that form.
  3. In the same form, look for conditional logic. Conditional logic needs a Professional or Enterprise subscription and makes a dependent property appear or become required when a dropdown-type property has a certain value.
  4. List every integration that creates or updates records of that object: forms, enrichment, billing or product data, imports through apps.
  5. For each pair of rule and integration, mark whether the integration sends that field. Where nobody knows, that is the first question for the vendor.

What to ask your developer or integration vendor

  • The HubSpot API version the integration calls today, and when it moves to 2026-09 or later.
  • Whether it reads the portal’s property requirements before writing or relies on a fixed field list.
  • What happens to a record HubSpot rejects: retried with the missing value, logged, or lost.

A vendor who cannot say what happens to a rejected record has not handled this change yet.

Our take

A required field is a process rule. Until September, it applied to people, not to integrations. Version 2026-09 closes that gap, and we think that is good: a CRM where the rules hold for every source is easier to trust.

The decision this change forces is organisational, not technical. When a rule and an integration disagree, someone must choose between relaxing the rule and changing the integration, and that person is usually not the developer. Only the owner of the process knows which field the business truly needs at creation.

Our rule of thumb: a field the integration cannot know at the moment of creation should not be required at creation. Move it to a later stage, a pipeline step or a review task, and keep the create rule for what every source really has. Decide per rule before the integration upgrades. If you have not picked a source of truth for each field yet, our note on choosing a source of truth for HubSpot data is the place to start. The legacy API retirement in 2027 is the sibling change on a longer clock.

Implementation

Planning a HubSpot rollout or a migration?

We set up pipelines, data and onboarding so the team actually uses it.

Plan your rollout

FAQ

Why is my HubSpot integration suddenly failing with a validation error?

The integration most likely writes through API version 2026-09 or later and skips a property your portal marks as required. Since September 8, 2026, HubSpot enforces conditional required properties and required create record fields on those writes, and returns a validation error naming the missing property.

Are HubSpot required associations enforced on API writes?

No. HubSpot’s correction of October 27, 2026 says required associations are enforced only in the app UI, not on public API writes. Required properties from the create record settings are enforced.

Who should decide whether to change a HubSpot validation rule or the integration?

The owner of the process the field supports, usually the RevOps lead or the head of the team that uses the field. The developer implements the choice. If nobody owns the field, settle that first, then decide.

This week, list the required fields on the create form of every object an integration writes to, and send your vendors the questions above. The answers tell you which rules to keep and which to move before the next missing lead is noticed.

Alignify

Alignify is a HubSpot implementation and admin team. We set up portals, clean up CRM data and run HubSpot as a service for B2B companies.

On this page

Get the audit checklist

All 25 checks as a spreadsheet with auto-scoring.

By submitting, you agree to our Privacy Policy.

Talk to Alignify

45 minutes, your portal on screen, no slides. We show what we would fix first.

Want a second set of eyes on your HubSpot?

Book a 45-minute portal review. We look at your portal together on a screen share and show what we would fix first. No slides, no sales pitch.