Initial Add

Author: Ergin008

DocuSign-Extensions.md

@@ -0,0 +1,70 @@
+# DocuSign Vendor specific Extensions
+
+The Swagger and OpenAPI specifications enable vendor specific extensions throughout Swagger files. 
+The extensions must start with the letter x. All DocuSign extensions start with `x-ds-`.
+
+## Categories, Resources, Methods
+The OpenAPI specification does not focus on the idea of resources for APIs. 
+In particular, the OpenAPI `tags` element can be used to add multiple tags to a method.
+
+DocuSign assigns each method to exactly one **resource**. Resources are usually plural nouns. 
+They start with a capital letter.
+
+Methods are verbs. They are lower case.
+
+Resources are grouped together into "categories." Within the documentation, a three level table of contents is used:
+Categories, Resources, Methods.
+
+### Categories
+Categories are listed in the top level `x-ds-categories` element. It is an array of Category objects. 
+Each object includes parameters:
+
+* `name` -- markdown format
+* `description` -- markdown format
+* `summary` -- markdown format
+
+### Resources
+Within the OpenAPI file, a method's resource name is stored in location `tags[0]` within the method's operation definition. 
+Only one element of the `tags` array is used.
+
+The top level `tags` array holds the extended descriptions of the resources in markdown format.
+
+Each resource name exactly matchs a definition name. The resource (and definition) names start with a capital letter.
+
+The `description` field in the matching definition entry for the resource holds the resource's summary description, 
+also in markdown format.
+
+Definitions that are also resources include the following extensions:
+
+* `x-ds-category` -- the name of the definition's (and resource's) owning category. 
+  The value will match a `name` value in the `x-ds-categories` array.
+* `x-ds-definition-name` -- the name of the definition as used for generating SDKs
+* `x-ds-order` -- an integer for ordering Resources with a Category table of contents entry. Not used.
+* `x-ms-summary` -- Not used.
+
+## Methods
+The heart of an API specification are the methods.
+
+A Method's Resource name is stored in `tags[0]`
+
+Important parameters for each method:
+
+* `description` -- markdown format.
+* `operationId` -- unique throughout the Swagger file.
+* `summary` -- markdown format.
+* `x-ds-in-sdk` -- is the method included in the SDK? Not used.
+* `x-ds-method` -- the method name within the resource's scope. This is the method name used in the API documentation.
+* `x-ds-methodname` -- the method name within the category's scope. This method name is used in the SDKs.
+* `x-ds-service` -- the owning category for the method.
+
+### Common method names
+
+Most resources include one or more common methods:
+
+| Method name | HTTP method | Description |
+| --- | --- | --- |
+| create | POST | creates a new resource instance |
+| get	| GET	| get a single instance of the resource |
+| list | GET	| list current resources |
+| delete | DELETE | delete a resource |
+| update | PUT | update a resource |

LICENSE

@@ -0,0 +1,22 @@
+The MIT License
+
+Copyright (c) 2016- DocuSign, Inc. (https://www.docusign.com)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+

OpenAPI.png

@@ -0,0 +1,29 @@
+![alt text](OpenAPI.png)
+
+# DocuSign OpenAPI Specifications  
+
+DocuSign uses the OpenAPI (OAI) Specification - formerly known as "Swagger" - to describe its REST APIs. The goal of the OAI specification is to define a standard, language-agnostic interface to REST APIs which allows both humans and computers to discover and understand the capabilities of the service.  For more info see the official [OAI](https://github.com/OAI/OpenAPI-Specification) spec.
+
+## The Swagger file
+
+`esignature.rest.swagger.json` - the full swagger file for DocuSign's eSignature REST API 
+
+## What can I do with a Swagger file? 
+
+We use OpenAPI/Swagger files to build many of our developer tools including our [client SDKs](https://www.docusign.com/developer-center/api-overview#sdk-docusign-supported) using `swagger-codegen`. We also use the OAI specification to build our [API Docs](https://docs.docusign.com/esign/) and [API Explorer](https://apiexplorer.docusign.com/#/) tools.  What will you build?  Let us know by filing an issue in this repository.
+
+### Vendor-specific extensions
+
+Some post-processing is performed on our eSignature Swagger spec which includes adding a number of vendor-specific extensions prefixed with `x-ds-`. See the [DocuSign-Extensions.md](DocuSign-Extensions.md) file for more information.
+
+### Releases
+
+The DocuSign eSignature REST API is updated monthly. The Swagger file in this repository is also updated monthly. See the "Releases" tab for version information. The current release information is available from the [demo/developer sandbox](https://demo.docusign.net/restapi/service_information) and [production](https://www.docusign.net/restapi/service_information) platforms.
+
+## Support
+
+Please log issues through GitHub. We also have an active developer community on Stack Overflow, search the [DocuSignAPI](http://stackoverflow.com/questions/tagged/docusignapi) tag.
+
+## License
+
+The DocuSign OpenAPI (Swagger) Files are licensed under the following [License](LICENSE).