Build against the Fiddle REST API
Read and write Fiddle data with plain HTTPS requests. Use the HTTP client you already trust, send JSON, and authenticate with an API key from your Fiddle account.
curl "https://fiddle.io/rest/api/v2/inventory-items?size=50" \
-H "X-API-Key: YOUR_API_KEY"
# Create a sales order (returns it, or a 400 naming each problem)
curl -X POST "https://fiddle.io/rest/api/v2/sales-orders" \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"salesOrderNumber": "WEB-1001",
"integrationSourceId": "WEB-1001",
"customerId": "CUSTOMER_ID",
"items": [
{ "sku": "SOAP-LAV-4OZ", "quantity": 2, "price": 4.5 }
]
}'No package install required
Use any standard HTTP client
Fiddle exposes a REST API, not a set of official language packages. Your integration can run from a server, worker, script, automation platform, or internal app as long as it can send authenticated HTTPS requests.
What the API is for
Connect Fiddle to the systems your team already runs
The API is scoped to the same account data users can access in the app, so custom integrations can work with inventory, orders, stock movement, and production records without inventing a separate data model.
Inventory sync
Read items, locations, and stock levels so external systems stay aligned with Fiddle.
Order workflows
Create and fetch sales orders for custom storefronts, operations tools, and channel bridges.
Stock adjustments
Post controlled adjustments for damaged goods, cycle counts, receiving fixes, and transfers.
Purchasing
Create purchase orders and move them through confirm, hold, close, and cancel.
Build path
A practical start for custom integrations
Start narrow, verify against your own Fiddle data, then expand the integration after the request and error handling are boring in the best possible way.
Create an API key
Generate a dedicated key under Integrations → Fiddle API, copy it once, and store it in your secrets manager.
Open the live reference
Use Redoc to inspect schemas or Swagger UI to test requests while shaping your payloads.
Make a first request
Send JSON over HTTPS with your key in the X-API-Key header. Start with a read-only endpoint before writing.
Keep data in sync
Fiddle does not send webhooks yet. Poll list endpoints on a schedule and page through new records.
Documentation
Real references, examples, and setup guides
Readable API reference
Browse the generated REST reference for endpoints, fields, request bodies, and response shapes.
Endpoints by resource
The most-used endpoints grouped by resource, with request examples and links to Swagger UI.
REST API overview
Understand the base URL, JSON request format, account scoping, and first request.
Get an API key
Create a key in Fiddle and send it in the X-API-Key header on every server-side request.
Auth and rate limits
Review authentication errors, request limits, retry behavior, and secure key handling.
Common API recipes
Copy curl examples for listing items, fetching records, creating orders, and adjusting stock.
Need a hand?
Bring us the workflow you are connecting
If you are mapping a custom storefront, warehouse tool, reporting pipeline, or ERP bridge, we can help you choose the right endpoints and rollout plan.