Skip to main content
New Participant
Oct 3, 2026 7:46 PM UTC
Question

OAuth 2.0

I have several clients needing to connect to third-party applications that exclusively use OAuth 2.0. Similar to Dayforce’s own token authentication, this requires an initial call to an authentication endpoint to exchange credentials for a token, which is then passed in the headers of subsequent API requests to push or pull data. While Integration Studio natively supports standard Client Credentials and Password grants, these specific vendors require token exchanges and grant types that fall outside those current native options.

Is there a roadmap for expanding Integration Studio's token-based authentication to handle more complex or custom OAuth 2.0 flows?

3 replies

Frank.R
Community Manager
Oct 13, 2026 5:34 PM UTC

​Hey @LexiWoodward, would you happen to know this info?

New Participant
Oct 14, 2026 1:13 PM UTC

Hi Asterion,

Expanding our options for Integration Studio token retrieval is not currently on the roadmap except for supporting signed jwt with a focus on Netsuite.

Can you please let me know some examples of these custom requirements? And a rough idea of the proportions of your API projects that need it?

Unfortunately, we cannot consider this for next year, but I will use your response to assess feasibility/priority for after.

 

Thank you,

Thibaut

Participating Frequently
Nov 13, 2026 2:04 AM UTC

Hi Asterion,

Expanding our options for Integration Studio token retrieval is not currently on the roadmap except for supporting signed jwt with a focus on Netsuite.

Can you please let me know some examples of these custom requirements? And a rough idea of the proportions of your API projects that need it?

Unfortunately, we cannot consider this for next year, but I will use your response to assess feasibility/priority for after.

 

Thank you,

Thibaut

this is an example https://synchrapi.atlassian.net/wiki/spaces/SI/pages/724430/REST+API#Authentication