Search conversations: Unsupported search modifier provided

Forum|Forum|8 months ago
December 5, 2025
6 replies
380 views

Hi,

We’ve started receiving 400 Bad Request errors when calling the conversations/search endpoint. A request such as:

now returns:

We aren’t using any other modifiers, and there have been no changes on our side. The issue began on 23 July 2025. From what I can see, using after: is still documented and there’s nothing in the changelog that suggests this behaviour should have changed.

Do you have any insight into why this might be happening or whether anything has recently changed with this endpoint?

Best answer by raymond_ching

Hi Alex, happy to help you here!

We do still support the ‘after:’ flag to search conversations, so likely something else is occurring here. Can you please submit a support ticket with us and provide an admin email so that we can take a look at your account to see why these API calls are failing? We can take a deeper look from there, thank you!

R

raymond_chingAnswer

Fronteer

Hi Alex, happy to help you here!

We do still support the ‘after:’ flag to search conversations, so likely something else is occurring here. Can you please submit a support ticket with us and provide an admin email so that we can take a look at your account to see why these API calls are failing? We can take a deeper look from there, thank you!

A

alexdialpadAuthor

Conversationalist

Hi Raymond,

I am unable to raise a support ticket as we do not have a Front account. Our customers connect their Front accounts to our product using an OAuth flow. We then use the stored access token to make requests for data on their behalf and this is what is failing. Is there some other way we can troubleshoot this?

patrick_v

Fronteer

Hi Alex,

No worries if you don’t have a Front account! You can reach out to support@front.com and provide your customers’ account details that we can look up on our end. If you can provide the admin email for a user associated with your customer’s account, it’ll help us verify the account in order to dig further into the logs to understand what may be causing issues with these failing API calls.

A

alexdialpadAuthor

Conversationalist

Hi,

It would appear that the endpoint no longer supports milliseconds as an integer but decimals do work: