Metadata-Version: 2.1
Name: auto_api
Version: 2.1.0
Summary: Automatic Web API REST
Home-page: https://github.com/fvalverd/AutoApi
Author: Felipe Valverde Campos
Author-email: felipe.valverde.campos@gmail.com
License: MIT license
Download-URL: https://github.com/fvalverd/AutoApi/tarball/v2.1.0
Project-URL: Source, https://github.com/fvalverd/AutoApi
Project-URL: Tracker, https://github.com/fvalverd/AutoApi/issues
Description: # AutoApi
        
        [![PyPI pyversions](https://img.shields.io/pypi/pyversions/auto_api.svg)](https://pypi.org/project/auto-api/)
        [![MIT license](https://img.shields.io/badge/License-MIT-blue.svg)](https://lbesson.mit-license.org/)
        [![PyPI](https://img.shields.io/pypi/v/AutoApi)](https://pypi.org/project/auto-api/)
        [![GitHub tag (latest SemVer)](https://img.shields.io/github/v/tag/fvalverd/AutoApi?sort=semver)](https://github.com/fvalverd/AutoApi/releases)
        [![tests](https://github.com/fvalverd/AutoApi/workflows/tests/badge.svg?branch=master)](https://github.com/fvalverd/AutoApi/actions?query=workflow%3A%22tests%22)
        [![Build Status](https://travis-ci.org/fvalverd/AutoApi.svg?branch=master)](https://travis-ci.org/fvalverd/AutoApi?branch=master)
        [![Coverage Status](https://coveralls.io/repos/github/fvalverd/AutoApi/badge.svg?branch=master)](https://coveralls.io/github/fvalverd/AutoApi?branch=master)
        [![Code Climate](https://codeclimate.com/github/fvalverd/AutoApi/badges/gpa.svg)](https://codeclimate.com/github/fvalverd/AutoApi)
        
        The goal of AutoApi is avoid developing an [API REST](https://en.wikipedia.org/wiki/Representational_state_transfer) at the start of a project, making a prototype easier than usual. AutoApi also has an authentication system and multiple APIs are supported.
        
        ## Quickstart
        
        Assuming you have MongoDB server running in *localhost* on the default port without authentication, AutoApi starts as:
        
        ```shell
        $ workon api
        (api) $ pip install auto_api
        (api) $ autoapi
          * Running on http://localhost:8686/ (Press CTRL+C to quit)
          ...
        ```
        
        A personal agenda is a good example to show how AutoApi works. We will use the *example* API to insert and retrieve items from *agenda* collection.
        
        ### Insert
        To add an item in the agenda, the following HTTP request shows how to do it:
        <pre>
        <b>POST</b> http://localhost:8686/example/agenda
        <b>Content-Type</b>: application/json
        
        {
          "name": "user",
          "email": "user@email.com",
          "phone": "+123 456-789",
          "address": "123 Street"
        }
        </pre>
        It's important to add **/example** (API name) before the REST path **/agenda**, because that is the way AutoApi identifies them.
        The response will contain the id of the created item as:
        ```
        {"id": "591a79400000000000000000"}
        ```
        
        Where the value of *id* will always be a [MongoDB ObjectId](https://docs.mongodb.com/manual/reference/method/ObjectId).
        
        
        ### Retrieve
        To get the previous inserted item in the agenda, is required to know the *id* of the item. The previous response shows the *id* is *591a79400000000000000000*, so the item can be retrieve making the following HTTP request:
        
        <pre>
        <b>GET</b> http://localhost:8686/example/agenda/591a79400000000000000000
        </pre>
        In the same way as the insert operation, the API name and the REST path are required, in this case the path is **/agenda/591a79400000000000000000**. The response will contain the initial inserted data and the AutoApi assigned *id*:
        <pre>
        {
          "id": "591a79400000000000000000",
          "name": "user",
          "email": "user@email.com",
          "phone": "+123 456-789",
          "address": "123 Street"
        }
        </pre>
        
        But, if you want to retrieve all the items of the agenda, the following HTTP request shows how:
        <pre>
        <b>GET</b> http://localhost:8686/example/agenda
        </pre>
        
        And the response will be:
        <pre>
        [
          {
            "id": "591a79400000000000000000",
            "name": "user",
            "email": "user@email.com",
            "phone": "+123 456-789",
            "address": "123 Street"
          },
          ...
        ]
        </pre>
        
        
        ## How does AutoApi work?
        
        AutoApi was develop on [Python](https://www.python.org/) using [Flask](http://flask.pocoo.org/) and [MongoDB](https://www.mongodb.com/), it was thought to support multiples API because AutoApi uses a database to represent an API, thus to differentiate between two APIs it is necessary to add the api name as a prefix in the URL. For instance, to retrieve all the movies from *imdb-copy* API it is necessary to do a **GET** to **/imdb-copy/movies**, but to retrieve the movies from **rottentomatoes-copy** API the URL is **/rottentomatoes-copy/movies**.
        
        Another important feature of AutoApi is the authentication, but authentication in this develop is at API level, so users can not be shared between APIs, the reason is because AutoApi uses MongoDB users instead of using a collection to store them, so they are related to a database and AutoApi consider a database as an API.
        
        ### Configuration file
        As AutoApi uses MongoDB to store the data, it is necessary to know the location of the database, by default AutoApi will try to connect to the default connection of MongoDB (*localhost*, *27017*) unless a configuration file is given.
        
        The configuration file stores the configuration for the MongoDB connection (including the authentication credentials), there is a template on this repository that show the syntax and the options, the template is called *server.cfg.default*.
        
        AutoApi can receive a configuration file using two methods, one is defining an environment variable with the name **AUTOAPI_SETTINGS** where the value is the file path. The other way is passing the parameter **config_path** to the constructor of AutoApi object with the file path.
        
        If you are going to use the given script to run AutoApi, you can provide [the configuration file as a parameter with the flag *-f*](#running-autoapi), that script uses one of the previous options.
        
        ## **AutoApi features**
        
        ### Authentication & Authorization
        
        AutoApi authentication is optional, by default it is not activated. To activate it is necessary:
         - [MongoDB auth](#mongodb) activated
         - [AutoApi configuration file](#configuration-file) filled
         - [Run AutoApi server](running-autoapi) with --auth flag
        
        #### Authentication
        
        Each API has their own users, so users have to logged specifying the API in the request:
        
        <pre>
        <b>POST</b> /login
        <b>Content-Type</b>: application/json
        
        {
          "api": "example",
          "email": "user@email.com",
          "password": "pass"
        }
        </pre>
        
        The response will contain a session token in the headers and body:
        
        <pre>
        <b>X-Email</b>: user@email.com
        <b>X-Token</b>: 123456
        
        {
          "email": "user@email.com",
          "token": "123456"
        }
        </pre>
        
        To logout, users have to specify the API too:
        
        <pre>
        <b>POST</b> /logout
        <b>Content-Type</b>: application/json
        <b>X-Email</b>: user@email.com
        <b>X-Token</b>: 123456
        
        {"api": "example"}
        </pre>
        
        #### Users and Authorization
        
        **Only admin users** can create more users specifying the API and CRUD roles:
        
        <pre>
        <b>POST</b> /user
        <b>Content-Type</b>: application/json
        <b>X-Email</b>: ADMIN_USER
        <b>X-Token</b>: ADMIN_USER_TOKEN
        
        {
          "email": "other_user@email.com",
          "password": "pass",
          "api": "example",
          "roles": ["read", "update"]
        }
        </pre>
        
        The last request creates the user *other_user@email.com* and authorizes him to *read* and *update* the *example* API without any API creation request.
        
        Each user can update his own password and only an admin user can change other users password . The change can be done using the following request:
        <pre>
        <b>POST</b> /password
        <b>Content-Type</b>: application/json
        <b>X-Email</b>: USER
        <b>X-Token</b>: USER_TOKEN
        
        {
          "email": "other_user@email.com",
          "password": "new-pass",
          "api": "example"
        }
        </pre>
        
        It is important to note that the request needs the *email* parameter to select to user that will change the password.
        
        Finally, only an admin user can change the authorization roles for a particular user using the following request:
        <pre>
        <b>POST</b> /roles
        <b>Content-Type</b>: application/json
        <b>X-Email</b>: ADMIN_USER
        <b>X-Token</b>: ADMIN_USER_TOKEN
        
        {
          "email": "other_user@email.com",
          "api": "example",
          "roles": {
            "update": false,
            "delete": true
          }
        }
        </pre>
        
        
        ### Collections and Resources
        
        #### API
        
        To use an API in AutoApi it is not necessary to create it, it is created on demand and there is no operations related for path **/api**.
        
        #### API collection
        
        To use and API collection in AutoApi it is not necessary to create it, it is also created on demand.
        
        #### CRUD collection's resources
        
        It is important to remember that if AutoApi's authentication is enabled then only logged users, with the respective authorization, can CRUD API's resources.
        
        A good API REST example is to show how to mark as a classic all the movies where *actor_1* appears.
        
        <pre>
        <b>PATCH</b> /example/actors/actor_1/movies
        <b>Content-Type</b>: application/json
        <b>X-Email</b>: user@email.com
        <b>X-Token</b>: USER_TOKEN
        
        {"classic": true}
        </pre>
        
        More info about REST:
        
        - http://www.restapitutorial.com/lessons/httpmethods.html
        - http://restful-api-design.readthedocs.org/en/latest/
        
        
        
        ## Dependencies and configuration
        
        #### Installation
        
        I strongly recommend you to use [virtualenv](https://virtualenv.pypa.io) and [virtualenvwrapper](https://virtualenvwrapper.readthedocs.io).
        
        <pre>
        $ workon api
        (api) $ pip install auto_api
        </pre>
        
        
        #### MongoDB
        
        AutoApi doesn't required modifications on MongoDB configuration to handle APIs, collectios or resources. But, if you want to activate [Authentication](#authentication) and [Authorization](#authorization), as AutoApi uses MongoDB users, it is necessary to set *auth=true* in your *mongodb.cfg* or run *mongod* with the flag *--auth* and you must to provide the MongoDB admin information inside the [AutoApi configuration file](#configuration-file)
        
        Related info:
        - http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/
        - http://docs.mongodb.org/manual/core/authentication
        - http://docs.mongodb.org/manual/core/authorization
        - http://docs.mongodb.org/manual/tutorial/add-user-administrator
        
        
        ## Running AutoApi
        
        After [installing AutoApi](#installation) it will be created an executable called **autoapi** and the python module **auto_api**. Also, remember that if you want to run AutoApi with authentication, you must first [turn on the authentication in MongoDB](#mongodb) and then provide the flags **-a** (or **--auth**) and **-f** (or **--config**) with a configuration file based on *server.cfg.default* (located on this repository) to the following commands:
        
        <pre>
        (api) $ autoapi [[-a] -f server.cfg]
        </pre>
        or
        <pre>
        (api) $ python -m auto_api [[-a] -f server.cfg]
        </pre>
        
        ## Testing AutoApi
        
        To run the AutoApi test there is a script called *run_tests.py*, that automatically start and stop two MongoDB servers for testing purpose only (one with authentication enabled).
        
        <pre>
        (api) $ ./run_tests.py [pytest-parameters]
        </pre>
        
        or
        
        <pre>
        (api) $ python setup.py run_tests [-a '[pytest-parameters]']
        </pre>
        
Keywords: api rest authentication mongodb automatic web flask json python
Platform: UNKNOWN
Classifier: Environment :: Web Environment
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: POSIX
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
Classifier: Topic :: Internet :: WWW/HTTP :: WSGI :: Application
Classifier: Topic :: Software Development :: Libraries :: Application Frameworks
Classifier: Topic :: Software Development :: Libraries :: Python Modules
Requires-Python: !=3.0.*,!=3.1.*,!=3.2.*,!=3.3.*,!=3.4.*,!=3.5.*,>=2.7
Description-Content-Type: text/markdown
