Developers

Build on ProdSys

A modern REST API, webhooks, OAuth, and a sandbox environment — everything you need to connect ProdSys to your tools and workflows.

Explore the live API → Read the docs

# List recent sales orders
curl "https://api.prodsys.com/v1/sales/orders?limit=10" \
  -H "Authorization: Bearer $PRODSYS_TOKEN" \
  -H "Accept: application/json"

import { ProdSys } from '@prodsys/sdk';

const client = new ProdSys({ token: process.env.PRODSYS_TOKEN });

const orders = await client.sales.orders.list({ limit: 10 });
console.log(orders);

from prodsys import ProdSys

client = ProdSys(token=os.environ["PRODSYS_TOKEN"])

orders = client.sales.orders.list(limit=10)
print(orders)

var client = new ProdSysClient(Environment.GetEnvironmentVariable("PRODSYS_TOKEN"));

var orders = await client.Sales.Orders.ListAsync(limit: 10);
Console.WriteLine(orders);

Our architecture

The same API the product runs on

Unlike most ERPs that maintain an internal API for the application and a separate, narrower public API for integrations, ProdSys runs on a single API. The same one your developers, partners, or in-house team can call.

🔓

No API gap

Anything the ProdSys application can do, your integration can do too. There's no hidden internal endpoint that's "off limits" to customers.

⚡

Day-one feature parity

New product features are immediately available via API, because they're built with it. No waiting for the integration team to "expose" something.

🧩

Headless-ready

Build custom UIs, kiosk applications, mobile experiences, or industry-specific workflows on top of the same data and business logic that powers the standard product.

🛡

Role-based access

API accounts get the same fine-grained permissions as users — limit them to specific modules, read-only access, specific companies, or scoped operations. Full API capability, full access control.

Why this matters: with most ERPs, integration projects eventually hit the "this isn't in the public API" wall. With ProdSys, there is no wall — and your developers can ship faster because they're working with the same surface area as the product team.

{}

See the API for yourself

Live Swagger documentation — every endpoint, every parameter

No marketing fluff — the full live API specification, identical to what ProdSys customers use today. Browse it, try requests, see real responses.

Open Swagger →

What you can build

From simple syncs to full integrations

The API covers every module — read and write across finance, sales, inventory, procurement, projects and more.

🛒

E-commerce sync

Push orders from your webshop, sync inventory levels back, automate fulfilment.

📊

Custom dashboards

Pull data into Power BI, Tableau, or your own internal tools with read-only API keys.

🔄

Workflow automation

Trigger emails, Slack messages, or external actions on order or invoice events via webhooks.

📦

Warehouse & WMS

Integrate with handheld scanners, label printers, and third-party WMS systems.

💼

CRM & marketing

Sync customer data and order history into HubSpot, Salesforce, Mailchimp or others.

📱

Mobile apps

Build internal apps for field staff, sales reps or warehouse workers using the API.

Quickstart

From zero to first API call in 5 minutes

Create an API account

In ProdSys, go to System → API accounts and create a new account. Assign the roles your integration needs — least privilege wins.

Read the full guide →

Generate a bearer token

Tokens are scoped to the API account's roles and can be revoked at any time. Store them as environment variables — never commit them.

Make your first request

Call any endpoint with your bearer token in the Authorization header. Start with read-only endpoints to verify access.

curl "https://api.prodsys.com/v1/me" \
  -H "Authorization: Bearer $PRODSYS_TOKEN"

Test in the sandbox

Build and validate without touching production data. The sandbox mirrors the production API and refreshes monthly.

Platform capabilities

A modern integration surface

REST API

JSON over HTTPS, consistent resource naming, pagination, filtering and sorting on every list endpoint.

Webhooks

Subscribe to events like order.created, invoice.paid, signed payloads for verification.

OAuth 2.0

Build integrations that act on behalf of users — full OAuth flow with refresh tokens, scopes and consent screens.

Sandbox environment

Identical to production, isolated data, no rate limits during development. Refresh on demand.

Rate limits

600 requests/minute per token, 10,000/hour for OAuth apps. Burst-tolerant. Limits visible in response headers.

Versioned API

Current version: v1. Breaking changes ship in new versions with 12 months overlap. Clear changelog.

Resources

Everything in one place

📖

API documentation

Full reference for every endpoint, parameter and response.

🚀

Step-by-step guide

From authentication to your first integration, end to end.

📡

API status

Real-time uptime and incident notifications for the API.

💬

Developer support

Email us at developers@prodsys.com — we respond within 1 business day.

FAQ

Developer questions

Is API access included in all plans?

API access is included on the Standard plan and above. Starter plans can read but not write. See pricing for details.

What happens if I exceed the rate limit?

You'll get a 429 Too Many Requests response with a Retry-After header. Implement exponential backoff and you'll be fine — the limits are generous enough for almost any real-world integration.

Do you offer official SDKs?

Node.js, Python and C# SDKs are in active development. PHP and Go are on the roadmap. For now, the REST API works from any HTTP client — and most developers find that's enough.

Can I publish my integration on the ProdSys marketplace?

Yes — we feature partner integrations on our integrations page. Reach out at partners@prodsys.com to start the listing process.

Is there a free tier for testing?

Every paid plan includes sandbox access at no extra cost. For ISVs and partners building commercial integrations, we offer free developer accounts — contact developers@prodsys.com.