canonical: https://jentic.com/apis/hubspot.com/hubspot-crm-buckettest111 # HubSpot Bucket_Test111 The HubSpot Bucket_Test111 API exposes a custom CRM object type used internally by HubSpot for bucket-style record collections. It provides full CRUD plus search and batch operations against the bucket_test111s object set within the standard CRM v3 object model. Records can be created, archived, merged with other CRM data, and queried alongside contacts, companies, and deals using the same association graph. ## For AI agents Read, create, update, archive, and search HubSpot bucket_test111 CRM records via the standard CRM v3 objects pattern, including batch operations and filtered search. ## Scope Does not handle deals, tickets, or marketing email - use for the bucket_test111 custom CRM object only. ## Capabilities - Read bucket_test111 records in batches by record ID using POST /crm/v3/objects/bucket_test111s/batch/read - Create new bucket_test111 records individually or in batches with property maps - Update existing bucket_test111 records by ID using PATCH operations - Archive bucket_test111 records in batch to remove them from active CRM views - Search bucket_test111 records with filter groups, sorts, and property selection - Page through the full list of bucket_test111 records with cursor-based pagination - Retrieve a single bucket_test111 record by ID with selected associated objects ## Use cases ### Custom Bucket Record Sync Sync bucket_test111 records between HubSpot CRM and an internal warehouse so analytics tooling can join bucket data with contacts and companies. The batch read and batch upsert endpoints handle up to 100 records per request, keeping sync jobs efficient even at scale. Example prompt: Call POST /crm/v3/objects/bucket_test111s/batch/read with a list of 50 record IDs and write the returned property maps to the warehouse staging table. ### Bulk Record Cleanup Identify stale bucket_test111 records using the search endpoint with a lastmodifieddate filter, then archive them in batch. Useful for routine CRM hygiene where bucket records older than a threshold should be removed from active views without permanent deletion. Example prompt: Search bucket_test111 records where hs_lastmodifieddate is older than 365 days, then POST the resulting IDs to /crm/v3/objects/bucket_test111s/batch/archive. ### Property-Based Lookup Look up specific bucket_test111 records by a custom property value rather than internal ID using the search endpoint with filter groups. This pattern supports lookups by external system ID, status, or any indexed custom property exposed on the bucket object schema. Example prompt: POST a search to /crm/v3/objects/bucket_test111s/search with filterGroups for external_id equals "EXT-12345" and return the matching record ID. ### AI Agent CRM Custom Object Workflow An AI agent uses Jentic to discover and call HubSpot bucket_test111 endpoints without browsing developer docs. The agent searches Jentic for the bucket operation it needs, loads the input schema, and executes the call with credentials handled by your Jentic One instance. Example prompt: Use Jentic search for "create a hubspot custom bucket record", load the schema for the create operation, and execute it with property values from the upstream task. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /crm/v3/objects/bucket_test111s/batch/read | Read bucket_test111 records in batch by ID | | POST | /crm/v3/objects/bucket_test111s/batch/create | Create bucket_test111 records in batch | | POST | /crm/v3/objects/bucket_test111s/batch/update | Update bucket_test111 records in batch | | POST | /crm/v3/objects/bucket_test111s/batch/archive | Archive bucket_test111 records in batch | | POST | /crm/v3/objects/bucket_test111s/search | Filter, sort, and search bucket_test111 records | | GET | /crm/v3/objects/bucket_test111s/{bucketTest111Id} | Retrieve a single bucket_test111 record | | GET | /crm/v3/objects/bucket_test111s | List bucket_test111 records with pagination | ## Key resources - **bucket_test111s** — Custom CRM object collection supporting read, create, update, archive, search, and batch operations. - **Batch operations** — Batch read, create, update, and archive endpoints for processing up to 100 records per call. - **Search** — Filter, sort, and paginate bucket_test111 records by any property using filter groups. ## Why Jentic - **Setup:** Wiring the HubSpot bucket_test111 custom object by hand means registering an OAuth app or minting a private app token, targeting api.hubapi.com, and coding the batch read, create, update, and search calls plus paging yourself. Through Jentic you install once, import Bucket_Test111 from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** The bucket_test111 object puts the record id in the URL path (/crm/v3/objects/bucket_test111s/{bucketTest111Id}) for reads, while writes run through batch endpoints that take a request body, so scope your agent to the operations it needs, such as reading or searching records. You choose the operations it may call, so batch archive is not included unless you add it. - **Credential handling:** Your HubSpot OAuth token or private app 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 'create a HubSpot bucket_test111 record' or 'search bucket_test111 records', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **CRM Custom Objects** — Define and manage custom object schemas that bucket-style records like bucket_test111 are built on. - **Contacts** — Standard CRM contacts object - commonly associated with custom bucket records. - **Salesforce** — Salesforce custom objects offer the same custom-record pattern at enterprise scale. ## FAQ ### What authentication does the HubSpot Bucket_Test111 API use? The Bucket_Test111 API supports OAuth 2.0 (oauth2 and oauth2_legacy) and HubSpot private app tokens passed as bearer tokens. Through Jentic, credentials are stored in your Jentic One instance and scoped tokens are injected at execution time so the raw token never enters the agent context. ### Can I batch update bucket_test111 records with the HubSpot Bucket_Test111 API? Yes. POST to /crm/v3/objects/bucket_test111s/batch/update with up to 100 inputs per request, where each input contains the record id and a properties map. The response returns each updated record or per-record errors. ### What are the rate limits for the HubSpot Bucket_Test111 API? HubSpot enforces account-wide CRM API limits - typically 100 requests per 10 seconds for OAuth apps and 110 per 10 seconds for private apps on Pro and Enterprise. Batch endpoints count as a single request, so prefer batch read and batch update over per-record loops. ### How do I search bucket_test111 records through Jentic? Run the Jentic search query "search hubspot bucket records" to locate the operation backed by POST /crm/v3/objects/bucket_test111s/search, load its input schema, then execute with a filterGroups payload. No manual auth wiring is required. ### Is the HubSpot Bucket_Test111 API free to use? Access is included in any HubSpot account that has the bucket_test111 object enabled, but custom object support generally requires Enterprise tier. There is no separate per-call fee from HubSpot for these endpoints. ### Can I associate bucket_test111 records with contacts or companies? Yes - pass an associations array on create or use the CRM Associations API to link bucket_test111 records to contacts, companies, or deals. The single-record GET supports an associations query parameter to return linked object IDs in one call. ### Can I limit what my agent is allowed to do with the HubSpot Bucket_Test111 API? Yes. Because Jentic One is self-hosted, you decide which bucket_test111 operations your agent may call, so you can allow read-only access such as GET /crm/v3/objects/bucket_test111s/{bucketTest111Id} and POST /crm/v3/objects/bucket_test111s/search while withholding the write and batch endpoints. Destructive operations like POST /crm/v3/objects/bucket_test111s/batch/archive stay unavailable unless you explicitly add them. Your HubSpot OAuth or private app token is held by your own instance and injected only at execution time, and your rules determine which credentials each agent may use.