Choosing an Integration Method
DeviceAssure supports two integration methods: Client to Server (C2S) and Server to Server (S2S). Both methods use the same DeviceAssure client library to collect device data - the difference is in how that data reaches the DeviceAssure API for validation.
Comparison
| Client to Server | Server to Server | |
|---|---|---|
| How it works | Library sends data directly to DeviceAssure API | Library collects data; your server sends it to DeviceAssure API |
| Licence key location | Client-side (in the library configuration) | Server-side only |
| Implementation effort | Lower - fewer moving parts | Higher - requires server-side API call |
| Response time | Optimal - direct to nearest endpoint | Additional hop via your server |
| Server-side control | Results via optional callback URL | Full control over request timing and handling |
| Best for | Most integrations, especially getting started quickly | When server-side control or licence key security is required |
When to Use Client to Server
Choose Client to Server if:
- You want the simplest integration with the fewest steps
- You don't need server-side control over validation requests
- You want minimal latency with no extra network hops
- You're building a straightforward web page or Android app
This is the recommended starting point for most integrations.
When to Use Server to Server
Choose Server to Server if:
- You need to keep your licence key on the server rather than exposing it client-side
- You want to integrate validation into existing server-side workflows
- You need full control over when and how validation requests are made
- Your architecture requires the client device to communicate only with your own servers
If You're Unsure
Start with Client to Server. It's simpler to implement and you can always switch to Server to Server later. The client-side library code is nearly identical for both methods - the main difference is a single configuration flag and adding a server-side API call for S2S.
Platform-Specific Guides
Web
- Client to Server - Direct validation from the browser
- Server to Server - Validation via your backend server
Android
- Client to Server - Direct validation from the app
- Server to Server - Validation via your backend server
Server-Side API
- Server to Server API - REST API reference for the server-side validation call
See Also
- How It Works - Architecture diagrams for both models
- Understanding Results - What the validation results mean