Create
API Reference
Register a device for an entity
Register a device for a person or company entity in gu1 β supports device fingerprinting, fraud prevention, and downstream rule-based risk checks.
POST
Create
Overview
Manually register a device for a specific entity. This endpoint allows you to add device information when itβs not automatically captured through events, useful for data migrations, testing, or manual registration workflows.Automatic Registration: In most cases, devices are automatically registered when you create user events with device information. Manual registration is typically only needed for:
- Migrating existing device data
- Testing and development
- Backfilling historical device records
Endpoint
Authentication
Requires a valid API key in the Authorization header:Path Parameters
UUID of the entity to associate this device with
Request Body
Unique identifier for this device. This should be a stable identifier that persists across sessions (e.g., device fingerprint, IMEI, advertising ID)
Entity type for audit trail. Options:
person, company. Default: "person"External ID of the entity (your systemβs identifier). Stored denormalized on the device for queries.
Entityβs tax ID (e.g., CUIT, CPF). Stored denormalized on the device for queries.
Device platform. Options:
android- Android deviceios- iOS deviceweb- Web browser
"android"Device manufacturer name (e.g., βsamsungβ, βAppleβ, βGoogleβ)
Device model identifier (e.g., βSM-A156Mβ, βiPhone 15 Proβ, βPixel 8β)
Device brand name (e.g., βsamsungβ, βAppleβ)
User-defined device name or hardware name
Operating system version (e.g., βAndroid 16β, βiOS 17.2β, βWindows 11β)
System name for iOS devices (e.g., βiOSβ)
System version for iOS devices (e.g., β17.2β)
Browser name for web platform (e.g., βChromeβ, βSafariβ, βFirefoxβ)
Browser version for web platform (e.g., β120.0.6099.129β)
Geographic latitude coordinate (-90 to 90)Example:
-34.6037Geographic longitude coordinate (-180 to 180)Example:
-58.3816City name (e.g., βBuenos Airesβ, βNew Yorkβ, βLondonβ)
State or province (e.g., βBuenos Airesβ, βCaliforniaβ, βOntarioβ)
Country name (e.g., βArgentinaβ, βUnited Statesβ, βCanadaβ)
ISO 3166-1 alpha-2 country code (e.g., βARβ, βUSβ, βCAβ)
IP address (IPv4 or IPv6) from which the device is accessingExample:
"10.40.64.231"Whether this device is detected as an emulator or simulator
Whether this device is rooted (Android) or jailbroken (iOS)
Response
Indicates if the request was successful
The created device object
gu1βs internal device UUID
Your provided device identifier
External device identifier (same as deviceId)
UUID of the associated entity
Entityβs external ID (denormalized)
Entityβs tax ID (denormalized)
Device platform (android, ios, web)
Device manufacturer
Device model
Device brand
User-defined device name or hardware name
Additional device metadata (JSON object). Platform-specific: Android (hardware, buildId, sdkVersion), iOS (systemName, identifierForVendor), Web (userAgent, etc.)
Operating system name
Operating system version
Browser name (web only)
Browser version (web only)
Geographic latitude
Geographic longitude
City name
State/province
Country name
ISO country code
IP address
Emulator detection flag
Root/jailbreak detection flag
Whether device is blocked
Whether device is marked as trusted
First time device was seen (ISO 8601 timestamp)
Last time device was seen (ISO 8601 timestamp)
Device record creation timestamp
Device record last update timestamp
Examples
Response Example
Error Responses
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
500 Internal Server Error
Use Cases
Testing Fraud Rules
Create test devices with specific characteristics to verify your fraud detection rules work correctly:Data Migration
Migrate historical device data from your existing system:Manual Device Enrollment
Allow customers to manually register their devices:Next Steps
List Devices
Query devices for an entity
Events API
Auto-register devices via events