How to get Inactive Users via api call from outside sugar.

You might need a custom API if you want to access inactive users, since sugar filters out Inactive users in the API by default.

Use this documentation to know how to create Custom APIs - https://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_10.1/Integration/Web_Services/REST_API/Extending_Endpoints/

May I know why you need inactive user info? If the API doesn't return anything, you can assume they don't have access to Sugar.

I need to sync records to sugar from other system. and that system may have some records assigned to inactive user. That system provides user_name as assignment identity. So first i need to fetch that user from sugar via that username and then do assignment.
As username can be of inactive user so i am not able to get the id of that user via default get api call.
So thats why i was asking is there any default way to achieve that. Or i need to write custom api.

If other system provides the name of a person not listed in active users by name it means this user is not allowed to use Sugar anymore.
What is the purpose to get the Sugar internal id of such a person?
Do assignments to other eligible Sugar users, using the name as identifier (if you search id by name, that means it is identifier too)

That is client's requirement, that user is expected to be set to active in future.

Client has to buy licenses first and activate users.

Until that, there is Employees ledger that  represent not only eligible users (employee record is created automatically for new user) but other staff too, whether they are retired users, possible future users or staff that nothing to do with CRM either. Employees could be retrieved with API  , that may help to link external accounts to future users until they receive legal rights to use Sugar and sugar data could be assigned to them 

I hope this makes sense

All the best,

Dmytro

Thanks for the idea, this is also possible to keep the employee status active and User inactive and then get the id of that user via employees api.
This could be a workaround.
Thanks that's really helpful.

Thanks for the idea, this is also possible to keep the employee status active and User inactive and then get the id of that user via employees api.
This could be a workaround.
Thanks that's really helpful.