Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Clarification on unexpected API Response

  • 1.  Clarification on unexpected API Response

    Posted 06-05-2025 18:30

    Davis_Walker | 2024-04-18 17:04:39 UTC | #1

    Hello,

    My team is currently undergoing the Direct Routing Beta, which requires a lot of interaction with the Users/Search API, and recently we noticed something we hadn't seen before while doing some testing and are unable to find any documentation on this behavior so hoping we can get some confirmation on a couple assumptions we're currently making.

    Unexpected Behavior: Users Search Returned an address with ( ) around it. Assumption 1: This was returned this way because it was a duplicate value. Assumption 2: The object that first had the address successfully added to it will return without ( ), while the second user who added the duplicate value to their profile would have the ( )'s.

    If both of these are true this will help us with some ongoing issues we're having with duplicates and give us a programmatic way to monitor for these issues and catch them faster while we come up with a long term fixes to user behavior.

    Here's an example of what the response looked like:

    "addresses": [
    {
      "display": "(+1 123-456-7890)",
      "mediaType": "PHONE",
      "type": "WORK",
      "countryCode": "US"
    },

    It also doesn't have an "address" which we're applying the same assumptions above to until we're able to confirm/test this out in more depth.

    Thanks for any clarifications/confirmations! -Davis

    Davis_Walker | 2024-04-30 17:57:51 UTC | #2

    Any help appreciated, or if there's a different way I should approach this question please point me in the right direction.

    system | 2024-05-30 17:58:10 UTC | #3

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 25804



Related Content