The API Report CardAPI Index
Erply

Erply API

POS / Hospitality · erply.com

Erply publishes an open, documented API covering everything the back office and POS can do, plus purpose-built REST APIs for PIM, reports, and WMS. Access is free and self-serve, with credentials exchanged for a session key. Webhook payloads are thin, so integrators fetch back after events.

Last verified: July 2026Retail & Ecommerce
API GRADE
B+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODAn open all-in-one JSON API plus newer purpose-built REST APIs: PIM, Reports, JSON, WMS, CDN, and Account Admin.
AccessGOODFree and self-serve: back-office credentials obtain a session key, with no partner approval required.
CoverageGOODProducts, customers, sales, inventory, webstore, POS, company, reports, and storage; WMS and PIM get dedicated APIs.
AuthPOORSession keys come from username and password via verifyUser; no OAuth2, no per-app scoping, and awkward credential rotation.
Docs & DXGOODDocs at learn-api.erply.com, a public GitHub org, and the Automat low-code app builder; depth varies across the newer APIs.
StabilityGOOD
Supergood: Erply shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

Erply scores B+ on the API Report Card. Erply publishes an open, documented API covering everything the back office and POS can do, plus purpose-built REST APIs for PIM, reports, and WMS. Access is free and self-serve, with credentials exchanged for a session key. Webhook payloads are thin, so integrators fetch back after events.

Tried to integrate with Erply?
SOURCES
Legacy 'Erply API' is a sprawling all-in-one endpoint - developers must choose between several overlapping APIs (Erply API vs PIM API vs JSON API vs WMS API) without clear guidance on which to pick wiki.erply.com
Webhook/push-notification payloads are limited - integrators often have to fetch back to the REST API after a webhook fires, increasing latency and call volume learn-api.erply.com
Rate limits exist but are sparsely documented; integrators report being throttled without clear guidance on quotas wiki.erply.com
Session-key auth (username + password to obtain a session key) is dated vs OAuth2; rotating credentials and per-app scoping are awkward learn-api.erply.com
SDK coverage is thin - cURL and PHP examples are the main getting-started path; no official first-party SDKs for JavaScript/TypeScript, Python, Go, etc. learn-api.erply.com
Documentation is split across learn-api.erply.com and wiki.erply.com with inconsistent depth across the newer specialized REST APIs wiki.erply.com
UI/UX described as dated and unintuitive - reviewers cite a steep learning curve and 'quirks' that require training to navigate g2.com
Customer support often unresponsive, including for enterprise-tier customers; tickets reportedly go unanswered g2.com
Feature breadth overwhelms new users - extensive configuration options without strong defaults or guided onboarding capterra.com
Some advanced features and attributes are not intuitive; admin workflows feel buried capterra.com
Pricing is opaque - no public pricing, sales-led quotes only, customers report inconsistent quotes capterra.com
Reports of bugs and reliability issues in the back office over time, requiring workarounds trustradius.com