We are evaluating a ServiceNow integration for a custom mobile application that will allow users to create requests, upload attachments, track ticket status, and receive notifications when records are updated.
I’m working with AppVerticals, a mobile app development company , to research the most secure and maintainable approach for this integration.
Our current idea is to place a secure backend layer between the mobile app and ServiceNow. This backend would manage authentication, permissions, data mapping, retries, and error logging instead of allowing the mobile client to access ServiceNow APIs directly.
I would appreciate guidance on a few points:
Should we use OAuth 2.0 with a dedicated ServiceNow integration account?
Is the Table API suitable, or would limited Scripted REST APIs be more secure?
What is the recommended method for uploading mobile attachments?
How can duplicate requests be prevented after network retries?
What is the best way to notify the app when a ticket status changes?
Are there API limits or mobile security requirements we should consider?
Our priority is to protect ServiceNow data while creating a fast and reliable mobile experience. Any recommended architectural patterns, documentation, or real implementation lessons would be appreciated.
