# Integrating .NET REST API with Ignition Perspective for real-time membership validation **URL:** \ **Category:** General Discussion\ **Tags:** perspective\ **Created:** [March 2, 2026, 3:16pm UTC](https://forum.inductiveautomation.com/t/integrating-net-rest-api-with-ignition-perspective-for-real-time-membership-validation/114264 "2026-03-02T15:16:11Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![nesitad31](https://avatars.discourse-cdn.com/v4/letter/n/c57346/32.png) [@nesitad31](https://forum.inductiveautomation.com/u/nesitad31)\ **Post date:** [March 2, 2026, 3:16pm UTC](https://forum.inductiveautomation.com/t/integrating-net-rest-api-with-ignition-perspective-for-real-time-membership-validation/114264/1 "2026-03-02T15:16:11Z")
Hi everyone, I’m currently developing a system using .NET ([ASP.NET](http://ASP.NET) Core) with an Oracle backend. The system exposes a REST API for validation and status checks. Specifically, this is for a [digital membership card](https://membershipanywhere.com/digital-membership/) solution that generates QR-based membership IDs. I’m exploring whether Ignition (Perspective) can be used as a front-end dashboard or kiosk interface to validate memberships in real time. A few technical questions: 1. Should Ignition connect directly to Oracle via JDBC, or is it better to call the .NET REST API? 2. Does Perspective support QR code scanning natively, or would a third-party module be required? 3. What’s the recommended architecture for secure API communication between Ignition Gateway and an external .NET service? Any insights or experiences with integrating external web services with Ignition would be highly appreciated. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 2, 2026, 7:24pm UTC](https://forum.inductiveautomation.com/t/integrating-net-rest-api-with-ignition-perspective-for-real-time-membership-validation/114264/2 "2026-03-02T19:24:19Z")
> [@nesitad31](#): > > Should Ignition connect directly to Oracle via JDBC, or is it better to call the .NET REST API? The answer here really is "it depends". The REST API might give you more control, programmatically, over what's being sent/received and have some other minor benefits, but it's also introducing another layer of latency. I would say the best advice is to target the point of abstraction that is less likely to change. In a year, or five, is the DB still going to be there with the same schema? Is the REST API (with the same schema)? Either one _could_ in theory be adjusted, but once you tie Ignition to one or the other you're making it more complicated, institutionally, to change that one. > [@nesitad31](#): > > Does Perspective support QR code scanning natively, or would a third-party module be required? If your end users are in the mobile apps, you can invoke the scan barcode action: > **[Scan Barcode Action​ - Component Events and Actions | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.3/ignition-modules/perspective/working-with-perspective-components/component-events-and-actions#scan-barcode-action)** > > In Perspective, events and actions are some of the fundamental building blocks of project functionality. Actions give you the ability to respond to specific user inputs (such as mouse, keyboard, and touch inputs), as well as broad session events... If they're in a browser-based session (on any device) or Perspective Workstation, then you can use a third party "keyboard wedge" style scanner via the [Barcode Scanner](https://www.docs.inductiveautomation.com/docs/8.3/appendix/components/perspective-components/perspective-input-palette/perspective-barcode-scanner-input) component. These are two _separate_ ideas - not complementary, and currently the only ways to do barcode scanning in Perspective. > [@nesitad31](#): > > What’s the recommended architecture for secure API communication between Ignition Gateway and an external .NET service? Use HTTPS on the external service, and if it's self-signed, add that cert to the gateway: > **[Adding Security Certificates into KeyStores​ - Security Certificates | Ignition...](https://www.docs.inductiveautomation.com/docs/8.3/platform/security/security-certificates#adding-security-certificates-into-keystores)** > > A security certificate, also known as a digital certificate, is used to provide trust between connections. Trusted certificates establish the identity, authenticity and reliability of incoming and outgoing traffic. In my opinion there's not really any need for anything more than that.