Build login, consent, payments, employee identity, check-in and physical access on SafeQloud infrastructure. Every transaction tied to a real verified person.
Requires a verified personal account and a SafeQloud Business account
// 1. Redirect user to SafeQloud — they scan QR and consent const authUrl = `https://safeqloud.com/walk/authorize.php ?response_type=code &client_id=${clientId} &state=xyz&signin=1` // 2. Exchange code for access token const token = await fetch('https://safeqloud.com/walk/token.php', { method: 'POST', body: { grant_type: 'authorization_code', code, client_id, client_secret } }) // 3. Verify and receive identity // → { "type":"signin", "first_name":"Alex", "email":"alex@...", // "country_of_residence":"SE", "user":1 }
Developer access
Every developer on SafeQloud is a verified individual tied to a verified business. This is what makes the identity layer trustworthy.
Sign up at safeqloud.com. This is your SQ ID — your verified personal identity on the platform.
Complete identity verification. This links your real identity to your SafeQloud account. Required before any corporate access.
Register your company on SafeQloud Business. You must be an employee or owner of the company you register.
Request a developer account from your corporate dashboard. After approval, you generate client credentials per API and per application.
The APIs
Each API requires its own client credentials. You generate them per application from your developer dashboard.
// Step 1 — redirect user to SafeQloud GET https://safeqloud.com/walk/authorize.php ?response_type=code &client_id=YOUR_CLIENT_ID &state=xyz &signin=1 // Step 3 — verify session and receive identity POST https://safeqloud.com/walk/resource_signin.php?signin=1 // → Response { "type": "signin", "first_name": "Alex", "last_name": "Johnson", "email": "alex@...", "country_of_residence": "SE", "user": 1 }
// Redirect user to consent flow GET https://safeqloud.com/walk/authorize.php ?response_type=code &client_id=YOUR_CLIENT_ID &state=xyz &signin=1 // → Response after QR scan and consent { "type": "signin", "first_name": "Alex", "email": "alex@...", "country_of_residence": "SE", "seller_company_id": 1, "user": 1 }
// Send user to payment flow with total GET https://safeqloud.com/user/index.php/LoginAccount/loginPurchaseVerify ?response_type=code &client_id=YOUR_CLIENT_ID &purchase=1 &total=89.00 // → Verified response { "user": "0", // 0=personal, 1=company "company": "0", // invoice destination "customer_id": "cu_***", "transaction_id": "tran_***" }
// Encrypt employee data and send to SafeQloud const payload = encrypt({ company_email: "company@example.com", fname: "Alex", lname: "Johnson", wemail: "alex@company.com", enumber: "EMP-001", d_country: "SE" }) // POST to POST https://safeqloud.com/user/index.php/Curl/addEmployee/{encrypted} // Relieve employee POST https://safeqloud.com/user/index.php/Curl/relieveEmployee/{encrypted}
// Wake SafeQloud app from your Android app Intent URL: https://safeqloud.com // Wake from iOS app URL Scheme: com.Qloudid.Url // Receive session and verify POST https://safeqloud.com/user/index.php/QloudidApp/verifyInterAppSession { session: session_received_from_app } // → Verified response { "user_id": 1, "result": 1 }
// Verify identity at access point POST https://api.safeqloud.com/v1/identity/access/verify { "qr_token": "sqt_live_abc123...", "access_point": "door_server_room_b2", "company_id": "YOUR_COMPANY_ID" } // → Response { "granted": true, "user_id": "usr_7f3a9b...", "role": "engineering", "logged_at": "2026-04-11T14:32:00Z" }
The pattern
One mechanic across six use cases. Once you integrate one API, the rest are familiar.
Your app renders a SafeQloud QR code at the relevant moment — login button, checkout page, door terminal, or document.
The user opens their SafeQloud app, taps Scan QR, and points at your QR. They enter their SafeQloud password to confirm.
Your server exchanges the code for a token, then re-verifies with SafeQloud. Identity confirmed. Session established. Access granted.
Get developer access
Developer access is approved per business. Once approved, you generate client credentials for each API and each application from your corporate dashboard.