The API Report CardAPI Index
Lano

Lano API

Global Payroll Consolidation / EOR / Contractor Management · lano.io

Lano documents a REST API with a full OpenAPI spec, JWT auth scoped per legal entity, and webhooks, covering hiring, payroll runs, and employee data. It is officially in closed beta: access means contacting Lano, passing partner qualification, and receiving manually provisioned credentials.

Last verified: July 2026HR & Payroll
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODDocumented REST API with a full OpenAPI spec covering the employee lifecycle, though officially still in closed beta.
AccessPOORClosed beta gated on partner or enterprise qualification; credentials and sandboxes are provisioned manually by Lano's team.
CoverageGOODHiring and onboarding, payroll cycles, bonuses and expenses, employee and legal entity data, plus webhooks for events.
AuthPOORJWT tokens scoped to specific legal entities, but issuance is manual and there is no OAuth2 app program for third parties.
Docs & DXPOORThe OpenAPI reference sits behind a request access gate; no self-serve sandbox keys, public SDKs, or open dev portal.
StabilityMIXEDStandardized errors and pagination are specced, but closed beta status means the surface can shift before general availability.
Supergood: Lano has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Lano scores D+ on the API Report Card. Lano documents a REST API with a full OpenAPI spec, JWT auth scoped per legal entity, and webhooks, covering hiring, payroll runs, and employee data. It is officially in closed beta: access means contacting Lano, passing partner qualification, and receiving manually provisioned credentials.

Tried to integrate with Lano?
SOURCES
API is in 'closed beta' and access requires contacting sales/support - no self-serve developer signup, sandbox keys, or public reference site lano.io
Sandbox environments are provisioned manually for partners and enterprise customers only - not generally available for prototyping lano.io
API tracker profile shows most public-API metadata missing (no published base URL, rate limits, webhook reference, or auth details on the tracker) - documentation lives behind a request-access gate apitracker.io
OAuth2 / Marketplace-style third-party app program is not publicly documented; integrations appear to be bilateral partner deals rather than self-serve lano.io
Payroll consolidation integrations bottleneck on customer-side acquisition of third-party in-country payroll API credentials, often adding 2-3 weeks per provider whichpayroll.com
Integration ecosystem is thin (~30 native integrations) and access to integrations requires purchasing Lano's 'Intelligence' module as a paid add-on lano.io
Documentation and help-center content is thinner than larger competitors, limiting self-service troubleshooting for developers eorhq.com
JWT tokens are scoped per legal entity - multi-entity customers must manage and rotate multiple tokens with no documented central key-management surface lano.io
No public documentation of rate limits, retry semantics, or idempotency guarantees on the API lano.io
Webhook event catalog, delivery guarantees, retry behavior, and signing scheme are not publicly documented outside the gated OpenAPI spec lano.io
100% partner-entity EOR model with no Lano-owned legal entities - users report escalation uncertainty during complex terminations or regulatory investigations vs Deel/Remote's owned-entity coverage eorhq.com
EOR onboarding typically takes 7-10 business days even in straightforward markets, slower than Deel's 2-5 days eorhq.com
Only 28 supported payout currencies vs 120+ at Deel; contractors absorb conversion costs for unsupported currencies eorhq.com
Customer support is concentrated in European business hours; APAC and Americas queries reportedly wait 6-12 hours for first response eorhq.com
Variable support quality - resolution times depend on the in-country partner involved, with delays when issues require escalation beyond Lano's internal team employborderless.com
Setup is complex and lengthy - 'multiple clicks' to configure, compliance documents 'not always easy to locate,' and noticeable learning curve employborderless.com
No dedicated mobile app; key administrative features are desktop-only employborderless.com
Inconsistent invoicing - users report invoicing errors and delays that affect cash flow g2.com
Platform UI feels split between old and new designs in places g2.com
Thin third-party review footprint (~35 combined G2 + Capterra reviews) makes vendor diligence harder vs Deel/Remote at thousands of reviews whichpayroll.com
Integration ecosystem is small (~30 native connectors vs Deel's 200+); integrations require buying Lano's 'Intelligence' module as an add-on lano.io
Pricing approaches Deel-level rates at the EOR tier (~EUR 499-600/mo) without the coverage, owned entities, or onboarding speed of larger vendors whichpayroll.com
Payroll consolidation setup adds 2-3 weeks because the bottleneck is acquiring third-party API credentials from each in-country provider whichpayroll.com
No specialized compliance coverage documented for heavily regulated industries (healthcare, financial services) employborderless.com