Developer ToolsFree generatorPDF, Excel, Word exportKatanaDiscrete Manufacturing

Katana MRP API Request Builder for Orders and Inventory

Katana provides an Open API that lets you pull orders, products and stock into reports, a warehouse tool or a spreadsheet. This builder writes the request for the resource you choose, as curl and as a short Python snippet.

Fill in

Resource

Page size

Page number

Generated code

Free, optional. Reopen it on any device.

Download:

curl request

curl -X GET "https://api.katanamrp.com/v1/manufacturing_orders?limit=50&page=1" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

Python snippet

import os
import requests

BASE = 'https://api.katanamrp.com/v1'
headers = {
    'Authorization': 'Bearer ' + os.environ['KATANA_API_KEY'],
    'Accept': 'application/json',
}

resp = requests.get(BASE + '/manufacturing_orders', headers=headers, params={'limit': 50, 'page': 1}, timeout=30)
resp.raise_for_status()
for row in resp.json().get('data', []):
    print(row.get('id'), row.get('status'))

Katana issues API keys in its settings; keep the key in an environment variable, never in shared code. Resource names, filters and rate limits can change, so check the current Katana API documentation, and test with a small page size first. This tool builds read requests only.

Planning an integration between MRP and other systems?

Optional: talk through your data flow with an ERP integration specialist.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use the builder

Pick a resource, a page size and a page number. Copy the curl command to test the call, then use the Python snippet as the start of a scheduled job. The API key goes in an environment variable and is sent as a bearer token. Start with a small page size, confirm the shape of the response, and only then loop through pages.

Create the API key in Katana settings
Store it in an environment variable
Test one page before looping
Check the current documentation for filters and rate limits

What you can build

Common uses are a daily export of open manufacturing orders to a shared sheet, a low-stock alert that reads inventory, syncing sales orders from an ecommerce store, and feeding a BI dashboard. Katana is a cloud tool aimed at small product makers, so integrations usually run in a small script or an automation platform rather than a dedicated middleware server.

Handling pages and limits

List endpoints return results in pages, so loop until a page comes back shorter than the limit. Respect rate limits by adding a short pause and retrying on a too-many-requests response with backoff. For large catalogs, fetch changes since your last run if the endpoint supports an updated-since filter, rather than pulling everything every time.

Common mistakes

Hard-coding the API key in a script that later gets shared. Ignoring pagination and reporting only the first page of orders. Treating a successful HTTP status as proof that the data is complete. Writing back to Katana from an untested script, which can change stock or orders. Use read calls until the process is proven, and log every run.

Frequently Asked Questions

Where do I get a Katana API key?

API keys are created by an account admin in the Katana settings area, in the API section. Copy the key when it is shown, store it in a secrets manager or environment variable, and revoke it from the same screen if it is ever exposed.

Does this builder create or change orders?

No. It only builds GET requests that read data. Creating or updating orders is possible through the API but should be built and tested separately in a safe environment, because a bad write can change inventory commitments and production plans.

How do I handle many pages of results?

Increase the page number until a response returns fewer rows than your limit or none. Add a small delay between calls to stay inside rate limits, and handle error responses with retries. Save the highest updated time you processed to fetch only changes next time.

Is Katana enough for a growing manufacturer?

It suits small make-to-order and make-to-stock product businesses with simple routings. Plants with complex multi-level BOMs, lot genealogy, quality records or compliance needs often move to a fuller ERP or MES. Use a readiness assessment to see where your needs sit.

If your small plant is outgrowing a cloud MRP and you want to compare options or connect data across systems, Netray can help you map the integration.

Talk to an Expert Explore More Free Tools