Recently, we encountered an issue with our HubSpot pipeline/tickets API results. One of the pipeline IDs was returned with a string format, differing from the rest of the IDs, which are numeric.
Example of the different ID:
“id”: “t_8c31e6e031e8a52a1bbdbead65e1b3aa”
Example of the usual numeric IDs:
“id”: “112643089”
Are there any recent changes I’m not aware of? I checked the changelog and didn’t find anything.
I’m only flagging this as an issue because our data ingestion tool reported this unexpected type change. It’s not a big deal, but I feel like I might have missed an update.
Context: API used in the cenario: https://api.hubapi.com/crm/v3/pipelines/tickets
Hi @lucas6,
Thank you for posting to the Community!
I understand that one of the pipeline IDs returned by the HubSpot pipeline/tickets API is now in string format instead of the usual numeric format, and you’re wondering if there have been any recent changes.
I’d like to tag in some of our Top Contributors to see if they are aware of any changes here -- Hi @mangelet@Gonzalo and @HubSpot_Corey Have any of you seen any of the changes that @lucas6 described?
Thank you!
Cassie, Community Manager
Hi @lucas6 , HubSpot has been rolling out more string-based IDs in places where objects or pipelines need globally unique identifiers, so seeing a t_… style ID mixed with numeric ones isn’t a bug.
The tickets pipelines API accepts both, and HubSpot’s own documentation treats pipeline IDs as strings even when they look numeric (Accounts Dashboard | HubSpot )
Older pipelines often keep their numeric IDs, while newly created or system-generated ones come through as the longer prefixed strings.
If your ingestion layer enforces numeric typing, the safest fix is to cast everything to string upstream and treat pipeline IDs as opaque identifiers rather than typed values. Are you syncing these pipelines into a warehouse or another CRM where the type mismatch is blocking updates? When integrations depend on consistent IDs across systems, Stacksync normalizes those identifiers and keeps the mapped pipelines aligned so your jobs don’t break on format shifts.