From 7349dfe98f0bb61843fb6e1a6dc57e194d792ca1 Mon Sep 17 00:00:00 2001 From: Ezhilarasi Date: Fri, 5 Jul 2019 13:41:38 +0530 Subject: Created microservice folder Change-Id: I89fd0da33dbaa1704ba93d2ca7ab2f29c4493935 Issue-ID: CCSDK-1453 Signed-off-by: Ezhilarasi --- docs/microservices/dynamicapi.rst | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 docs/microservices/dynamicapi.rst (limited to 'docs/microservices/dynamicapi.rst') diff --git a/docs/microservices/dynamicapi.rst b/docs/microservices/dynamicapi.rst new file mode 100644 index 000000000..eaf9987b7 --- /dev/null +++ b/docs/microservices/dynamicapi.rst @@ -0,0 +1,24 @@ +.. 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 -- cgit 1.2.3-korg