Skip to main content
Solved

Search conversations: Unsupported search modifier provided

  • December 5, 2025
  • 6 replies
  • 113 views
A

Hi,

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

https://api2.frontapp.com/conversations/search/after:1762920938801

now returns:

400 Bad Request {"_error":{"status":400,"title":"Bad request","message":"Unsupported search modifier provided."}}

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!

    6 replies

    R
    Forum|alt.badge.img+5
    • raymond_ching
    • Fronteer
    • Answer
    • December 7, 2025

    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
    • alexdialpad
    • Author
    • Conversationalist
    • December 8, 2025

    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
    Forum|alt.badge.img+2
    • patrick_v
    • Fronteer
    • December 8, 2025

    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
    • alexdialpad
    • Author
    • Conversationalist
    • December 10, 2025

    Hi,

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

    • after:1762920938801 fails
    • after:1762920938 succeeds
    • after:1762920938.801 succeeds
    bestrada
    Forum|alt.badge.img
    • bestrada
    • Fronteer
    • December 10, 2025

    Hey Alex,

    Beyker here from the Customer Support team. Can you please reach out to  support@front.com so we can investigate this better? 

     

    Looking forward to hearing back from you!

    Beyker Estrada
    A
    • alexdialpad
    • Author
    • Conversationalist
    • December 11, 2025

    Done!

    Terms & ConditionsCookie settingsAccessibility statement