FAQ

Understand TOTPX before you integrate it.

A practical overview of products, devices, token verification, presence tokens and organizational planning inside TOTPX.

View pricing See API overview
TOTPX structure
Product Token model or device family
Device SN-1001
Device SN-1002
Device SN-1003
Token Verification API Verify tokens from your application
Quick model

Product → Device → Verification

This is the core idea behind TOTPX. Products group token types. Devices represent individual tokens. API requests verify token values.

Ask a question

TOTPX is organized in a simple hierarchy: a product represents a token model or device family, devices are the individual physical or virtual tokens, and API requests verify tokens generated by those devices.

A product represents a token model, token type or device family. For example, one product can be a specific hardware token model, a software authenticator type or a presence token setup.

A device is one individual token under a product. Each device usually has its own serial number, identifier or secret and can be verified through the TOTPX API.

Products describe the type or model. Devices are the actual individual tokens. Example: Product = FEITIAN OTP Generator Model X. Devices = SN-1001, SN-1002 and SN-1003.

Most organizations only need a few products. You usually create one product per token model, device family, software token setup or verification use case.

You need one device entry for each individual token that should be managed or verified. If you have 80 physical tokens, you normally need 80 devices.

A token verification API request is one server-side check where your application sends token data to TOTPX and receives a verification result.

Presence Tokens are used to verify that a person or device is present in a specific context, such as a physical location, workplace, event or controlled environment.

Yes. TOTPX is designed for BYOT workflows, meaning Bring Your Own Token. Supported integration depends on the token type, seed handling and verification method.

Shared Access allows multiple users, teams or applications to work with selected resources without giving everyone unrestricted administrative access.

No. TOTPX focuses on token verification, token management and simple integration APIs. It is designed to integrate with your existing application or authentication workflow.

Basic knowledge helps, but you do not need to build the whole verification logic yourself. TOTPX provides an API layer that simplifies token verification and management.
Ready to test

Plan your token setup with confidence.

Start with your products, register your devices and connect your application through the verification API.

Open playground Request access