> ## Documentation Index > Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt > Use this file to discover all available pages before exploring further. # Quick Start > Get up and running with OneSDK in minutes. This guide walks you through implementing two common onboarding flows: eKYC and IDV verification. ## Prerequisites
* Customer ID * Child ID (if applicable) * API Key * Service Name — Required in the request body for V2 API calls. * UAT: `https://backend.kycaml.uat.frankiefinancial.io/auth/v2/machine-session` * Prod: `https://backend.kycaml.frankiefinancial.io/auth/v2/machine-session`
**Important**: When using V2 endpoints, you must include "serviceName": "KYC" in the request body. Omitting this field will result in a 400 Bad Request error. Need credentials? Contact FrankieOne support to set up your account. ## Implementation Guide ##### Security Best Practice Never expose API credentials in client-side code. Generate session tokens server-side and pass only the token to your frontend. Select the implementation that best fits your needs: Manual capture and verification flow. ```html ekycFlow.html theme={null} OneSDK eKYC Onboarding
``` OCR and Biometrics verification flow. ```html idvFlow.html theme={null} OneSDK IDV Onboarding
``` Replace the following placeholders with your credentials: ```javascript theme={null} const config = { CUSTOMER_ID: "your-customer-id", CUSTOMER_CHILD_ID: "your-child-id", // Remove if not applicable API_KEY: "your-api-key" }; ``` Add Google Maps support for address auto-completion: ```javascript theme={null} const oneSdk = await OneSDK({ session: sessionObjectFromBackend, mode: "development", recipe: { form: { provider: { name: "react", googleApiKey: "your-google-maps-api-key" } } } }); ``` Add a unique customer reference: ```javascript theme={null} permissions: { preset: "one-sdk", reference: "your-unique-reference" } ``` 1. Save your code as an HTML file 2. Open in a web browser 3. Test on both desktop and mobile devices ##### Development Tips * Use the browser console to monitor events (`oneSdk.on("*", console.log)`) * Test with different document types * Verify all flow stages work as expected Congratulations! You've successfully set up OneSDK. Need help? Contact our support team for assistance.