iVALT API
iVALT API as documented publicly: 46 operations. Contract generated from the documentation by API Evangelist (2026-10-28); not the provider's own document.
Operations 46
POST
/admin/public/api/biometric-geo-fence-auth-results
POST /admin/public/api/biometric-geo-fence-auth-results
#
POST
/api/v1/validate/user
Validates user identity using face authentication and auth tokens for API version 1.
#
POST
/backup/validate/user
Check if a user with the given mobile number exists in the backup system.
#
POST
/backup/wp/websites
Returns a list of websites associated with the backup user supplied by mobile number.
#
POST
/check-imei
Validate and check the status of a device IMEI (International Mobile Equipment Identity). Used for device authentication and security.
#
POST
/contact/support
Send a support message to IVALT support team. Includes user contact information for follow-up.
#
POST
/dynamic_auth/login
Authenticate a device within the dynamic auth workflow by associating its machine and stock details.
#
POST
/dynamic_auth/verify
Verify whether a device is authentic/known to the dynamic auth system using its machine identifier.
#
POST
/enrolstatus
Check the enrollment status of a mobile user. Returns current enrollment state and any pending requirements.
#
GET
/get/stock-price/{symbol}
Fetch the latest price and associated exchange details for a given stock symbol.
#
POST
/is_enrolled
Verify if a user is enrolled in the system. Returns boolean result indicating enrollment status.
#
POST
/resend-email-verification
Resend email verification link to user's email address. Used when initial verification email was not received or expired.
#
GET
/save/faceauth/success/{authToken}
Record a successful face authentication event. Typically called by authentication systems after successful biometric verification.
#
POST
/send-auth-request-by-email
Sends an authentication notification to a recipient via email for login verification or identity confirmation.
#
POST
/send/app-auth/notification
Sends an authentication request from one mobile user to another — typically used in peer-to-peer or user-to-admin workflows.
#
POST
/send/global/notification
Sends a notification to a recipient identified by their mobile number.
#
POST
/user/assign-org
Assign a mobile user to a specific organization. Links user account with organizational context and permissions.
#
POST
/user/check-org-assignment
Verify if a user is assigned to any organization and retrieve assignment details.
#
POST
/validate/user/timeslots/geofencing
Validates the time slots and geofence location data of a user.
#
POST
/wp/confirm/register
Confirm and complete the user registration process after OTP verification. Updates user record with final details and activates the account.
#
POST
/wp/is-registered
Operation for /wp/is-registered via POST. Returns a SuccessResponse on success and an ErrorResponse on failure.
#
POST
/wp/mobile/refresh/token
Refresh the authentication token for a mobile user. Used to maintain session validity and security.
#
POST
/wp/register
Operation for /wp/register via POST. Returns a SuccessResponse on success and an ErrorResponse on failure.
#
POST
/wp/register-confirmation
Operation for /wp/register-confirmation via POST. Returns a SuccessResponse on success and an ErrorResponse on failure.
#
POST
/wp/register/confirmation
Operation for /wp/register/confirmation via POST. Returns a SuccessResponse on success and an ErrorResponse on failure.
#
POST
/wp/register/mobile/user
Register a new mobile user with comprehensive device and profile information. Typically used during initial app onboarding or user registration workflow.
#
POST
/wp/send-notification
Operation for /wp/send-notification via POST. Returns a SuccessResponse on success and an ErrorResponse on failure.
#
POST
/wp/send/sms
Send an OTP (One-Time Password) via SMS to the specified mobile number. Used for mobile verification during registration or authentication flows.
#
POST
/wp/watch-for-login
Operation for /wp/watch-for-login via POST. Returns a SuccessResponse on success and an ErrorResponse on failure.
#
Specifications
Schemas & Data
JSONSchema
https://artifacts.apis.io/ivalt/json-schema/ivalt-post-biometric-geo-fence-auth-results-request-schema.json
JSONSchema
https://artifacts.apis.io/ivalt/json-schema/ivalt-post-admin-public-api-biometric-geo-fence-auth-results-request-schema.json
JSONSchema
https://artifacts.apis.io/ivalt/json-schema/ivalt-post-admin-public-api-biometric-geo-fence-auth-results-response-schema.json
JSONSchema
https://artifacts.apis.io/ivalt/json-schema/ivalt-post-admin-public-api-verify-user-response-schema.json
JSONSchema
https://artifacts.apis.io/ivalt/json-schema/ivalt-post-verify-user-request-schema.json
JSONSchema
https://artifacts.apis.io/ivalt/json-schema/ivalt-post-admin-public-api-verify-user-request-schema.json