| Products | Versions |
|---|---|
| TIBCO Scribe Online | All |
Once the hotfix is deployed to your organization it’s imperative that customers review the below changes to ensure their integrations continue to run.
Refresh Metadata
Once the hotfix is applied, all customers must refresh their metadata within the application. This ensures your local schema is synced with the new v3 endpoints and that the new fields are visible in your environment. Instructions for how to refresh the metadata for your hubspot connection can be found in our help documentation.
HubSpot is transitioning from Legacy V1 List IDs to ILS Segment IDs. Depending on the entity you are querying, the ID requirements have changed:
Action / Entity | Field Name | ID Type Required |
Querying ContactLists | listid | ILS Segment ID (New) |
Updating/Deleting Lists | listid | ILS Segment ID (New) |
Querying Contacts | contactlistid | Legacy V1 List ID |
Querying Contacts | ilslistid | ILS Segment ID (New) |
Note: When managing lists directly (updating/deleting), the system now strictly expects the ILS Segment ID.
To help you bridge the gap between your old records and the new system, we’ve introduced a new entity called ListIdMapping.
If you only have a Legacy V1 List ID, you can use this entity to find its modern counterpart:
Result: Returns the corresponding ilsListId (ILS Segment ID).
** Revised the timing for the fix deployment**
We are updating our HubSpot Connector to utilize the Contact List v3 API and this activity takes place from 11:00pm EST on April 28th till 3:00am EST on April 29th. This upgrade ensures better performance and long-term compatibility with HubSpot’s latest features.
To ensure a smooth transition, please review the following changes included in our latest hotfix.
HubSpot is phasing out the Contact Lists API (v1) endpoints on April 30th, 2026. All but the three Contact Lists API (v1) endpoints will be removed on the deadline and begin returning HTTP 404. The full notice regarding these changes can be found here.
Please be aware of a critical behavior change when adding members to a contact list:
If you attempt to add a list member using a Legacy V1 List ID, the system will not return an error. The request will appear to be successful. However, the contact will not actually be added to the list.
You must ensure you are using the ILS Segment ID for all member additions to ensure the record is processed correctly.
Questions? Please submit a ticket at support.tibco.com for assistance.