Is REST API the best approach for Integration Workday - Tempo

[Michael Gillespie]

Do any of you suggest anything different for the solution when it comes to creating an integration with a daily run of Workday HR columns into Tempo.  We are going down the path of REST API and I am interested in any more efficient methods of accomplishing this with maybe a connector.

[Prabhu Palanisamy _Onward_]

Workday has a robust API and suitable for common objects. If you have specific data set that you want and restrict with filters then one way to consider is building a custom report in Workday and exposing it as a webservice.
Here is an article we posted on how OnLink has a native connector to both Workday and Tempo.

Disclosure: I'm part of Onward who built OnLink.

[Henry Cavill]

In most cases, using a REST API is a solid and flexible approach for integrating Workday with Tempo, especially if you need real-time or near real-time data exchange.

REST APIs are generally easier to work with, scalable, and well-supported across different platforms. If both systems expose reliable endpoints, you can handle data synchronization, authentication, and updates more efficiently compared to older methods like file-based transfers.

That said, the best approach still depends on your specific use case. For example:

- If you need real-time updates → REST API is usually the best choice
- If the integration is batch-based → scheduled jobs or middleware might work better
- If there are limitations in API access → you may need to consider alternative connectors or integration tools

It’s also important to consider rate limits, authentication methods (OAuth, tokens), and error handling when designing the integration.

I’ve seen a structured integration overview that explains how to handle similar system connections step by step, which might give you a clearer direction depending on your setup.

Overall, REST API is a strong option, but it should align with your data flow and system capabilities.