diff options
author | Dan Timoney <dtimoney@att.com> | 2019-07-08 19:19:57 +0000 |
---|---|---|
committer | Gerrit Code Review <gerrit@onap.org> | 2019-07-08 19:19:57 +0000 |
commit | c7daf1efab55aab027885b0f768a21077c264819 (patch) | |
tree | 4b441c9ae538181bf90f67ffe7f193512d9e3ecb /docs/microservices/dynamicapi.rst | |
parent | 74b35262d799525a979165e0c46872b756372914 (diff) | |
parent | 7349dfe98f0bb61843fb6e1a6dc57e194d792ca1 (diff) |
Merge "Created microservice folder"
Diffstat (limited to 'docs/microservices/dynamicapi.rst')
-rw-r--r-- | docs/microservices/dynamicapi.rst | 24 |
1 files changed, 24 insertions, 0 deletions
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 |