From d184c4b1947ed334964ab95f86ab6f66ec144cf0 Mon Sep 17 00:00:00 2001
From: Wilco Krikke <wilco.krikke@akkerweb.nl>
Date: Fri, 28 May 2021 14:58:47 +0000
Subject: [PATCH] Update 'Blight-API.md'

---
 Blight-API.md | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/Blight-API.md b/Blight-API.md
index 50bd972..a3785de 100644
--- a/Blight-API.md
+++ b/Blight-API.md
@@ -6,11 +6,19 @@ For the currently available public FarmMaps API you can take a look at swagger:
 
 ## API flow
 * Authenticate User
+* Create cropping scheme (if not exists)
+* Create crop field (if not exists)
+* Get blight advice
+* Create blight advice 
+* Update UserInput
+* Add spray
+* Add irrigation
+
+
+
 * Optional steps
     * *Create cropfield through FarmMaps API*
         * Item 'vnd.farmmaps.itemtype.cropfield' must be created with its data as specified in the api.
-        * Task 'vnd.farmmaps.task.workflow' can be executed if needed executed to aggregate all needed data.
-            * This is an asynchronous process and can take a while before all data is collected in FarmMaps.
 
 * Task 'vnd.farmmaps.task.blight' must be executed to create an advice. This task is automatically created for crop fields with potato and is scheduled to run at configered times to keep the advice updated.
 It is also possible to executed this task at any time through the API. This will be explained in the following chapters.