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
string
required
UUID of the entity to associate this device with
Request Body
string
required
Unique identifier for this device. This should be a stable identifier that persists across sessions (e.g., device fingerprint, IMEI, advertising ID)
string
Entity type for audit trail. Options:
person, company. Default: "person"string
External ID of the entity (your systemβs identifier). Stored denormalized on the device for queries.
string
Entityβs tax ID (e.g., CUIT, CPF). Stored denormalized on the device for queries.
string
Device platform. Options:
android- Android deviceios- iOS deviceweb- Web browser
"android"string
Device manufacturer name (e.g., βsamsungβ, βAppleβ, βGoogleβ)
string
Device model identifier (e.g., βSM-A156Mβ, βiPhone 15 Proβ, βPixel 8β)
string
Device brand name (e.g., βsamsungβ, βAppleβ)
string
User-defined device name or hardware name
string
Operating system version (e.g., βAndroid 16β, βiOS 17.2β, βWindows 11β)
string
System name for iOS devices (e.g., βiOSβ)
string
System version for iOS devices (e.g., β17.2β)
string
Browser name for web platform (e.g., βChromeβ, βSafariβ, βFirefoxβ)
string
Browser version for web platform (e.g., β120.0.6099.129β)
number
Geographic latitude coordinate (-90 to 90)Example:
-34.6037number
Geographic longitude coordinate (-180 to 180)Example:
-58.3816string
City name (e.g., βBuenos Airesβ, βNew Yorkβ, βLondonβ)
string
State or province (e.g., βBuenos Airesβ, βCaliforniaβ, βOntarioβ)
string
Country name (e.g., βArgentinaβ, βUnited Statesβ, βCanadaβ)
string
ISO 3166-1 alpha-2 country code (e.g., βARβ, βUSβ, βCAβ)
string
IP address (IPv4 or IPv6) from which the device is accessingExample:
"10.40.64.231"boolean
default:"false"
Whether this device is detected as an emulator or simulator
boolean
default:"false"
Whether this device is rooted (Android) or jailbroken (iOS)
Response
boolean
Indicates if the request was successful
object
The created device object
string
gu1βs internal device UUID
string
Your provided device identifier
string
External device identifier (same as deviceId)
string
UUID of the associated entity
string
Entityβs external ID (denormalized)
string
Entityβs tax ID (denormalized)
string
Device platform (android, ios, web)
string
Device manufacturer
string
Device model
string
Device brand
string
User-defined device name or hardware name
object
Additional device metadata (JSON object). Platform-specific: Android (hardware, buildId, sdkVersion), iOS (systemName, identifierForVendor), Web (userAgent, etc.)
string
Operating system name
string
Operating system version
string
Browser name (web only)
string
Browser version (web only)
number
Geographic latitude
number
Geographic longitude
string
City name
string
State/province
string
Country name
string
ISO country code
string
IP address
boolean
Emulator detection flag
boolean
Root/jailbreak detection flag
boolean
Whether device is blocked
boolean
Whether device is marked as trusted
string
First time device was seen (ISO 8601 timestamp)
string
Last time device was seen (ISO 8601 timestamp)
string
Device record creation timestamp
string
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