diff options
author | Ezhilarasi <ezhrajam@in.ibm.com> | 2019-07-05 13:41:38 +0530 |
---|---|---|
committer | Ezhilarasi <ezhrajam@in.ibm.com> | 2019-07-05 13:41:48 +0530 |
commit | 7349dfe98f0bb61843fb6e1a6dc57e194d792ca1 (patch) | |
tree | 10b9f7fb677f3a3059d8bf7082b8acf6c015170b /docs/dynamicapi.rst | |
parent | a6fae85764a8dfbeba6000a060b8be0f21fb0466 (diff) |
Created microservice folder
Change-Id: I89fd0da33dbaa1704ba93d2ca7ab2f29c4493935
Issue-ID: CCSDK-1453
Signed-off-by: Ezhilarasi <ezhrajam@in.ibm.com>
Diffstat (limited to 'docs/dynamicapi.rst')
-rw-r--r-- | docs/dynamicapi.rst | 24 |
1 files changed, 0 insertions, 24 deletions
diff --git a/docs/dynamicapi.rst b/docs/dynamicapi.rst deleted file mode 100644 index eaf9987b7..000000000 --- a/docs/dynamicapi.rst +++ /dev/null @@ -1,24 +0,0 @@ -.. This work is licensed under a Creative Commons Attribution 4.0 International License. -.. http://creativecommons.org/licenses/by/4.0 -.. Copyright (C) 2019 IBM. - -Dynamic API ------------ - -The nature of the API request and response is meant to be model driven and dynamic. They both share the same definition. - -The actionName, under the actionIdentifiers refers to the name of a Workflow (see workflow) - -The content of the payload is what is fully dynamic / model driven. - -The first top level element will always be either $actionName-request for a request or $actionName-response for a response. - -Then the content within this element is fully based on the workflow input and output. - -Here is how the a generic request and response look like. - -|image0| - -.. |image0| image:: media/dynamicapi.jpg - :height: 4.43750in - :width: 7.88889in
\ No newline at end of file |