Recipe & Menu Engineering Import API Release Notes

Overview

This page explains the changes that have happened to our Recipe & Menu Engineering Import API since August 2020.

These Release Notes are up-to-date at the time of the release. Further improvements or corrections to our API documentation will normally occur in the guide and reference only.

If you have already integrated with Fourth and would like to be kept abreast of API changes via email, please fill in this form.

Note: Access to new POST and DELETE operations is provided only on request. If you wish to use a new POST or DELETE operation, please get your customer to request access on your behalf. New GET operations are normally available to integrated partners immediately, unless otherwise indicated.

26 June 2024 - GET /suppliers and POST/suppliers, 'Supplier Type' Property Added

To provide more available supplier options when suppliers are created via the import API, we've added the property 'Supplier type' as an optional value. 

POST /suppliers

Note also that the import logic has been changed so that if the optional 'supplier type' property is not included in the payload, the supplier will be created as supplier type 'Supplier and Distributor'. Previously, suppliers created via the import API were created as 'Supplier Only'. This change aligns the import API logic with the UI.

Valid values for property supplierType

1. Supplier Only
2. Supplier and Distributor
3. Distributor Only

Example POST body:

  {
    "supplierId": 123,
    "accountNumber": "AccountNumber",
    "supplierName": "SupplierName",
    "alternateSupplierName": "Alternate Supplier Name",
    "countryGuid": "45418C37-E44D-4889-A65C-B6E9040BD850",
    "supplierCurrencyCode": "GBP",
    "supplierType": "Supplier and distributor"
  }
]

GET /suppliers

Example GET body:

[
  {
    "supplierId": 123,
    "accountNumber": "AccountNumber",
    "supplierName": "SupplierName",
    "alternateSupplierName": "Alternate Supplier Name",
    "countryGuid": "45418C37-E44D-4889-A65C-B6E9040BD850",
    "supplierCurrencyCode": "GBP",
    "supplierType": "Supplier and distributor"
  }
]

Breaking change notification

20th August 2023

As part of its ongoing commitment to the security of its customer’s information, Fourth will be updating its platform to require all connections to use TLS 1.2 or higher from 9 January 2024. Older versions of TLS will be retired.

TLS is the encryption method used to secure communications over HTTPS. This will have no impact on SFTP connections.

22 March 2023 — Two new properties for GET and POST /ingredientsalternates

Two new properties, TransferRequisitionStatus and ItemVatable, have been added to these endpoints:

• POST ingredientsalternates — Add or update alternate ingredient
• GET ingredientsalternates — Get alternate ingredients

These properties exist already within the POST and GET /ingredients endpoints. This update ensures that adding alternate ingredients via the API behaves similarly to adding alternate ingredients via the UI.

If the properties are excluded from POST requests, then:

• When creating a new alternate, Fourth copies the properties from the parent ingredient
• When updating an existing alternate, the existing properties are not changed

The TransferRequisitionStatus field must be either true (sites can transfer the product internally) or false. If it is included in the payload with an empty string, then for new alternates the value is copied from the parent ingredient, while for existing alternates the value remains unchanged.

The ItemVatable field can be one of:

• Yes — VAT applies to the item
• No — VAT does not apply to the item
• - — The item is otherwise exempt from VAT

For more information about these endpoints, see the API Reference: POST ingredientsalternates and GET ingredientsalternates.

11 January 2023 — SupplierOrderUom now available in more ingredient requests

We have added the ingredient property, Supplier Order UoM, to the following requests that relate to alternate ingredients:

• GET /ingredientalternates — Get summary of alternates for ingredients
• GET  /ingredientsalternates — Get alternate ingredients
• POST /ingredientsalternates — Add or update alternate ingredient

The possible values for POST requests are EA, CS, and KGM. If you send through an invalid value then you will receive an error response.

Property name and example value:  

"SupplierOrderUom": "KGM",

For information on UoM values please see Unit of measure (UoM) values and codes.

11 January 2023 — Change to Swagger UI location

The location of the Swagger UI has changed for the API. This UI is available to integrated partners and customers as necessary for testing purposes. The new location is:

<ROOT>/api/ingredientandaccessimport/swagger/index.html

Maintenance Notification

As part of the continued commitment to the scalability and security of our technology stack, Fourth will be completing proactive maintenance to the database tier that underpins the Recipe & Menu Engineering (RME) platform.

Scheduled maintenance windows are:

• APAC  – Wednesday 12th October 2022  11:00 – 16:00 BST
• NA – Thursday 13th October 2022  02:00 – 07:00 BST
• EMEA  – Tuesday 18th October 2022  18:00 – 00:00 BST

Impact during the maintenance windows stated above:

• The RME application, including RME APIs, will be unavailable during the downtime.
• Due to the risk to import data integrity, please refrain from using the RME Import API POST endpoints in the 24 hours prior to the migration window stated

This includes the following commonly-used RME Import API POST endpoints:

• POST/ingredients
• POST/ingredientintolerance
• POST/ingredientnutrient
• POST/ingredientpriceband

21 September 2022 — New Custom Field and CO2 endpoints

POST Custom Field endpoint for ingredients

Custom fields provide customers with a wider range of options when classifying ingredients that’s specific to their needs.

The POST /ingredientcustomfields endpoint enables you to manage custom fields for ingredients.

Example request body

[
  {
   "StarChefKey": "0030702",
   "SupplierName": "Dairy",
   "SupplierCode": "B365",
   "CustomFieldName": "Farming_Method",
   "CustomFieldValue": "Mixed_Organic_and_Non-Organic"
  }
]

To find out how to integrate with this endpoint, please read:

• Custom Fields section in the API Guide
• API Reference

Ingredient CO2 endpoints

We now provide a GET and POST request for managing CO2 data for ingredients.

The meaning and use of CO2 values is defined by the customer. During integration, partners should ensure they discuss with the customer how they are using these values.

Example GET request

[
  {
    "StarChefKey": "0030702",
    "IngredientGuid": "2B05F7E8-D60E-4949-916F-389BC3CEA56B",
    "IngredientName": "Fresh Orange",
    "IngredientCO2Value": "55.5"
  }
]

Example POST request

[
  {
    "IngredientCO2Value": "55.5",
    "SupplierName": "Dairy",
    "SupplierCode": "B365",
    "StarChefKey": "0030702"
  }
]

To find out how to integrate with this endpoint, please read:

• API Reference: GET ingredient CO2 endpoint
• API Reference: POST ingredient CO2 endpoint

Recipe CO2 endpoints

We now provide a GET and POST request for managing CO2 data for recipes. Recipes can have both a CO2 value and a CO2 rating.

The meaning and use of CO2 values is defined by the customer. During integration, partners should ensure they discuss with the customer how they are using these values.

Example GET request

[
  {
    "RecipeStarChefKey": "0030702",
    "RecipeGuid": "6c3fec7d-97c9-48f8-b84e-13bb179b9fa6",
    "RecipeName": "Roast Lamb Salad",
    "RecipeCO2Value": "55.5",
    "RecipeCO2Ranking": "Free text"
  }
]

Example POST request

[
  {
    "RecipeStarChefKey": "0030702",
    "RecipeCO2Value": "55.5",
    "RecipeCO2Ranking": "Free text"
  }
]

To find out how to integrate with this endpoint, please read:

• API Reference: GET Recipe CO2 endpoint
• API Reference: POST Recipe CO2 endpoint

23 March 2022 — POST /ingredients and POST /ingredientsalternates further refined

The POST /ingredients and POST /ingredientsalternates endpoints have been refined further to support their intended use.

Removed RankOrder from both endpoints

The field RankOrder is no longer supported in requests for either parent or alternate ingredients. If you do include RankOrder in a request, the value for it is ignored.

POST /ingredients

This endpoint can add and update parent ingredients only. New parent ingredients are given the rank order of 1 by default.

POST /ingredientsalternates

This endpoint can add or update alternate ingredients only. When adding a new alternate ingredient, the ingredient is given the next available rank; for example, if there are 4 alternate ingredients already, the new one will have the rank 5. When updating an existing alternate ingredient, the rank will remain the same.

POST /ingredients includes ParentIngredientProductName field

The POST /ingredients endpoint now includes the following field:

• ParentIngredientProductName

This is the name shown on the Supply Details screen for an ingredient. If no value is provided, then the value of the IngredientName field is used, with the text "Copy of " added. For example, if the IngredientName is set to Orange, then the value created is:

• Copy of Orange

See the API Reference for the full request fields.

POST /ingredientsalternates logic refined

When adding or updating an alternate ingredient, the following logic now applies.

Adding alternate ingredients

To add a new alternate ingredient to a parent ingredient, you must include either ParentStarChefKey OR ParentSupplierName and ParentSupplierCode:

• If the request includes a ParentStarChefKey, then we use this to identify the parent ingredient. If the ingredient isn’t found, then we generate an error. The values for ParentSupplierName and ParentSupplierCode are completely ignored.
• If the request does not include a ParentStarChefKey, then we use the ParentSupplierName and ParentSupplierCode to check whether there is a matching ingredient record. If the ingredient isn't found, then we generate an error.
• The request for the new alternate ingredient must include a SupplierName and SupplierCode for the ingredient. If the combination of these match an existing alternate ingredient, then we generate an error.

Updating alternate ingredients

To update an existing alternate ingredient, do not include ParentStarChefKey OR ParentSupplierName and ParentSupplierCode.

• If the request includes a StarChefKey, then we use this to identify the alternate ingredient. If the ingredient isn’t found, then we generate an error. The values for SupplierName and SupplierCode are not used for matching the ingredient. Instead:
  • If these have values, we update the record with the new values.
  • If the values are null, then we keep the existing values, as these fields must always have a value.
• If the request does not include a StarChefKey, then we use the SupplierName and SupplierCode to check whether there is a matching ingredient record. If the ingredient isn't found, then we generate an error.

See the API Reference for the full request fields.

12 January 2022 — POST /ingredients no longer accepts alternate ingredients

The POST /ingredients endpoint now only supports adding or updating a standalone or parent ingredients.

As part of this change, the following fields were removed from the request body:

• ParentIngredientProductName
• ParentSupplierName
• ParentSupplierCode
• ParentStarChefKey

For an up-to-date example of this request please see add or update ingredients in the API reference.

To add or update an alternate ingredient, you must use the POST /ingredientsalternates endpoint.

23 November 2021 — Additional properties added to new alternate ingredients endpoints

Additional properties have been added to the response of the recently released GET request:

• GET /ingredientsalternates

The new properties are:

• ParentIngredientGuid — Use this to link the data to other exports, including in the RME Exports API.
• ParentIngredientProductName — Use this to relate the alternate ingredient to the parent ingredient.
• IngredientGuid — Use this to relate the data to the GET /recipes response
• IngredientSets and its child Set.

Example response (partial)

[
  {
    "ParentIngredientGUID": "33f996a6-c338-4258-8dec-b1814709d2a6",
    "ParentIngredientProductName": "Brandy",
    "IngredientGuid": "e9ad7f40-15a3-461f-8b03-b91950e5eacd",
    "IngredientSets": {
      "Set": [
        "Set 1"
    ]
  },
    "ParentSupplierName": "Dave's Fancy Booze",
    "ParentSupplierCode": "123456",
    "ParentStarChefKey": "14842",
    "RankOrder": "1",
    "IngredientName": "Chapel Down Brandy",
    "InternalCode": "",
    "SupplyQuantityNumber": "1.0000",
    "SupplyQuantity": "1.0000",
    "SupplyQuantityUnit": "bottle",
...

Note that the rest of response is truncated — see the API reference for full details for this endpoint.

28 July 2021 — New endpoints for alternate ingredients; and additional validation for ingredient endpoints

New endpoints for managing alternate ingredients

Two new endpoints are available for managing alternate ingredients:

• GET /ingredientsalternates
• POST /ingredientsalternates

These endpoints are intended to permanently replace the GET and POST /ingredients endpoint for managing alternate ingredients. This will make your managing ingredient requests simpler, as you will be able to send through just the relevant data to update either a parent or alternate ingredient.  

Warning: After the 1st of February 2022, the POST and GET /ingredients endpoint will stop supporting alternate ingredients. If you are using the POST /ingredients endpoint, you will need to update your integration to reflect this change.

Parent ingredients will continue to be managed via the GET and POST /ingredients requests.

Please see the API reference for integration details.

Additional validation for ingredient endpoints

Additional validation now exists that prevents an ingredient in the “Approval” workflow from being updated by the API.

The endpoints this applies to are:

• POST /ingredients
• POST /ingredientintolerance
• POST /ingredientcategory
• POST /ingredientnutrient
• POST /ingredientpriceband
• POST /ingredientconversion      

If you attempt to update an ingredient that is in the approval workflow via these endpoints, Fourth now returns an error message.

18 May 2021 — New shelf life endpoints, updates for Natasha's Law, and additional validation for UoMs

Update to access rights for Natasha’s Law ingredient list endpoints

These endpoints are accessible only if the customer has the full ingredient list functionality enabled for their organisation:

• POST /ingredientlist
• GET /ingredientlist
• GET /recipeingredientlist

To enable this functionality, customers must contact the Fourth team. If it is not enabled, then requests receive a 403 response.

New ReadyForUse field for ingredient lists

A new field, ReadyForUse is now required in the request body for the Update Ingredient List endpoint:

• POST /ingredientlist

Possible values are:

• yes — the ingredient's Ingredient List is ready for use in recipe Ingredient Lists. This means the ingredient's Ingredient List is included in the combined ingredient list of any recipes that it is in.
• no — the ingredient's Ingredient List is not ready for use in recipe Ingredient Lists. Any recipe that includes this ingredient will not have an auto-calculated ingredient list.

Example request body

[
   {
      "StarchefKey": "3422",
      "SupplierName": "Grocer",
      "SupplierCode": "N101",
      "FullIngredientList": "Orange Juice, Vitamin C, Calcium",
      "LabelDescription": "Fortified Orange Juice",
      "ReadyForUse": "yes"
   }
]

The same field is now returned in the GET request for the endpoint:

• GET /ingredientlist

Example response body

[
   {
      "IngredientName": "Calcium Plus Vitamin D (No Pulp) Orange Juice",
      "StarchefKey": "3422",
      "ParentGuid": "ce769cd4-c84a-4144-84f4-4ac912646152",
      "AlternateGuid": "aa869cd4-c84a-4144-84f4-4ac912646152",
      "FullIngredientList": "Orange Juice, Vitamin C, Calcium",
      "LabelDescription": "Fortified Orange Juice",
      "ReadyForUse": "yes"
   }
]

New Ingredient Shelf Life endpoint

A new endpoint with POST and GET methods is available for managing the shelf life of ingredients:

• POST /ingredientshelflife
• GET /ingredientshelflife

You will need to talk to your customer about their Fourth settings when integrating with this endpoint. Customers can tailor the six shelf life fields in Fourth for their own use (normally done during the Fourth implementation stage). Therefore, the names that customers use for the fields may not match the ones in the API request. For example, ShelfLifeTwo may be named “Maximum shelf life from freezer” in the UI. Most customers only use a few of the shelf life fields.

As well, each customer can have a global setting for the minimum and maximum accepted shelf life for items. When Fourth receives a POST /ingredientshelflife request, we check that the values sent are within the customer’s limits. If one or more of the values is outside a limit, Fourth returns an error message in the format:

The value should be between [min - max] value.

The POST /ingredientshelflife method lets you both add or update shelf life values. To update an existing record, either include its StarChefKey or the original SupplierName and SupplierCode.

Unlike the other POST requests for this API, you can choose to update ONLY the shelf life fields that are relevant. Any fields you don’t include in the request retain their current value.

You cannot send through a null value. However, 0 is an accepted value — you should discuss with your customer what this value would mean for them.

Example POST /ingredientshelflife request body

This example shows all the possible shelf life fields.

[
   {
      "ShelfLife": "12", 
      "ShelfLifeTwo": "2",
      "ShelfLifeThree": "0",
      "ShelfLifeFour": "0",
      "MinShelfLifeIntoUnit": "0",
      "MinShelfLifeDays": "0",
      "SupplierName": "Dairy",
      "SupplierCode": "B365",
      "StarChefKey": "0030702"
   }
]

The GET /ingredientShelfLife method returns the shelf life values for an ingredient. This can include empty strings, as most customers do not use all the shelf life fields.

You can filter these requests by ingredient productId, guid, and groupGuid.

Example GET /ingredientShelfLife response body

[
   {
      "ShelfLife": "7",
      "ShelfLifeTwo": "3",
      "ShelfLifeThree": "",
      "ShelfLifeFour": "",
      "MinShelfLifeIntoUnit": "",
      "MinShelfLifeDays": "",
      "SupplierName": "The Farm",
      "SupplierCode": "C132",
      "StarChefKey": "0031291"
   }
]

For more information about integrating, see the API Reference:

• POST /ingredientshelflife
• GET /ingredientshelflife

Additional validation added for ingredient Unit of Measure fields

This update includes additional validation for the POST /ingredients Unit of Measure (UoM) fields.

This update supports our customers who use the Fourth Inventory system for stock management. It ensures that the supplied product UoM and the stock-taking UoM use the same types of unit.

There are three sets of fields in the Ingredients endpoint that relate to the unit size and type:

• Supply fields: the details of the supplied product. E.g. SupplyQuantity and SupplyQuantityUnit.
• Invoice fields: the details of a supplied product as invoiced. E.g. invoiceUom.
• Unit fields: the details used in Inventory for stocktake. E.g. UnitSizeNumber, and UnitSizeUom.

Catch weight ingredients

For catch weight ingredients, the UoMs of the Invoice and Unit must now match. For example:

   "UnitSizeUom": "KG",
   "InvoiceUom": "KGM",
   ...

Note that the only valid UoMs for catch weight products are KG (KGM) or LB.

All other ingredients

For all other ingredients, the UoMs of the Supply and Unit must logically match. This means that if an ingredient's UnitSizeUom is:

• A weight, the SupplyQuantityUnit must also be a weight.
• A volume, the SupplyQuantityUnit must also be a volume.
• Other, the SupplyQuantityUnit must be the same value; e.g. each, slice or bottle.

Volume example

   ...
   "SupplyQuantity": "12", 
   "SupplyQuantityNumber": "150",  
   "SupplyQuantityUnit": "millilitre",
   "SupplyQuantityDescriptor": "Carton",
   ...
   "UnitSizeNumber": "15",  
   "UnitSizeUom": "centilitre",  
   "UnitSizeUomDescriptor": "Can",
   ...

Settings that restrict access to updating UoMs

There are two global settings in Fourth that can stop you from updating UoM values via the API. These are:

• Supply Quantity read-only for Live Ingredients — when enabled, you cannot update these supply fields for an ingredient: SupplyQuantityNumber, SupplyQuantity, and SupplyQuantityUnit.
• Unit Size read-only for Live Ingredients —  when enabled, you cannot update the values for these fields: UnitSizeNumber, and UnitSizeUom.

To enable or disable this functionality, customers must contact the Fourth team.

7th April 2021 — New endpoints supporting Natasha’s Law

The Food Information (Amendment) (England) Regulations 2019, also known as Natasha’s Law, requires food businesses to label all food that is ‘pre-packaged for direct sale’ with the complete ingredient and allergen details.

To support this legislation, each ingredient and recipe in Fourth now has a field that holds full sub-ingredient data. This data can come from two sources: manually keyed in by our customers, or via our APIs from a partner or supplier. The field is called an Ingredient List. Partners can view and update data in ingredient lists using the following new endpoints:

• GET /ingredientlist — Gets the ingredient lists for ingredients. This retrieves the current value of the ingredient list for an ingredient, and any supporting data that you need to supply when updating an ingredient list.
• POST /ingredientlist — Updates an ingredient’s ingredient lists. Use this to replace the current ingredient list with a new list.
• GET /recipeingredientlist — Gets the ingredient list for a recipe. This retrieves the current value of a recipe’s ingredient list.

The Import API Guide contains a section called Support for Natasha’s Law, which explains how to use these endpoints and how they interact with the settings available to users in the Fourth user interface. Please ensure that you read this, as well as the Import API reference, when integrating with these endpoints. 

Additionally, to support the creation of consumer-friendly labels, there are these additional new endpoints:

• POST /recipenames — Add or update recipe names. This endpoint lets you add a recipe name that is label and consumer-friendly.
• GET /recipenames — Gets the recipe names. This retrieves the recipe names, and any supporting data that you need to supply when updating recipe names.

The Recipe & Menu Engineering Export API also includes endpoints related to Natasha’s Law. These endpoints allow you to audit a recipe or ingredient's ingredient list history. You can find out about these endpoints in the Export API Guide.

For more information about Natasha's Law:

• Visit help.fourth.com and search for "Natasha's Law" for articles published by us.
• View the Food Standards Agency's technical guidance on their website.
• View the Legislation online.

7th April 2021 — Update to alternate ingredients conversion UoMs

Now, when an alternate ingredient is created, its pack size (supply quantity) can be defined using the parent ingredient base Unit of Measure (UoM) or any of the parent ingredient conversion UoMs.

This update means that GET requests that return supply pack size (or supply quantity values) may now return values that are a conversion UoM of the parent ingredient. And, you can use these conversion rates when creating or updating an alternate ingredient using a POST /ingredients request.

For further information about how conversion values work, please see the customer release note.

17 November 2020 — New Delete Alternate Ingredients endpoint

A new endpoint is available that lets you delete an alternate ingredient. This removes the alternate’s details from the parent ingredient with any information that is owned by the parent ingredient remaining the same.

Parent ingredients cannot be deleted via this endpoint, and you cannot delete an alternate ingredient that is currently in use in a recipe.

The endpoint is:

• [ROOT]/deletealternates

The request includes a body with the details of the ingredient you wish to delete. You can choose to identify the ingredient using either its StarChefKey or the SupplierName and SupplierCode. If you use StarChefKey, the other two fields are ignored.

Request body example

[
   {
        "StarChefKey": "22",
        "SupplierName": "Grocer",
        "SuppplierCode": "N101"
    }
]

For more information on this endpoint, see the API reference.

29 September 2020

Manual approval step available for intolerance values

Please note that customers can now choose to manually review and approve any intolerance values updated via the API.

This does not have any impact on the behavior of the API itself.

New recipeidentifiers endpoint

The new GET recipeIdentifiers endpoint lets you retrieve just the identifiers for recipes. This will particular benefit API users who retrieve large data sets.

The filters available for the endpoint are:

• lastModifiedAfter
• lastModifiedNutrientsAfter
• lastModifiedIntolerancesAfter

Sample response

{
   "RecipeName": "Seasoning Salt & Pepper",
   "StarChefKey": 358,
   "RecipeGuid": "F4F29170-2344-4B20-A0AE-534EB34C4FB7",
   "DateLastUpdated": "2021-02-16T09:18:49"
}

For further information on this endpoint, please see the API reference.

Additional field in POST ingredients endpoint

The POST /ingredient endpoint now includes a new request body field: ParentIngredientProductName.

The value is optional. However, if you are updating an ingredient, please remember that if you leave this field blank, this will remove any existing value for the field.

Example request body (truncated)

[
  {
    "IngredientName": "Orange",
    "IngredientGuid": "5FD5ED46-C254-4002-9EF4-6513C623CD0D",
    "ParentIngredientProductName": "Fresh Orange",
    "SupplierName": "Beetniks Beets and Beverages",
    "SupplierCode": "B112",
    "StarChefKey": "0231703",
    …
    }
]

26 August 2020 — New endpoints for ingredient costs and price bands

Two new endpoints have been introduced to GET ingredient costs and price bands.

Ingredient costs

The new endpoint is:

• GET [ROOT]/ingredientcosts

By default, this returns details for all ingredients. You can filter the response using query parameters:

• lastModifiedAfter — Returns only records modified on or after the date. Use the format: yyyy-mm-dd
• groupGuid — The logical business group within Recipe & Menu Engineering.
• productId — The StarChefKey for an ingredient
• GUID — The IngredientGuid for an ingredient
• setType — The ingredient set type, if these are in use. Options are: Blank, Trial, Archive, and Live.

This returns the existing and pending price details for an ingredient. If there is no value for a price it will be set to 0.00; for a date it will be set to null. For example:

[
  {
    "SupplierName": "The Vegan Butcher",
    "SupplierCode": "12A4D63C",
    "StarChefKey": 213,
    "ProductGUID": "a429bf60-bd54-4b82-8e28-151c4d94a1fb",
    "IngredientCostPrice": "13.99",
    "PendingIngredientCostPrice": "25.00",
    "PendingCostEffectiveDate": "8/21/2020 12:00:00 AM",
    "InvoicePrice": "0.00",
    "PendingInvoicePrice": "0.00",
    "PendingInvoicePriceEffectiveDate": null
  }
]

For more information on this endpoint, please see the API guide and reference.

Ingredients price bands

The new endpoint is:

• GET [ROOT]/ingredientspricebands

By default, this returns details for all ingredients. You can filter the response using query parameters:

• lastModifiedAfter — Returns only records modified on or after the date. Use the format: yyyy-mm-dd
• groupGuid — The business group within Recipe & Menu Engineering.

This returns the price bands for ingredients.

[
  {
    "StarChefKey": 0036858,
    "ProductGUID": "00000000-0000-0000-0000-000000000000",
    "SupplierName": "Dairy",
    "SupplierCode": "B365",
    "PriceBandName": "Default",
    "OverridePrice": "12.14",
    "SupplierAccountCode": "21323"
  }
]

For more information on this endpoint, please see the API guide and reference.

26 August 2020 — New batch endpoint for checking request processing

For successfully submitted POST requests, Fourth returns a status in the synchronous response body. For example:

{
  "Status": "Processed;Aug 10 2020 8:32AM",
  "BatchId": "2345"
}

The two possible states are Processed (with a timestamp) and Not processed. To check the processing status later, you can now use the /batches endpoint:

• [ROOT]/api/ingredientandaccessimport/batches

You can filter the response by individual request; for example:

• [ROOT]/api/ingredientandaccessimport/batches?batchId=3722

Or filter by the number of results want returned (from 1 to 100). For example, this returns the last processing status of the last two requests made:

• [ROOT]/api/ingredientandaccessimport/batches?batchSize=2

Sample response:

[
  {
    "Status": "Not processed",
    "BatchId": 3724
  },
{
    "Status": "Processed;Aug 28 2020  8:32AM",
    "BatchId": 3722
  }
]

26 August 2020 — New Units of Measure

New Units of Measure

Fourteen new standard RME UoMs (units of measure) have been created. These UoMs are compatible for use with the Inventory application.