March 2026 Rollup

This month's rollup introduces exciting updates designed to streamline developer workflows and enhance visibility. Key highlights include the ability to view app objects directly within the Data Model Builder and a faster, video-based review process for App Cards. There are also three new public betas: a File Ingestion API for bringing raw tabular data into Data Studio, substantial feature enhancements and reliability fixes for the Conversations API, and a new Connection Insights tab to help you monitor app and integration activity at a glance.

Developer Updates for March 2026

New features for app objects: View in data model builder and add pipeline rules

To help you make the most of app objects, you can now view them in your data model builder alongside standard CRM objects and custom objects. This helps you understand how app objects interact and are associated with other CRM objects.

There are also three new pipeline rules for app objects. These rules can be configured individually in the app object’s settings:

• Limit record creation to specific stages
• Restrict records from skipping stages
• Restrict records from moving backwards

Adding pipeline rules ensures everyone in an account follows standard processes.

App card review updates

The App Card Review Program is being updated with an improved process for reviewing and approving CRM UI extension app cards submitted by marketplace partners before they go live. This updated process replaces a longer, more complex review with a standardized, video-based submission and evaluation.

The current process requires that a HubSpot review team be added as a super admin to a test account with the app card installed.

The updated process still begins with submitting the review form, but replaces the super admin manual review with an updated testing video review. The video must cover the complete functionality of the app card, as it will be reviewed against our updated quality categories and requirements.

This updated process will lead to more consistent feedback for partners, as well as a faster turnaround on marketplace applications. Please check the listing requirements and process documentation for more details as this new process is rolled out in the near future.

Public Betas

New file ingestion API beta for Data Studio

You can now use a new File Ingestion API that enables developers to upload static tabular data (CSV, XLS(X), TSV) as reusable data sources in HubSpot’s Data Studio. This API provides a developer-friendly, schema-agnostic way to bring structured data into HubSpot without mapping it to CRM objects.

What's new?

New endpoints:

• Create a data source: POST /data-studio/data-source/beta/
• Update (overwrite) a data source: PUT /data-studio/data-source/2026-9-beta/{datasourceId}
• Retrieve a data source: GET /data-studio/data-source/2026-9-beta/{datasourceId}
• Delete a data source: DELETE /data-studio/data-source/2026-9-beta/{datasourceId}

Key capabilities introduced:

• API-Driven File Imports: Upload CSV, XLS, XLSX, or TSV files (up to 512 MB) into Data Studio as named, reusable data sources.
• Schema-Agnostic Ingestion: Load raw tabular data without mapping to CRM objects.
• Flexible Column Typing: Define column data types explicitly using supported types:
  • STRING
  • INTEGER
  • DECIMAL
  • DATE (YYYY-MM-DD)
  • DATETIME (ISO 8601 format)
  • BOOL
• Overwrite-Based Updates: Update an existing file-based data source by uploading a new file.
  • The new file must include all existing fields.
  • Additional fields may be added.
  • Existing fields cannot be removed.
  • If no new configuration is provided, the existing schema is retained.
• Non-CRM Focus: This API is purpose-built for general datasets in Data Studio and is not tied directly to CRM object schemas.

What does this mean for developers?

Developers can now define a reusable external data source and programmatically manage it through the API.

To update data:

• Create a data source using POST /data-studio/v1/data-source
• Upload a new file via the versioned PUT endpoint to overwrite the existing data
• Ensure the updated file maintains schema compatibility.

All files uploaded to the same data source must maintain a consistent schema. Missing existing fields will cause the update request to be rejected. This API provides a dedicated pathway for managing non-CRM datasets in Data Studio and may serve as a forward-looking alternative to the Imports API for relevant use cases.

Note: Developers managing non-CRM datasets in Data Studio should use this API instead of (or alongside) the Imports API where appropriate. Ensure:

• Unique datasourceName values within the HubSpot Account
• Schema consistency across updates
• All required OAuth scopes are included.

Refer to the full API documentation for complete details on requests and responses.

Conversations API beta enhancements

The latest Conversations API (BETA) update includes several of your top-requested enhancements, important reliability fixes, and a Help Desk sunset reminder. Below is a complete breakdown of what’s changing, why it matters, and what developers can look forward to.

What's changing?

New Features:

• Assign or Unassign a User to a Thread: Developers now have direct access to assigning users to threads. This can be helpful if you have designed a bot to respond to messages, but need to hand the conversation off to a human.
  • PUT conversations/v3/conversations/threads/{threadId}/assignee
  • Accepts a JSON object with a single ‘actorId’ element in the request
  • DELETE conversations/v3/conversations/threads/{threadId}/assignee
• Identify what type of inbox: Inbox endpoints now include a type property to indicate whether a lowercase i inbox is a Conversations Inbox or a Help Desk:
  • Values are INBOX or HELP_DESK
  • Applies when resolving a lowercase i inboxId
• Check whether a thread is associated with a ticket: Thread endpoints now support explicitly requesting ticket association data:
  • New optional query param: association=TICKET
  • Available on the GET threads and the GET single thread endpoints
  • Responses may include a threadAssociations array with the associatedTicketId property
  • Example Response:
    
    

• Retrieve all threads for a specific ticket: You can now fetch threads associated with a given ticket:
  • New optional query param on GET threads: associatedTicketId=12345
  • Supports sorting by id and latestMessageTimestamp
  • Enables common Help Desk workflows, such as “show all conversations for this ticket”.
• New actor type: L (LLM): GET actor endpoints now expose actor type L (short for “LLM”), representing HubSpot’s Customer Agent.

Bug Fixes:

Several issues have been resolved to improve consistency and reliability across thread retrieval and messaging:

• threadStatus filtering now works reliably in all cases.
• Resolved inconsistent behavior when filtering by inboxId and sorting by latestMessageTimestamp.
• All threads now return when filtering by associatedContactId (previously only OPEN) and sorting by latestMessageTimestamp.
• Removed user-level permissions check that previously resulted in POST message requests to Help Desk Channels failing.
• Resolve the issue preventing the retrieval of more than 100 messages when timestamps were identical.

Sunset Reminder:

Help Desk is moving away from the legacy internal thread comments feature (shared with Conversations Inbox) and transitioning to Notes. As a result, posting and retrieving thread comments via the Conversations API will be sunset for Help Desk-connected channels. Developers should instead use:

• Notes API (to create/read notes)
• Associations API (to associate Notes with Tickets)

Important Note: Thread comments will continue to work for Conversations Inbox. For full details and timelines, see the dedicated sunset announcement here.

What does this mean for developers?

The Conversations API enables Smart CRM use cases such as exporting or archiving conversations, analyzing unstructured customer interactions with AI, mirroring Inbox or Help Desk conversations into external tools like Slack, supporting internal collaboration via comments or Notes, and powering translation workflows. Developers can discover inboxes and channels, retrieve and filter threads and messages, and post outbound messages and internal comments (Inbox only). For more information, please refer to HubSpot’s Developer Documentation.

Connections insights

Connection Insights is a new tab in Connected Apps that provides a high-level, centralized view of how your apps are behaving across HubSpot, at a glance. It brings together global insights about app activity, automation involvement, disconnect history, and API usage. From this tab, you can see:

• Automation insights: High-level signals that show how apps interact with automation, helping explain downstream behavior and linking you to relevant automation tools when needed.
• Record Insights: Get visibility into how your connected apps are interacting with CRM records by tracking record events (such as creates and updates) over time. Quickly understand which integrations are most active, how activity is trending, and which apps are driving the most changes in your CRM data.

This feature is currently in public beta. See the product notification for more details.

Questions or comments? Please join us in our developer forums.