Frequently Asked Questions
Answers for product and developer teams building on Intelomatic. Looking for the business and operations view instead? See the FAQ for Business & Operations Teams on the homepage.
Products & modular adoption
What products are available?
Intelomatic provides Map SDK, Tracking SDK, Location and Address APIs, Route and Journey APIs, and Geo-fence and Boundary APIs.
These products can be used individually or combined to build a complete location-enabled field workflow.
Can we use Intelomatic APIs without using the full Field Force Mobility Platform?
Yes. Intelomatic supports modular adoption. You can use only the Map SDK, Tracking SDK, geocoding API, reverse-geocoding API, route-distance API, route-optimisation API, geofencing API or other location intelligence services based on your use case. See the API Reference for what's available today.
Can the SDK work inside our existing mobile or web application?
Yes. Intelomatic SDKs and APIs are designed to be embedded into existing enterprise mobile and web applications.
Your application retains its existing user experience, business workflow and backend integration, while Intelomatic provides the selected location capability. See SDKs & Platform Guides.
Backend & integration
Can we use our own backend and database?
Yes. Your existing backend can remain the system of record.
Intelomatic can send relevant location events, journey data, visit-validation results, route information and geofence outcomes to your backend through agreed APIs or data-integration methods.
Can Intelomatic integrate with CRM, HRMS, LOS, LMS and enterprise workflow systems?
Yes. Intelomatic can integrate with enterprise applications such as CRM, HRMS, LOS, LMS, collections systems, service-management platforms and custom workflow engines.
The integration can connect employee data, customer/case context, journeys, visits, geofence events, route information and operational reports.
Security
What encryption mechanism is used for data in transit?
Intelomatic uses TLS 1.2 for secure communication between applications, SDKs, APIs and backend services.
TLS 1.2 helps protect data while it is transmitted over public or private networks. The overall integration security design should follow the client's approved architecture, network controls and information-security requirements.
How should API keys and integration credentials be protected?
API keys and credentials should be stored securely and must not be hard-coded in public mobile or web client code.
For enterprise integrations, Sovereign recommends server-side credential handling, environment-specific keys, access controls, credential-rotation practices and usage monitoring.
SDK capabilities
Can the Tracking SDK work when the user has poor network connectivity?
The Tracking SDK can support offline location capture and synchronisation when network connectivity returns.
The exact behaviour depends on the mobile operating system, application permissions, device settings and agreed tracking configuration.
Can we create our own geofences and service boundaries?
Yes. You can create and manage circular or polygonal geofences, customer-site zones, branch boundaries, territories and other operational areas based on the selected APIs and use case. See Geo-fence and Boundary Intelligence.
Geofence and boundary events can be connected to your workflow engine, employee journey, visit-validation or exception-management process.
Can we use location APIs for address validation and customer onboarding?
Yes. Location and Address Intelligence APIs can support geocoding, reverse geocoding, address suggestions, location search, nearby-place discovery, address context and batch geocoding.
These APIs can be used in customer onboarding, CRM, collections, service and verification workflows.
Can we use Intelomatic for route planning and planned-versus-actual journey analysis?
Yes. Route and Journey Intelligence APIs can support distance calculation, travel-time calculation, multi-stop route planning, route optimisation, nearby customer prioritisation and planned-versus-actual journey analysis.
Do you provide map data and location data services?
Yes. Along with maps and APIs, Intelomatic can provide location data services such as administrative boundaries, district, taluka and village context, points of interest, address intelligence, nearby-place search and other India-focused location datasets.
Scale & access
Can the platform support high-volume enterprise usage?
Yes. The architecture and capacity plan are designed based on expected active users, API volume, concurrent requests, peak usage, data retention and required response times.
Share your expected scale during solution design so that infrastructure, support and commercial requirements can be planned correctly.
How do we get API keys or access credentials?
Use the Request Access or Talk to a Solutions Architect option. Our team will understand your use case, share the appropriate onboarding path and provide required environment access.
Is there a sandbox or interactive demo environment?
Yes. The interactive playground lets users explore selected Intelomatic capabilities.
The initial launch priority is Field Force Mobility use cases. Additional SDK, map and API examples can be added progressively.
Are developer documentation and sample code available?
The developer portal provides API references, SDK setup guidance, quickstarts, request and response examples, integration patterns and selected interactive examples — see Getting Started and the API Reference.
Product and solutions teams can also support enterprise integration design, testing and production-readiness planning.
Can we test a Field Force Mobility use case before production integration?
Yes. The initial interactive experience focuses on Field Force Mobility use cases.
It can help product and engineering teams understand maps, journey events, visit validation, routes and relevant API outputs before moving into a controlled integration or pilot.
Do you provide technical support during integration?
Yes. Sovereign's product, engineering and solutions teams can support solution design, onboarding, integration review, testing and production-readiness planning based on the agreed engagement scope. See Support.
How are API limits and scale handled?
Capacity, rate limits and commercial usage models are planned based on expected users, API volume, peak traffic and the intended use case.
Share expected usage during onboarding so we can recommend the suitable solution architecture and commercial model.
