Data-driven decisions
Enrich decision models with verified, consented attributes instead of inferred or scraped data.
← Use cases / Data services
Power your product with verified risk data, on demand.
Request exactly the fields your product needs — identity, income, or a composite risk score — from one composable API, instead of building and maintaining your own verification pipes.
The shape · A continuous loop — data flowing in and out of one shared profile.
The problem
Building verified identity and risk features in-house means integrating with government data sources, payroll systems, and fraud signal providers separately — a multi-quarter engineering effort before a platform can even ship the risk features its own customers are asking for.
The solution
Smile exposes the same verified identity, income, and risk-scoring data it uses internally as a composable API — a platform requests only the fields it needs, and gets back the same profile it would if it had built the pipes itself.
What changes
How it works
From trigger to decision, in four steps.
STEP 1
Trigger the event
Your platform needs to power a risk feature for its own end user — a credit decision, a trust badge, an eligibility check.
STEP 2
Call the API endpoint
Your backend sends a GET request to the endpoint for each data point you need — for example /identities — with the end user's ID, or reads them together from GET /users/{id}/payload.
STEP 3
Real-time processing & webhooks
Smile returns only the data points you request, each with metadata showing which source and provider it came from.
STEP 4
Deliver the output
Your product renders the verified data directly in your own UI — a score, a badge, an eligibility flag — under your own brand.
The code
Request in, structured data out.
Request — cURL
curl "https://sandbox.smileapi.io/v1/identities?userId=tenant-5c1a2e8678e3494eba303ad1afa54ee8&size=1" \
-u "$SMILE_CLIENT_ID:$SMILE_CLIENT_SECRET"Response — 200 OK
{
"code": "OK",
"message": "Success",
"requestId": "5b79399a-6852-4234-bb0e-ad472648282d",
"data": {
"nextCursor": "1259723474",
"items": [
{
"id": "i-17bbf36498de4d68a0d4f86c7b62f69f",
"fullName": "George Cimafranca Palomero, Jr",
"firstName": "George",
"middleName": "Cimafranca",
"lastName": "Palomero",
"suffix": "Jr",
"gender": "Male",
"dob": "1970-08-24",
"maritalStatus": "Married",
"countryResidence": "PH",
"citizenship": "Citizen",
"emails": [{ "address": "gpalomero1234@yahoo.com", "type": "Primary" }],
"phones": [{ "number": "+639175551234", "type": "Mobile" }],
"addresses": [
{
"fullAddress": "12 Maybunga St, Barangay Paraiso, Pasig City, NCR, 1600, PH",
"city": "Pasig City",
"region": "NCR",
"zip": "1600",
"country": "PH",
"type": "Primary"
}
],
"metadata": {
"createdAt": "2021-04-14T09:30:24Z",
"sourceId": "a-17bbf36498de4d68a0d4f86c7b62f69f",
"sourceType": "ACCOUNT",
"userId": "tenant-5c1a2e8678e3494eba303ad1afa54ee8",
"providerId": "upwork"
}
}
]
}
}Security & reliability
Built to be trusted in production.
Data privacy & compliance
Data is encrypted in transit and at rest, sensitive fields are tokenized rather than stored in the clear, and consent is captured at the point of collection — adapted to the data privacy regulations applicable in each market you operate.
Reliability
Idempotent requests, built-in retry support, and published rate limits mean a dropped connection or a retried request never produces a duplicate check. Each client can make up to 20 requests per second per IP address across all endpoints; anything above that returns HTTP 429.
Graceful failure
Every error returns a descriptive status code and a structured JSON body with a machine-readable code and a request ID — never a bare 500 — so a failed check is something your application can handle, not just log.
Under the hood
Relevant products
AI & data-driven decisions
How does Smile API power AI and data-driven decisions?
Smile API delivers consented, verified identity, income and risk attributes as structured data. Data teams and AI products can use them to build models and power data-driven services.
Features for your models
Clean, labelled and consented attributes — identity, income, device and watchlist outcomes — ready to use as inputs for credit and fraud scoring models.
Context for AI agents
AI products can call Smile API as a tool to fetch fresh, verified context about a consenting user whenever a decision needs it.
Can Smile API data be used to build AI models?
- Consented Smile API attributes are structured and labelled, which makes them suitable as model features within the scope of the end user's consent and your agreement with Smile.
Is Smile API data structured for machine use?
- Yes. Results come back as consistent, typed JSON fields — verification statuses, scores and flags — so rules engines, machine learning models and large language model agents can read them without manual cleanup.
How is consent handled when AI uses Smile API data?
- Every request carries the consent record captured from the end user, and Smile returns only the signals that consent covers. Your models and agents work with permissioned data, never scraped or self-reported guesses.
{
"profile": "prf_8f21",
"identity": "verified",
"income": { "status": "verified", "source": "payroll" },
"device": "trusted",
"fraudScore": 0.07,
"watchlists": "cleared",
"suggestedAction": "approve"
}