Smile API

Overview

Smile API brings together data from government, HR and payroll systems, gig economy platforms and uploaded documents. Its use cases span lending, buy now, pay later, earned wage access, banking, card issuing, recruitment, rental verification and data services. The product is built for organizations integrating verification into their own workflows, not for individuals seeking a standalone consumer service.

The API uses REST, JSON and HTTPS, with an OpenAPI specification and Postman collection for developers. New accounts can test in a Sandbox using mock data; production access requires contacting Smile and is subject to approval. That makes initial evaluation accessible, but teams should factor approval and billable production use into a launch plan.

Key features

Account linking: Smile Wink lets users connect payroll, government or HR accounts to retrieve verified employment and income data. It can give lenders or wage-access providers an alternative to relying entirely on uploaded records, though it depends on a user being able to link an account. Wink can be embedded as a widget or sent by email.

Document processing: Smile Snap extracts and validates data from identity documents, income statements, photographed IDs, PDFs and scans. This adds a route for applicants whose evidence is in documents rather than a linked account, and complements account-based verification.

Risk screening: Smile Signals combines telecom, behavioral and email signals with sanctions, PEP, identity, phone and email screening. It may suit onboarding that needs several kinds of checks; a service needing only one narrow screening function may not need the full combination.

Digital onboarding: Smile Flip supports identity checks, face matching, document capture, form autofill and customizable onboarding workflows. It is relevant to teams assembling identity and application steps into one user journey, while those seeking only a data API may have less use for its workflow capabilities.

Integration and privacy: Smile describes a unified API, plug-and-play APIs and a developer SDK. Users control which parties receive their personal data and can revoke access; Smile says data is deleted through its Revoke API after revocation. The company states that it complies with the Philippines Data Privacy Act of 2012 and supports portability rights under Section 18. Smile Wink says transfers are encrypted and follow industry standards.

Pricing

Smile uses a freemium model with custom pricing for production. The Sandbox plan costs 0.00 USD per free and provides test credentials and mock data only. It is useful for developers assessing integration, but it does not provide live access: production requires approval and is billable.

Smile directs organizations to book a demo or contact the company for pricing. This is a fit for teams prepared to discuss their expected use before budgeting; it is less convenient for buyers who need to compare a published production price or estimate costs without a sales conversation. No production quota, seat limit or renewal term is stated.

Platforms

Smile API runs on API and web. API access is central to integrating its verification capabilities into another service; web access provides a browser platform. The API's REST, JSON and HTTPS approach, plus its OpenAPI specification and Postman collection, gives development teams standard materials for integration.

Who it's for

Banks, fintechs, digital lenders, recruitment agencies, HR teams and other service providers are the intended users. It is particularly relevant when a workflow needs employment or income verification alongside identity checks, document handling or screening. The listed use cases also make it pertinent to rental verification and card issuing. Organizations should look elsewhere if they need immediate production access without approval or a public production price to assess costs upfront.

Pros and cons

• Multiple evidence routes: linked accounts, uploaded documents and data from government, HR, payroll and gig platforms can support workflows with differing evidence sources.
• Broad workflow coverage: account linking, document processing, screening and onboarding can serve teams that need several capabilities through an API offering.
• Useful developer entry point: mock-data Sandbox access, an OpenAPI specification and a Postman collection support evaluation before production approval.
• Production has a gate and a cost: approval is required and live access is billable, so a Sandbox test alone does not establish readiness or cost for launch.
• Budgeting requires contact: production pricing is custom rather than published, which limits straightforward price comparison.

Alternatives

For a broader shortlist, see Employment Verification Software. MyEmployment is worth comparing for a free employee or former-employee service, with Android, iOS, web and API platforms. Choose ADP Workforce Now instead if the requirement is a payroll and HR suite, including an option that adds benefits administration. Clear Verify offers employers a free plan with no setup, monthly or integration fees, and may suit organizations prioritizing that stated fee structure.

MeasureOne Employment Verification is another API and web option, with a free trial and CORE plan features including direct connections, status-level data, PDF processing and real-time results. Konfir Employment Verification may suit buyers preferring pay-as-you-go pricing: its Basic plan is 5.50 GBP per once, billed per successfully verified activity, and includes three users and custom UX branding. Argyle is an API and web alternative with usage-based pricing and no extra charge for reverifications. Decentro is another API and web option, with free setup and unlimited rollover of unused API hits. Zinc is a web-based alternative with a Pay As You Grow plan billed per check.

Verdict

Smile API is a strong candidate for lenders, fintechs and service providers that want account linking, document handling, screening and onboarding capabilities in one integration. The Sandbox and developer resources make it possible to assess the integration with mock data, but the central trade-off is clear: production requires approval and costs are custom. Choose it when the breadth suits the workflow and the organization can accommodate those terms; look elsewhere when immediate live access or an upfront price is essential.