Is per-user access is not supported for REST API integration?

7 replies
80 views

All users reach Dayforce REST APIs through one shared service account, because Dayforce only supports client credentials.

Can I get written confirmation from Dayforce that per-user access is not supported?

M

mmadhoun

Participating Frequently

What is the reason behind setting up a shared service account for all your consumers? It is recommended that you setup a web service user account per consumer which would mean per-user access is supported.

The role that is assigned to that user account will dictate what web service features/role authorizations are permitted for that role. This guide should give more context on best practices: https://help.dayforce.com/r/documents/Dayforce-Web-Services-Configuration-Guide/Standard-Configuration-Steps-Required. Hope this help.

M

md.shakiraliAuthor

New Participant

Does it mean that web service user account will be responsible for authentication of each consumer?

M

mmadhoun

Participating Frequently

This largely depends on how the downstream application is designed. From an integration and security perspective, each system consuming Dayforce APIs should use its own Dayforce web service account as best practice. Authentication should be managed by the consuming system, with token-based authentication being the recommended approach, and API calls should be made as required by that system’s workflow.

Sign up

Sign in to the Dayforce Developer Community