When your mini app initializes inside World App, MiniKit stores device context, launch context, and basic user metadata on the client. If you are using React,Documentation Index
Fetch the complete documentation index at: https://tfh-ertugrulaypek-pop-3807-update-poh-credential-documentat.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
MiniKitProvider will perform the initialization for you.
Otherwise, manually initialize MiniKit at the start of your app:
MiniKit State
After install, these are the public MiniKit state accessors you can rely on:- Type
walletAddress,verificationStatus,preferredCurrency,pendingNotifications, andoptedIntoOptionalAnalyticsare all available at initialization.usernameandprofilePictureUrlare populated afterwalletAuth().MiniKit.locationis the mapped launch location. Use this instead of reading older launch-origin fields directly.
Permissions
MiniKitProvider installs MiniKit, but it does not automatically fetch permission state.
If you need the current permission settings, call MiniKit.getPermissions() explicitly:
MiniKit.user.permissionsis cached MiniKit state and should be treated as incomplete until you fetch permissions.getPermissions()can returnnotifications,contacts, andmicrophone.- The cached
MiniKit.user.permissionsshape only exposesnotificationsandcontacts.
Launch Location
MiniKit normalizes the raw World App launch origin into:- Type
- Example
Raw World App Object
If you need the untransformed World App payload, readwindow.WorldApp directly.
- Type
- Example
window.WorldApp only when you need the raw payload. In application code, prefer MiniKit.user, MiniKit.deviceProperties, and MiniKit.location.