CRM API V3 improvements (compared to V1 and V2)

• Filtering capabilities for most important tables. Supported operators include =, !=, >, <, <=, >=, IN.
• Filtering using AND and OR combinations. A maximum of three OR operators are supported server-side, with each of these operators supporting up to three AND operators inside of them.
• Sorting capability for most important tables. Only one column is supported to be sorted by the API.
• Support for 'Batch' operations (Batch INSERT, Batch Update, Batch Delete).
• Support for Creating, Updating and Deleting Custom HubSpot Objects (tables) and Properties (columns).

CRM API V3 limitations

• Filtering is available only when the number of rows to be returned is less than 10,000. If there are more rows to be returned for the query then all rows will be retrived first and filtering is then applied on them by the driver
• When issuing either filtering requests or sorting requests, no more than one request/second is allowed.
• A few columns (such as "CreatedAt" and "UpdatedAt") do not support filters.
• The stored procedures to Create/Update custom objects may not work for the OAuth Authentication Scheme, since the OAuth apps are limited to the read-only access scope for custom objects. To work around this limitation, you can connect via a Private App Token.
• You cannot request custom object types by their base name. All custom object types must be referenced by their fully qualified object type name or their short-hand custom object type name (p_<object_name>).