Skip to main content
Nintex Community Menu Bar

Hello there, šŸ˜€


I am working on a project that requires integrating several external APIs into our Skuid applications. While I have some experience with basic API integrations; I want to ensure I am following best practices šŸ˜Š to maintain performance; security; and scalability.


What are the recommended approaches for handling API authentication within Skuid? Is there a preferred method for managing API keys or OAuth tokens securely? šŸ¤”


How should I structure my data models in Skuid to efficiently handle API responses, especially when dealing with large datasets? Are there any strategies to minimize the impact on page load times and ensure a smooth user experience?


What are the best practices for implementing robust error handling when making API calls? How can I ensure that my application gracefully handles API errors or timeouts and provides meaningful feedback to users?


When is it more appropriate to use Skuidā€™s native actions for API calls versus writing custom JavaScript? Are there any significant advantages or limitations to be aware of with either approach?


What are the key security considerations I should keep in mind when integrating external APIs? How can I protect sensitive data and ensure compliance with relevant security standards?


For APIs that provide real-time data, what are the best practices for integrating this type of data into Skuid pages?


Also, I have gone through this post: https://community.skuid.com/t/skuid-based-public-salesforce-admin-sites-and-security-concerns/8748 which definitely helped me out a lot.


I would love šŸ˜ to hear from anyone who has experience or insights on these topics. Additionally; if there are any resources; documentation; or examples you could point me to; that would be incredibly helpful.


Thank you in advance for your help and assistance. šŸ˜‡

Hi Samzyan, thanks for the quesitons.


Which API (or APIs) do you want to integrate with Skuid? The data source docs are a great place to start.


Hereā€™s answers to a few of your questions:


  1. Authentication and Skuid should get you started on the authentication piece. Tokens are stored securely and you can access them via authentication merge variables in your requests.

  2. Data model structuring depends on the data source youā€™re connecting with. Are you using REST, SQL, or something else?

  3. To improve page load time, you can load some models asynchronously. Uncheck ā€œload model on page loadā€ and use an action sequence that runs on page load to query the models that arenā€™t immediately necessary. See the Skuid Skool Course Tips to Optimize Performance with Models for more details.

  4. I would always recommend using Skuidā€™s native actions first over Javascript. The native actions should save you time and be future proof (as opposed to Javascript which you have to maintain with future changes). Use Javascript when the Skuid native method doesnā€™t exist or to supplement the native method when it doesnā€™t get you all the way there.

You had a lot of good questions I didnā€™t have time to get to today, but review the docs and the links above, and feel free to ask more questions (and more specific questions) as you get into connecting to a specific API.


Also, note that the Skuid Community is going read-only tomorrow as we migrate to community.nintex.com, so we can continue this conversation there.