Reference · built on requestConnectorERP & finance

Fishbowl Advanced

Parts, inventory by location, purchase and manufacture orders, and vendors from a Fishbowl Advanced server's REST API.

Request accessPricing ↗

About

Fishbowl Advanced is on-premise inventory and manufacturing software; the server runs on your network or on Fishbowl's hosting. Its REST API listens on the server's API port, 2456 by default, and uses GET, POST, and DELETE against JSON objects for parts, inventory, purchase orders, manufacture orders, vendors, and payments. A CSV import endpoint reaches whatever the desktop import tools can load, and a data-query endpoint runs SQL against the database.

An operator on Fibric reads quantities by location and open purchase orders, then proposes a purchase order, a manufacture order, a stock move, or a cycle count for your approval, with a receipt of what changed and how to reverse it.

This is a reference listing. It documents what Fibric would read from Fishbowl Advanced and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Parts with type, unit of measure, UPC, bill-of-materials flag, and serial-number tracking, through GET /api/parts
  • Inventory quantities by part, location, and location group, including tracking items, through GET /api/parts/inventory
  • Purchase orders with status, vendor, buyer, dates created, scheduled, and completed, and their line items
  • Manufacture orders, which organize the work orders that make, disassemble, or repair items
  • Vendors with account number, address, and active flag; location groups; units of measure
  • Any table the logged-in user may read, through GET /api/data-query with a SQL statement

Proposed actions

  • Target capability: propose a purchase order, then its issue, un-issue, close-short, or void
  • Target capability: propose a manufacture order and its issue or close-short
  • Target capability: propose adding, moving, cycle-counting, or scrapping inventory for a part at a location
  • Target capability: propose a CSV or JSON import by its Fishbowl import name, for example Sales-Order-Details

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Plan cycle counts from what moved

    Read inventory by location group and propose a count list for one location, then record each count through the cycle endpoint once a person confirms it.

    With Cycle Count Plan, Count Variance

  • Draft a purchase order from the best cost

    Pull the best cost for a part and its vendor part number, then propose the purchase order and hold it un-issued until someone approves.

    With Purchase Order Draft

  • Chase purchase orders past their scheduled date

    Filter purchase orders by issued and scheduled dates and propose the vendor follow-up for each line still open.

    With PO Chase

  • Move stock before a manufacture order starts

    Check the parts a manufacture order needs and propose moving inventory to the work location before the order is issued.

    With Stock Transfer

Requirements

  • A Fishbowl Advanced server reachable on its API port, 2456 unless changed in Fishbowl Server Administration
  • A Fishbowl user for the integration; every call runs with that user's access rights
  • An administrator to approve the integrated app inside Fishbowl the first time it logs in
  • A certificate on the Fishbowl server for TLS, which Fishbowl recommends
  • A TOTP code at login when multi-factor authentication is on for that user
Authentication
A session token from POST /api/login with a Fishbowl username and password plus an appName, appDescription, and appId; the token goes in Authorization: Bearer on every later call.

Limits

  • No webhooks or change feeds are documented; reads poll the list endpoints and the data-query endpoint
  • The public reference documents only DELETE for sales orders; creating one goes through the import endpoint
  • No rate limits are documented; list calls page at 100 results by default
  • The reference on help.fishbowlinventory.com is an example; the documentation matching your version lives on your own Fishbowl server

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Fishbowl Advanced ↗

Questions and answers

Does Fishbowl Advanced have a cloud API?
No. Fishbowl Advanced is on-premise, and its REST API runs on your Fishbowl server, on port 2456 by default. The server can sit on your network or on Fishbowl's hosting; either way the integration needs network reach to it.
How does an app authenticate?
POST /api/login with appName, appDescription, appId, username, and password returns a token. The first login must be approved in Fishbowl by an administrator. If MFA is on, the server answers 401 with an MFA: Required header and you resend with mfaCode.
How do I create a sales order through the API?
The public reference documents DELETE /api/sales-orders/:id only. Creating or updating sales orders uses POST /api/import/:name, where name is the import's default name with spaces replaced by hyphens, and the body is CSV or JSON rows.
Ask about Fishbowl Advanced

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Fishbowl Advanced through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy