Initial client.

.gitignore

@@ -0,0 +1,64 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+env/
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+*.egg-info/
+.installed.cfg
+*.egg
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*,cover
+.hypothesis/
+venv/
+.python-version
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+#Ipython Notebook
+.ipynb_checkpoints

README.md

@@ -0,0 +1,141 @@
+# banking-client
+
+- API version: 0.1.0
+- Package version: 1.0.0
+- Build package: io.swagger.codegen.languages.PythonClientCodegen
+
+## Requirements.
+
+Python 2.7 and 3.4+
+
+## Installation & Usage
+### pip install
+
+If the python package is hosted on Github, you can install directly from Github
+
+```sh
+pip install git+https://github.com/narmitech/banking-client-python.git
+```
+(you may need to run `pip` with root permission: `sudo pip install git+https://github.com/narmitech/banking-client-python.git`)
+
+Then import the package:
+```python
+import banking_client
+```
+
+### Setuptools
+
+Install via [Setuptools](http://pypi.python.org/pypi/setuptools).
+
+```sh
+python setup.py install --user
+```
+(or `sudo python setup.py install` to install the package for all users)
+
+Then import the package:
+```python
+import banking_client
+```
+
+## Getting Started
+
+Please follow the [installation procedure](#installation--usage) and then run the following:
+
+```python
+from __future__ import print_function
+import time
+import banking_client
+from banking_client.api_client import ApiClient
+from banking_client.configuration import Configuration
+from banking_client.rest import ApiException
+from pprint import pprint
+
+config = Configuration()
+config.host = 'https://api.demo.narmitech.com/v1'
+config.access_token = 'YOUR_ACCESS_TOKEN'
+config.secret = 'YOUR_SECRET'
+api_instance = banking_client.AccountApi(api_client=ApiClient(configuration=config))
+api_instance.list()
+
+try:
+    # Get account
+    api_response = api_instance.list()
+    pprint(api_response)
+except ApiException as e:
+    print("Exception when calling AccountApi->get: %s\n" % e)
+
+```
+
+## Documentation for API Endpoints
+
+All URIs are relative to *https://api.example.com/v1*
+
+Class | Method | HTTP request | Description
+------------ | ------------- | ------------- | -------------
+*AccountApi* | [**get**](docs/AccountApi.md#get) | **GET** /accounts/{accountId} | Get account
+*AccountApi* | [**get_account_balances**](docs/AccountApi.md#get_account_balances) | **GET** /account_balances/{accountBalancesId} | Get account balances for an account
+*AccountApi* | [**list**](docs/AccountApi.md#list) | **GET** /accounts | List accounts
+*AccountApi* | [**list_account_balances**](docs/AccountApi.md#list_account_balances) | **GET** /account_balances | List account balances
+*AccountApi* | [**update**](docs/AccountApi.md#update) | **PUT** /accounts/{accountId} | Update account
+*GeneralApi* | [**list_ping**](docs/GeneralApi.md#list_ping) | **GET** /ping | Server heartbeat operation
+*SubscriptionApi* | [**create**](docs/SubscriptionApi.md#create) | **POST** /subscriptions | Create subscription
+*SubscriptionApi* | [**destroy**](docs/SubscriptionApi.md#destroy) | **DELETE** /subscriptions/{subscriptionId} | Delete subscription
+*SubscriptionApi* | [**get**](docs/SubscriptionApi.md#get) | **GET** /subscriptions/{subscriptionId} | Get subscription
+*SubscriptionApi* | [**list**](docs/SubscriptionApi.md#list) | **GET** /subscriptions | List subscriptions
+*SubscriptionApi* | [**update**](docs/SubscriptionApi.md#update) | **PUT** /subscriptions/{subscriptionId} | Update subscription
+*TransactionApi* | [**get**](docs/TransactionApi.md#get) | **GET** /transactions/{transactionId} | Get transaction
+*TransactionApi* | [**list**](docs/TransactionApi.md#list) | **GET** /transactions | List transactions
+*TransactionApi* | [**list_transactions**](docs/TransactionApi.md#list_transactions) | **GET** /accounts/{accountId}/transactions | List transactions for an account
+*TransactionApi* | [**update**](docs/TransactionApi.md#update) | **PUT** /transactions/{transactionId} | Update transaction
+*TransferApi* | [**create**](docs/TransferApi.md#create) | **POST** /transfers | Create a transfer
+*UserApi* | [**get**](docs/UserApi.md#get) | **GET** /users/{userId} | Get user
+*UserApi* | [**list**](docs/UserApi.md#list) | **GET** /users | List users
+
+
+## Documentation For Models
+
+ - [Account](docs/Account.md)
+ - [AccountBalances](docs/AccountBalances.md)
+ - [Address](docs/Address.md)
+ - [Check](docs/Check.md)
+ - [Document](docs/Document.md)
+ - [Error](docs/Error.md)
+ - [InlineResponse200](docs/InlineResponse200.md)
+ - [InlineResponse2001](docs/InlineResponse2001.md)
+ - [InlineResponse2002](docs/InlineResponse2002.md)
+ - [InlineResponse2003](docs/InlineResponse2003.md)
+ - [InlineResponse2004](docs/InlineResponse2004.md)
+ - [InlineResponse2005](docs/InlineResponse2005.md)
+ - [InlineResponse2006](docs/InlineResponse2006.md)
+ - [InlineResponse2007](docs/InlineResponse2007.md)
+ - [InlineResponse2008](docs/InlineResponse2008.md)
+ - [InlineResponse201](docs/InlineResponse201.md)
+ - [Links](docs/Links.md)
+ - [Location](docs/Location.md)
+ - [Membership](docs/Membership.md)
+ - [Meta](docs/Meta.md)
+ - [Phone](docs/Phone.md)
+ - [Subscription](docs/Subscription.md)
+ - [Transaction](docs/Transaction.md)
+ - [Transfer](docs/Transfer.md)
+ - [User](docs/User.md)
+
+
+## Documentation For Authorization
+
+
+## Application
+
+- **Type**: OAuth
+- **Flow**: application
+- **Authorization URL**:
+- **Scopes**:
+ - **write**: allows reading and modifying resources
+ - **read**: allows reading resources
+ - **read:profile**: allows reading extended information about the user including address
+
+
+## Author
+
+contact@narmitech.com
+

banking_client/__init__.py

@@ -0,0 +1,53 @@
+# coding: utf-8
+
+# flake8: noqa
+
+"""
+    Narmi Banking API
+
+    ## Introduction  This API is organized around REST. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors.  ### Schema  JSON is returned by all API responses, including errors.  All timestamps return in ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ`.  ## Access  All API requests must be made over HTTPS. API requests without authentication will also fail.  Authentication to the API is via bearer authorization, for example using curl this would be `-H \"Authorization: Bearer $SECRET_KEY\"`.  Your API keys carry many privileges, so be sure to keep them secret! Do not share your secret API keys in publicly accessible areas such source code pushed to Github, client-side code, and so forth.  ### Request Signing  Requests to the production API must be signed, this requires use of the secret returned alongside the API token. This is done following [the draft specification on HTTP request signing](https://tools.ietf.org/html/draft-cavage-http-signatures-08).  This is a simple of example of signing only the `Date` header:  ``` token='1234acdefghijk' secret='acdefghijk1234' date=`date -u +'%Y-%m-%dT%H:%M:%SZ'` signature=`echo -n \"date: $date\" | openssl dgst -sha256 -binary -hmac \"$secret\" | base64` curl -H \"Authorization: Bearer $token\" -H \"Date: $date\" -H \"Signature: keyId=\\\"$token\\\",algorithm=\\\"hmac-sha256\\\",headers=\\\"date\\\",signature=\\\"$signature\\\"\" 'https://api.example.com/v1/accounts/' ```  For the production api, the following components of the signature are required:   * (request-target) psuedo header   * `Host` header   * `Date` header   * `Content-Type` header   * `Digest` header containing a digest of SHA-256 digest of the request body   * `Content-Length` header  A full signature header would look like:  ``` Signature: keyId=\"1234acdefghijk\",algorithm=\"hmac-sha256\",headers=\"(request-target),date,host,content-type,digest,content-length\",signature=\"zxywut321asdf\" ```  These signatures increase the security of production data in three ways: verifying the identity of the requester, protecting data in transit, and reducing the window of replay attacks.  Request signatures ensure that the request has been sent by someone with a valid access key and secret - even if the key was seen in transit, the secret should never be exposed and the signature depends on having a valid key and secret.  In addition, this prevents tampering with a request while it's in transit, since some of the request elements are used to calculate a digest of the request, and the resulting hash value is included as part of the request. If the value of the digest calculated by the API doesn't match, the digest in the request the API denies the request.  Finally, because a request must reach the API within five minutes of the timestamp in the request, a request is valid only for those five minutes.  ## Versions and resource stability  When we make backwards-incompatible changes to the API, we release new versions.  All requests will use your account API settings, unless you override the API version.  To set the API version on a specific request, send a `API-Version: '1234567'` header.  ### Stability  Within any given version of the API, any given resource (eg. /foos, /foo or /foos/:id/bars) has a specified level of stability. The stability of a resource is specified in the stability property.  The stability of a resource specifies what changes will be made to the resource and how changes will be communicated. The possible types of changes are detailed below. All changes are communicated in the api changelog.  There are three levels of stability: prototype, development, and production.  #### Prototype  A prototype resource is experimental and major changes are likely. In time, a prototype resource may or may not advance to production.  * Compatible and emergency changes may be made with no advance notice * Disruptive changes may be made with one week notice * Deprecated resources will remain available for at least one month after deprecation  #### Development  A Development resource is a work-in-progress, but major changes should be infrequent. Development resources should advance to production stability in time.  * Compatible and emergency changes may be made with no advance notice * Disruptive changes may be made with one month notice * Deprecated resources will remain available for at least six months after deprecation  #### Production  A production resources is complete and major changes will no longer occur.  * Compatible and emergency changes may be made with no advance notice * Disruptive changes may not occur, instead a new major version is developed * Deprecated resources will remain available for at least twelve months after deprecation  ### Deprecation  Deprecated resources have a deprecated_at date property which is also displayed in the documentation. Deprecated resources will keep working for at least as long after deprecation as mandated by their stability: 1 month for prototype resources, 6 month for development resources and 12 months for production resources. Deprecated resources will not change stability.  Once a resource has been completely deactivated, it will return HTTP 410 for all requests.  ### Types of changes  #### Compatible change  Small in scope and unlikely to break or change semantics of existing methods.  * Add resources, methods and attributes * Change documentation * Change undocumented behavior  #### Disruptive change  May have larger impact and effort will be made to provide migration paths as needed.  * Change semantics of existing methods * Remove resources, methods and attributes  #### Emergency change  May have larger impact, but are unavoidable due to legal compliance, security vulnerabilities or violation of specification.  ## Requests and responses  ### Requests  An endpoint's name indicates the type of data it handles and the action it performs on that data. The most common actions are:  | Action |  HTTP Method | Description | | ------ | ------------ | ----------- | | Create  |  POST |  Creates and persists an entity of the corresponding type. | | List  |  GET |   Returns all instances of a particular entity that match query parameters you provide. | | Retrieve  |  GET |   Returns the single instance of an entity that matches the identifier you provide. | | Update  |  PUT |   Modifies the existing entity that matches the identifier you provide. | | Delete  |  DELETE |  Deletes the existing entity that matches the identifier you provide. Deleted entities cannot be retrieved or undeleted. |  All requests must include a header indicating the format of the resposne to be returned:  ``` Accept: application/json ```  #### Providing parameters  The way you provide parameters to a request depends on the HTTP method of the request.  ##### `GET` and `DELETE`  For GET and DELETE requests, you provide parameters in a query string you append to your request's URL. For example,  ``` /v1/locations/$LOCATION_ID/transactions?sort_order=ASC ```  Values for query parameters must be URL-escaped.  ##### `POST`, `PUT` and `PATCH`  For `POST`, `PUT` and `PATCH` requests, you instead provide parameters as JSON in the body of your request. POST and PUT requests must include one additional header:  ``` Content-Type: application/json ```  And in the body of the request:  ``` {   \"given_name\": \"Amelia\",   \"family_name\": \"Earhart\" } ```  ### Responses  [Conventional HTTP response codes](https://httpstatuses.com/) indicate the success or failure of an API request, not all errors map cleanly onto HTTP response codes, however. In general:  | HTTP Response code | Indication | | ------------------ | ---------- | | 2xx                | success    | | 4xx                | an error that failed given the information provided (e.g., a required parameter was omitted, or the configuration does is invalid, etc.) | | 5xx                | 5xx range indicate an error processing the request |  #### Response bodies  When a request is successful, a response body will typically be sent back in the form of a JSON object and include a `Content-Type: application/json` header. One exception to this is when a DELETE request is processed, which will result in a successful HTTP 204 status and an empty response body.  Inside of this JSON object, the resource root that was the target of the request will be set as the key. This will be the singular form of the word if the request operated on a single object, and the plural form of the word if a collection was processed.  #### Response meta-information  Responses will have a [top level `meta` key](http://jsonapi.org/format/#document-meta) with meta information associated with the request. Common keys include:  | key | description | example | | --- | ----------- | ------- | | deprecated_at | | | | stability | | | | total | used in paginating responses | |  #### Errors  Failing responses will have an appropriate status and a JSON body containing more details about a particular error.  | Name | Type | Description |  Example | | ---- | ---- | ----------- | ---------- | | id |  string |  id of error raised | \"rate_limit\" | | message |   string |  end user message of error raised | \"Your account reached the API limit. Please wait a few minutes before making new requests\" | | url |   string |  reference url with more information about the error  | https://example.com/developer/articles/rate-limits |  ## Pagination  Requests that return multiple items will be paginated to 25 items by default. You can specify subsequent pages with the `page` query parameter. For some resources, you can also set a custom page size up to `100` with the `per_page` parameter. A top level object in the response body named `links` will contain full URLs to access the next and previous pages of the response.  ``` { ... \"links\": {   \"next\": \"https://api.example.com/v1/accounts?page=2\",   \"previous\": \"https://api.example.com/v1/accounts?page=1\" } ... } ```  For endpoints that return resources that have an inherent temporal order (for example transactions, for which one transaction must follow another), cursors are supported. The `before` and `after` query parameters allow cursor like pagination, where the value of each is the id of the resource to continue pagination.  ## Filtering  List (index) endpoints sometimes expose query parameters which allow the responses to be limited to resources matching the given filters.  In the case that an invalid filter value is specified a status code of 404 with a detailed explanation is returned.  ## Working with money  We support different currencies, for resources in all of these currencies, the amount is in the smallest common currency unit - this is the amount in cents (or pence, or similarly named unit). For example, to specify for $1.00 or 1.00, you would set amount=100 (100 cents of the respective currency).  For zero-decimal currencies, we use the regular denomination. For example, a transaction of 1 Yen, you should set amount=1 (1 JPY), since 1 is the smallest currency unit.  ## Request IDs  Each API request has an associated request identifier in the response headers, under Request-Id. You can also find request identifiers in the URLs of individual request logs in your Dashboard. If you need to contact us about a specific request, providing the request identifier will ensure the fastest possible resolution.   # noqa: E501
+
+    OpenAPI spec version: 0.1.0
+    Contact: contact@narmitech.com
+"""
+
+
+from __future__ import absolute_import
+
+# import apis into sdk package
+from banking_client.api.account_api import AccountApi
+from banking_client.api.general_api import GeneralApi
+from banking_client.api.subscription_api import SubscriptionApi
+from banking_client.api.transaction_api import TransactionApi
+from banking_client.api.transfer_api import TransferApi
+from banking_client.api.user_api import UserApi
+
+# import ApiClient
+from banking_client.api_client import ApiClient
+from banking_client.configuration import Configuration
+# import models into sdk package
+from banking_client.models.account import Account
+from banking_client.models.account_balances import AccountBalances
+from banking_client.models.address import Address
+from banking_client.models.check import Check
+from banking_client.models.document import Document
+from banking_client.models.error import Error
+from banking_client.models.inline_response_200 import InlineResponse200
+from banking_client.models.inline_response_200_1 import InlineResponse2001
+from banking_client.models.inline_response_200_2 import InlineResponse2002
+from banking_client.models.inline_response_200_3 import InlineResponse2003
+from banking_client.models.inline_response_200_4 import InlineResponse2004
+from banking_client.models.inline_response_200_5 import InlineResponse2005
+from banking_client.models.inline_response_200_6 import InlineResponse2006
+from banking_client.models.inline_response_200_7 import InlineResponse2007
+from banking_client.models.inline_response_200_8 import InlineResponse2008
+from banking_client.models.inline_response_201 import InlineResponse201
+from banking_client.models.links import Links
+from banking_client.models.location import Location
+from banking_client.models.membership import Membership
+from banking_client.models.meta import Meta
+from banking_client.models.phone import Phone
+from banking_client.models.subscription import Subscription
+from banking_client.models.transaction import Transaction
+from banking_client.models.transfer import Transfer
+from banking_client.models.user import User

banking_client/api/__init__.py

@@ -0,0 +1,11 @@
+from __future__ import absolute_import
+
+# flake8: noqa
+
+# import apis into api package
+from banking_client.api.account_api import AccountApi
+from banking_client.api.general_api import GeneralApi
+from banking_client.api.subscription_api import SubscriptionApi
+from banking_client.api.transaction_api import TransactionApi
+from banking_client.api.transfer_api import TransferApi
+from banking_client.api.user_api import UserApi