4 ms·

You are perfectly right, your description is perfectly on point, even though our description confused you at first. To be honest, I'm not too much a fan of Pay

You are perfectly right, your description is perfectly on point, even though our description confused you at first. To be honest, I'm not too much a fan of Payroll API too, but it seems it is the term that is now coined in the US for what we are doing (see that article from a16z: https://a16z.com/2020/10/20/payroll-apis/ https://a16z.com/2020/10/20/payroll-apis/) If you happen to have an another idea about a very quick way to describe what we are doing (less than 10 words), that would be great !

abraae 5y ago
That is an interesting article indeed. I see that after the headline, they immediately revert to talking about "payroll-connected APIs". They use this phrase 3 or 4 times, then they switch back to "payroll APIs" towards the end. All in all I don't know that "payroll-connected API" is any better for you - quite a mouthful and sounds way more techy. Personally I would like "Payroll verification API" but maybe that's just because we're having this discussion and that fancy will disappear like dust in the wind by the end of the day. It might also preclude you from getting into some of the juicier areas that a16z are talking about (i.e. things that are > just verifiying data), but of course you can always change your tagline :) FYI this area is of interest as we briefly explored automating some nasty govt systems using selenium or similar (aka RPA). We would run the robot in a VM that was torn down at the end of every session for security. We presented the UI to the user via guacamole - then once they had entered their credentials, the robot took over. Interesting but not the path we took in the end.
- pierre62360 5y ago
  You're right, "connected" can add more clarity. For the automation of some govt systems, you didn't try a "proper" reverse engineering where don't use selenium, but rather uncover the private APIs of the govt ?

abraae 5y ago

That is an interesting article indeed. I see that after the headline, they immediately revert to talking about "payroll-connected APIs". They use this phrase 3 or 4 times, then they switch back to "payroll APIs" towards the end. All in all I don't know that "payroll-connected API" is any better for you - quite a mouthful and sounds way more techy. Personally I would like "Payroll verification API" but maybe that's just because we're having this discussion and that fancy will disappear like dust in the wind by the end of the day. It might also preclude you from getting into some of the juicier areas that a16z are talking about (i.e. things that are > just verifiying data), but of course you can always change your tagline :) FYI this area is of interest as we briefly explored automating some nasty govt systems using selenium or similar (aka RPA). We would run the robot in a VM that was torn down at the end of every session for security. We presented the UI to the user via guacamole - then once they had entered their credentials, the robot took over. Interesting but not the path we took in the end.

pierre62360 5y ago
You're right, "connected" can add more clarity. For the automation of some govt systems, you didn't try a "proper" reverse engineering where don't use selenium, but rather uncover the private APIs of the govt ?