Base APIs - Endpoint Overview
This is an overview of the available endpoints. For each base path, there is a sub-page with more information.
Some data is non-editable because the data must always be set up within BC.
In some cases, new entries can only be created with a specific procedures, for example Lots.
Even if there is a POST, PATCH, DELETE option, the data is only editable, as long as it is still editable within Wisefish. For example, if a status does of an entry does not allow changes in BC, the functionality is the same when trying to modify with an API.
Endpoint | Description | Requests available | Procedures | |||
1. Setup | ||||||
| Wisefish User Profiles |
|
| |||
| Locations |
| ||||
| Stock Centers with Certification Program Registers. |
|
|
|
|
|
| Fishing Areas |
|
|
|
| |
| Landing Types |
|
|
|
| |
| Item categories. |
|
|
|
| |
| Processing Stages |
|
|
|
| |
| Raw Material Size Quality Grades |
|
|
|
| |
2. Master data | ||||||
| Customers, the most important fields. |
|
|
|
| |
| Vendors |
|
|
|
| |
| Vessels |
|
|
|
| |
| Items, a simple list. |
| ||||
| Items with units and variants and the most important fields. |
|
|
|
| |
| Item units. |
|
|
|
| |
| Item variants. |
|
|
|
| |
| The Certification Program Register. |
|
|
|
| |
3. Inventory | ||||||
| List of inventory items with quantity in stock |
|
| |||
| Lots with catch origin and certifications. |
|
|
|
| See procedure on |
| Certification Programs for a Lot |
|
|
|
| |
| Lot Groups. These are groups to be added on Lots. |
|
|
|
| |
| Trade Items available in the warehouse. |
| ||||
| Pallets |
| ||||
4. Purchase & Sales | ||||||
| Purchase Agreements that have not been posted, with type = Receipt |
|
|
|
| Procedures are available to do the most general actions:
|
| Purchase Agreement Lines, with type = Receipt. |
|
|
|
|
|
| Closed Purchase Agreements, with type = Receipt Lines are shown with |
| ||||
| Sales Agreements, with type = Delivery Lines are shown with |
|
|
|
|
TO-DO: methods came from Lava, TEST! do we want to post as well? have 2 options? |
| Sales Agreement Lines, with type = Delivery |
|
|
|
| Methods are given for easier usage (instead of PATCH):
|
| Closed Sales Agreements, with type = Delivery |
| ||||
| Extended texts can be added on agreements. |
|
|
|
| |
| Scheduled trips. |
| This could be modified to allow changes. | |||
| Transport Units. |
| This could be modified to allow changes. | |||
5. Production | ||||||
| Production lots. |
|
|
|
|
There is also a procedure on |
| TO DO | |||||
6. Warehouse (std) | ||||||
| Warehouse Receipts, i.e. the standard documents created for standard Purchase Orders |
|
| |||
| Warehouse Shipments, i.e. the standard documents created for standard Sales Orders |
|
| |||
7. Change Log | ||||||
| The module logs changes on the main tables |
|
| |||