Set reporting access via API
complete
E
Eko
Hello James C thanks for sharing. We'll look into this. For any future errors/bugs, it's usually best to raise it through support@evaluagent.com
Is the data you shared from your production account? If so, can you please edit/delete it as this board is a public one so people outside Evaluagent may be able to see the user data you have shared
J
James C
Hey Eko - thanks for the update. I'm getting a 500 error when trying to do a PATCH to update a user and change their
attributes.reporting_access_id
value from one ID to another.Specifically, we're seeing this response:
{
"errors": [
{
"status": "500",
"code": "0",
"title": "Internal Server Error.",
"detail": ""
}
]
}
when we send this payload as a PATCH request with Content-Type
"application/json"
:{
"data": {
"type": "users",
"id": "b3530f47-557b-4aba-aa1e-b3557df07ee1",
"attributes": {
"forename": "Chevonne",
"surname": "Switzer",
"fullname": "Chevonne Switzer",
"email": "CSwitzer@gohealth.com",
"username": "CSwitzer@gohealth.com",
"active": true,
"allow_login": true,
"reporting_access_id": "8a9fdcd0-6b95-4b97-aada-3d75e83eb507",
"third_party_id": 109985
},
"relationships": {
"agent-team": {
"data": null
},
"roles": {
"data": [
{
"type": "roles",
"id": "ce03894a-53f8-4e1e-a277-7dc9cd79f0fc"
},
{
"type": "roles",
"id": "46cbf745-ba7e-4f21-884d-8bdbc428bc80"
},
{
"type": "roles",
"id": "bd84c1a1-35d7-4727-b7e6-4915050fa4ed"
},
{
"type": "roles",
"id": "ff21bc96-a4b0-402b-bcf2-1eaae7e8c932"
},
{
"type": "roles",
"id": "ff21bc96-a4b0-402b-bcf2-1eaae7e8c932"
},
{
"type": "roles",
"id": "bd84c1a1-35d7-4727-b7e6-4915050fa4ed"
}
]
}
}
}
}
to this endpoint:
https://api.us-east.evaluagent.com/v1/org/users/b3530f47-557b-4aba-aa1e-b3557df07ee1
The new ID (
8a9f...
) is confirmed to be a valid group from the "fetch groups" response.Is there any chance you have more info about this error from the server side? Thanks!
E
Eko
complete
E
Eko
Hello James C Kevin T we have just launched the ability to set reporting and login access via API(beta). Please read our documentation for more information: https://docs.evaluagent.com/#operation/createUsers
E
Eko
in progress
E
Eko
in design
The architecture design for this is ongoing
J
James C
Eko: Excellent, thank you! Hopefully it's a quick fix. I can see the the payload sent when making the changes from the UI already includes this field, so I can't imagine that what's exposed in the provided API is too far away from supporting this.
We appreciate the updates!
E
Eko
Hello James C Kevin T We are currently reviewing this and I will update this ticket with more information at the end of the month (latest).
K
Kevin T
Eko: Thanks Eko
J
James C
Hey Jon (Product Manager @Evaluagent) - can we get an update on the status of this request? Until we are able to get and set the Reporting Access field via the API (on user fetch/update/create), we are still manually making these updates to users. If we don't make the right updates at the right time (because it's manual, and we're human), people will be able to see data they shouldn't. Not only is this confusing for our users, but it could negatively affect our compliance.
K
Kevin T
Hi Jon - Just following up on this proposal to see where this stands for review and determination? Thanks, Kevin
K
Kevin T
This feature request we consider a blocker at GoHealth, simply because we cannot automate the role assignments outside of Agent without being able to set the Reporting Access within your API. We have over 250 users (150 of those required to be built in Structure), so without this field in the API, this part remains 100% manual to add or edit any user that does not have the role of an Agent. It seems logical that if the API is able to set the Agent to Team Leader structure (Team Selection field), that one could also set the other existing roles for the proper Reporting Access level as well. Please consider adding this into the API soon, as we don't have true automation and hierarchy synching without this feature available to us within the API.
Load More
→