Expensify.org/hunger SNAP campaign status
We’re no longer accepting new participants as our focus is on reimbursing existing claims. While we’re unable to provide a specific timeline on when your report will be reimbursed, we’re doing our best to drive donations and keep reimbursements moving forward. If you know anyone who can donate to this campaign please encourage them to enable Personal or Corporate Karma on their Expensify account.

Syncing Users via API

CoryPittCoryPitt Expensify Customer Posts: 1
edited September 17 in Ideas

When we connect a Rippling company to Expensify, we need to know which employees are currently associated with Expensify account policies. This gives us a starting point to match Rippling accounts to users in Expensify. Currently, we have to ask customers to sign-in to their Expensify account, then download a CSV file of their current employees, and then upload it into Rippling. We then match the company's employees within Rippling with pre-existing Expensify users.

Usually, applications expose the capability for a GET /users endpoint, allowing identity managers to completely automate the employee lifecycle process. This removes touch points for mutual customers and makes for a much better user experience.

The lack of a GET endpoint for users, prevents our system from querying multiple policies for an employee. Ideally, this endpoint would return all employees and show which policies an employee is associated with.

As an additional benefit, this functionality can provide real-time account statuses within provisioning integrations. For instance, the user list often includes an associated userStatus field, such as 'isActive'. This allows our customers to see who has an account and the employees whose accounts have been removed. Without this functionality, a user might have their account removed from directly within Expensify and we will have no way of knowing without another CSV upload. Typically, we call the GET /users endpoint to the partner, and it solves the issue immediately.

Would you be able to expose a GET /users endpoint for us to support these functionalities?

1 votes

Understanding the Issue · Last Updated


Sign In or Register to comment.