Last active
August 29, 2015 14:04
-
-
Save bago2k4/f2a8975f21d2de03fd06 to your computer and use it in GitHub Desktop.
jids.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"api_key": "1cb2f6ddee83ca88f1ce1ea39c3ea9413cefb369", | |
"email": "agent.iacopo1@talkto.com", | |
"first_name": "", | |
"is_staff": false, | |
"is_superuser": false, | |
"jids": [ | |
{ | |
"address": null, | |
"city": null, | |
"contact_email": null, | |
"contact_name": null, | |
"contact_phone": null, | |
"entity_type": "workflow", | |
"is_ambassador": false, | |
"is_anonymous": false, | |
"is_claimed": false, | |
"is_talkto": false, | |
"jid": "2eae7aeb", | |
"latitude": null, | |
"longitude": null, | |
"name": "agent.iacopo1attalkto.com", | |
"placepage_url": null, | |
"profile_image_url": null, | |
"resource_uri": "/xapi/v1/entity/2eae7aeb/", | |
"state_or_province": null, | |
"ttags": [], | |
"zip": null | |
}, | |
{ | |
"address": null, | |
"city": null, | |
"contact_email": null, | |
"contact_name": null, | |
"contact_phone": null, | |
"entity_type": "person", | |
"is_ambassador": false, | |
"is_anonymous": false, | |
"is_claimed": false, | |
"is_talkto": false, | |
"jid": "2eae7aebperson", | |
"latitude": null, | |
"longitude": null, | |
"name": "agent.iacopo1attalkto.com", | |
"placepage_url": null, | |
"profile_image_url": null, | |
"resource_uri": "/xapi/v1/entity/2eae7aebperson/", | |
"state_or_province": null, | |
"ttags": [], | |
"zip": null | |
} | |
], | |
"last_name": "" | |
} |
You are right, we don't need those two entities. Just a "User" for the agent. The login API should return is_superuser and is_staff.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
an agent has 2 entities, one is the entity he uses to reply in place of the business and one is a normal person entity that i think was required by tt.
Now it doesn't need none of these so i think we can safely remove this call, the api_key is returned in the login API.
WYT?