mikcanf | Posts: 71

/api/reports/delegation

0 votes

Returns set of delegationEvents with EventID(?) arrays that contain 4 items below:

eventDate, eventType, eventDescription and eventUser

EventID example-> 699AK8PzZMg0

a) can you confirm this is not a SenderID ( can't seem to find a Sender using this for ID )

b) there can be "n" number of events under EventID(?), crossing multiple dates, so it is not clear what the grouping is for

 


Duo_Liang | Posts: 3776

Reply to: /api/reports/delegation

0 votes

Hi Mike,

 

Please be aware that the keys of the nodes under the "delegationEvents" do refer to the sender IDs

{
  "from": "2016-01-01T00:00:00Z",
  "to": "2017-01-10T00:00:00Z",
  "delegationEvents": {
    "ZQI8k6faVoM8": [
      {
        "eventDate": "2017-01-09T18:35:04Z",
        "eventType": "Updated Delegates",
        "eventDescription": "Set delegates to: John Smith ([email protected]) to delegate on behalf of: Haris Haidary ([email protected])",
        "eventUser": "Haris Haidary ([email protected], from 00.00.000.000) "
      },
      {
        "eventDate": "2017-01-09T19:09:46Z",
        "eventType": "Removed all Delegates",
        "eventDescription": "Removed all delegates for: Haris Haidary ([email protected])",
        "eventUser": "Haris Haidary ([email protected], from 00.00.000.000) "
      }
    ]
  }
}

If you download the report as CSV format, this column is referenced as "Delegator ID" which makes it clearer to understand

8-19-1

From above screenshot:
The longer (in UUID format) delegator ID refers to group ID - members within a group delegate access each other

The shorter delegator ID refers to sender ID - whom delegates access to his/her dashboard to other sender(s)

 

eventDescription: describes what's been changed in this event

eventUser: who operates this event, could be account owner, or any sender with "Manager" role, or the delegator him/herself.

 

Duo

 

 


mikcanf | Posts: 71

Reply to: /api/reports/delegation

0 votes

 

{{TheHost}}/api/account/senders/{senderId}/delegates

senderId=Yup8muGfYRwY<-works with ->{{TheHost}}/api/account/senders/Yup8muGfYRwY

senderId=wVjrTjuxpOQT<-fails->{{TheHost}}/api/account/senders/wVjrTjuxpOQT

The first senderId works but second does not.

Are senderId's immutable? i.e. once created they don't change?


Duo_Liang | Posts: 3776

Reply to: /api/reports/delegation

0 votes

Hi Mike,

 

Thanks for the information, just checked with support team and seems the sender "wVjrTjuxpOQT" doesn't exist any more. Can you find the sender email from the event descriptions, and search under your account to see if the email is still a sender or has be deleted?

A typical event description looks like below, "[email protected]" is the sender email:

"eventDescription": "Set delegates to: sam ([email protected]), \njohn smith ([email protected]) to delegate on behalf of: John Smith([email protected])"

For your question is the sender ID immutable, it should be the case, but sender could be deleted if the person hasn't sent out a package. (On the contrary, if the sender has an ongoing transaction, you can at most lock the sender instead of deleting)

 

Duo


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off