Notifications API

[asikarwar]

Hello,

Thank you for all your help!
I was able to make the right decision of using Notification APIs.

Shema for Notification and Analytics APIs are different.

I have started to understand this better... but I have couple of queries for v2.analytics.queues.{id}.observations

I wanted to process event only with direction: inbound

With Analytics API (where we used to get everything in the same json body) using conditional statements we could exclude outbound call before processing json.
Python Example: if(str(rows['direction'])!="outbound"):

My question is, how can I include only inbound calls with Events APIs?
Do I need to use two Notification APIs together and process the data?
v2.analytics.queues.{id}.observations + v2.routing.queues.{id}.conversations.calls

---

2. Sorry this may come across as a silly question!

I do not see requestedRoutingSkillIds in events from v2.analytics.queues.{id}.observations (important to discern the teams) we need this to determine which team we need to send alerts to.

requestedRoutingSkillIds does not exist because there wasn’t a "metric": "oInteracting" ?
or
Is this included in some other API?

Json sample:

   {
          "metric":"oMemberUsers",
          "stats":{
             "count":61.0
          }
       },
       {
          "metric":"oUserRoutingStatuses",
          "qualifier":"INTERACTING",
          "stats":{
             "count":1.0
          }
       },
       {
          "metric":"oOnQueueUsers",
          "qualifier":"INTERACTING",
          "stats":{
             "count":1.0
          }
       }, .................... and many more but I did not "metric": "oInteracting",

Thanks
Ashish

[asikarwar]

Is conversationRoutingData from v2.routing.queues.{id}.conversations.calls same as requestedRoutingSkillIds ?

  "conversationRoutingData": {
    "queue": "object",
    "language": "object",
    "priority": 0,
    "skills": [
      {}
    ],

[Jerome.Saint-Marc]

Hello,

direction is propagated in v2.routing.queues.{id}.conversations and v2.routing.queues.{id}.conversations.calls

"" Is conversationRoutingData from v2.routing.queues.{id}.conversations.calls same as requestedRoutingSkillIds ?
Yes, I think so.
conversationRoutingData is propagated in v2.routing.queues.{id}.conversations and v2.routing.queues.{id}.conversations.calls

Regards,

[asikarwar]

Thank you @Jerome.Saint-Marc!