canonical: https://jentic.com/apis/hubspot.com/hubspot-crm-property-validations # HubSpot CRM Property Validations The HubSpot CRM Property Validations API reads the validation rules HubSpot enforces on the properties of a CRM object - pattern checks, length constraints, enumerated value lists, and other input rules. It exposes a single object-type-level endpoint that returns every validation rule for the object's properties, plus a property-level endpoint that returns the rule for one named property. Use it to mirror HubSpot's validation logic in an external form, prevent failed writes by validating input client-side before calling the CRM Objects API, and document the input contract for downstream agents. ## For AI agents Read the validation rules HubSpot applies to CRM object properties so agents can validate input client-side before issuing writes. ## Scope Does not create, update, or delete validation rules and does not validate input itself - use for reading existing HubSpot CRM property validation rules only. ## Capabilities - Retrieve every validation rule defined for the properties of a given object type - Read the validation rule attached to a single named property - Inspect pattern, length, and enumeration constraints on a property - Mirror HubSpot's validation contract in an external form before submission - Document the input contract for downstream tools that write to HubSpot - Detect when a property has changed validation rules in a portal ## Use cases ### Client-side input validation Validate user input before calling the CRM Objects API to write a record. GET /crm/v3/property-validations/{objectTypeId} returns every rule the portal enforces for an object type. The agent applies the same rules locally so a write only goes out once it would actually pass server-side. Example prompt: GET /crm/v3/property-validations/0-1 (the contacts object type ID) and apply each returned rule to user input before issuing a PATCH. ### Validation contract documentation Generate documentation for an internal portal that shows every validation rule on every property of an object type. Useful for support engineers and integration partners who need to know what input HubSpot will accept without trial and error. Example prompt: GET /crm/v3/property-validations/{objectTypeId} for each object type the portal cares about and render the result as a Markdown table. ### Single-property rule lookup Fetch the validation rule for one specific property - for example to display a helpful error message when an input fails. GET /crm/v3/property-validations/{objectTypeId}/{propertyName} returns just the rule for the named property without iterating the full object type. Example prompt: GET /crm/v3/property-validations/0-1/email and extract the regex pattern and any allowed-domain rule it returns. ### AI agent execution through Jentic An agent that needs to validate input before writing to HubSpot discovers this API via Jentic's intent search using a query like 'read hubspot property validation', loads the input schema for the chosen operation, and executes the call with credentials supplied from your Jentic One instance. The result then conditions which CRM Objects write the agent makes next. Example prompt: Search Jentic for 'read hubspot property validation', load GET /crm/v3/property-validations/{objectTypeId}, and execute it for the contacts object type. ## Key resources - **Public_Property_Validations** — Read validation rules at object-type and per-property level ## Why Jentic - **Setup:** Wiring CRM Property Validations by hand means implementing HubSpot's OAuth2 authorization-code flow (or managing a private-app header token), routing read calls to api.hubapi.com with the right objectTypeId, and parsing the validation-rule response yourself. Through Jentic you install once, import CRM Property Validations from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** This API is read-only, exposing existing validation rules addressed by an objectTypeId in the URL path. Limit the agent to the operations it needs, such as reading validation rules, so it only inspects the rules you intend and performs no writes. - **Credential handling:** Your HubSpot token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'read HubSpot property validation rules', and Jentic returns the matching operation with its objectTypeId path parameter contract so the agent supplies the right id and calls the endpoint without browsing the reference docs. ## Related APIs - **HubSpot CRM Properties** — Manages the properties whose validation rules this API exposes - **HubSpot CRM Objects** — Writes record values that need to satisfy the rules this API returns - **HubSpot CRM Custom Objects** — Defines custom object types whose property validations can be read here ## FAQ ### What authentication does the HubSpot Property Validations API use? It accepts OAuth 2.0 access tokens and private app access tokens passed as a Bearer credential in the Authorization header. Both endpoints are read-only; standard CRM read scopes are sufficient. ### Can I create new validation rules through this API? No. The API is read-only - it exposes two GET endpoints. Validation rules themselves are configured through HubSpot's property settings UI or via the Properties API. ### What are the rate limits for the HubSpot Property Validations API? It shares HubSpot's account-level rate limits, typically 100 requests per 10 seconds for OAuth apps. Cache the rules locally - they change rarely - to avoid hitting the limit on high-volume validation paths. ### How do I read every validation rule on contacts through Jentic? Search Jentic with 'read hubspot property validation', load GET /crm/v3/property-validations/{objectTypeId}, and execute with objectTypeId=0-1 (the system ID for the contacts object). The response returns each property's rule. ### Is the HubSpot Property Validations API free? It is included with all HubSpot accounts that have CRM access enabled. There is no per-call fee; the standard account-level rate limits apply. ### What does the response look like for a property with no rule? Properties without an explicit validation rule return either an empty rule object or are omitted from the object-type-level response entirely. Treat absence as 'no constraint beyond the field type itself'. ### Can I limit what my agent is allowed to do with the HubSpot Property Validations API? Yes. Because you run your own self-hosted Jentic One instance, your rules decide which operations and credentials the agent may use. This API exposes only two read-only GET operations that return validation rules by objectTypeId, so you can grant the agent just the rule-reading operation and confirm it can never create, update, or delete rules or write records. You can also restrict which objectTypeId paths the token permits, keeping the agent to the objects you intend it to inspect.