Legacy Dev Forum Posts

 View Only

Sign Up

  • 1.  Field to store ClientID

    Posted 06-05-2025 18:11

    RogierBosch | 2016-12-14 10:44:02 UTC | #1

    Hi all,

    Is there a field that we can (ab)use to store a (client)id with API and that is available in each kind of interaction (like e-mail, webchat, callback etc) and that we can extract with API for analytics etc?

    anon28066628 | 2016-12-14 13:54:53 UTC | #2

    Hi Rogier,

    Properties indexed with this endpoint are available in analytics: https://developer.mypurecloud.com/api/rest/v2/conversations/index.html#postAnalyticsConversationsConversationIdDetailsProperties

    It requires the conversation id, the session (media) id, and a target date timestamp. The property is attached to a segment in the session / media object, if target date timestamp is between the start and end times of that segment. If the timestamp is not between the start and end times of any of the segments in the session, then no tag is added.

    RogierBosch | 2016-12-15 09:46:09 UTC | #3

    Thanks,

    But this is not something an user can add during an interaction (like 'Notes') in a Webchat / Email / Manual placed outbound call?

    anon28066628 | 2016-12-15 14:17:56 UTC | #4

    Hi Rogier, no, a user cannot add to this property using the normal purecloud ui. Is that the desired behavior? I understood it was based on this statement: "we can (ab)use to store a (client)id with API".

    If you need a user-editable "abusable" field, Wrap Up Notes are also available in analytics. That field can be written by agents in the standard purecloud ui, and can also be written to by API (and read later from analytics).

    POST /api/v2/analytics/conversations/details/query

    RogierBosch | 2016-12-15 14:22:16 UTC | #5

    I am looking for a combination of user and api "abusable" field.

    I tried "Notes" but if a call is setup with the use of API I can't set the "Notes" with the patch function. Error "Wrap-up code can't be empty"..

    anon28066628 | 2016-12-15 14:35:43 UTC | #6

    Ah, yes in that case you should check if there is a wrap-up code. If not, assign that first via api (you can make a 'junk' one to use as a placeholder, only for this purpose). For example call the wrap-up code "ALLOWANOTE" or similar.

    RogierBosch | 2016-12-15 15:19:39 UTC | #7

    :+1:

    Thanks! I've tested it and I can work with this 'work-around'..

    system | 2017-08-28 19:29:24 UTC | #8

    This post was migrated from the old Developer Forum.

    ref: 718



Related Content