<!doctype html>
<html lang="en">

<head>
    <!-- Global site tag (gtag.js) - Google Analytics -->
    <script async src="https://www.googletagmanager.com/gtag/js?id=UA-92107911-8"></script>
    <script>
    window.dataLayer = window.dataLayer || [];
    function gtag(){dataLayer.push(arguments);}
    gtag('js', new Date());

    gtag('config', 'UA-92107911-8');
    </script>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
    <meta name="description" content="FellowshipOne API Documentation">
    <meta name="author" content="FellowshipOne">
    <title>Fellowship One - Developer Community</title>
    <!-- <link href="https://stackpath.bootstrapcdn.com/bootstrap/4.3.1/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-ggOyR0iXCbMQv3Xipma34MD+dH/1fQ784/j6cY/iJTQUOhcWr7x9JvoRxT2MZw1T" crossorigin="anonymous"> -->
    <link href="/assets/css/f1-kit.min.css" rel="stylesheet">
    <link href="/assets/css/docs.css" rel="stylesheet">
    <link href="https://fonts.googleapis.com/css?family=Open+Sans:300,400,600,700|Roboto:400,500,600" rel="stylesheet">
</head>

<body>
    <nav class="navbar navbar-expand-lg fixed-top navbar-dark bg-dark">
        <a class="navbar-brand mr-auto mr-lg-4" href="/">FellowshipOne API</a>
        <button class="navbar-toggler p-0 border-0" type="button" data-toggle="offcanvas">
            <span class="navbar-toggler-icon"></span>
        </button>

        <div class="navbar-collapse offcanvas-collapse" id="navigation">
            <ul class="navbar-nav mr-auto">    
                <li class="nav-item dropdown">
                    <a class="nav-link dropdown-toggle" href="#" id="api-realms" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">API Realms</a>
                    <div class="dropdown-menu" aria-labelledby="api-realms">
                        <a class="dropdown-item" href="/docs/v1/util/docs.help">People</a>
                        <a class="dropdown-item" href="/docs/giving/v1/util/docs.help">Giving</a>
                        <a class="dropdown-item" href="/docs/groups/v1/util/docs.help">Groups</a>
                        <a class="dropdown-item" href="/docs/events/v1/util/docs.help">Events</a>
                    </div>
                </li>    
                <li class="nav-item">
                    <a class="nav-link" href="/docs/v1/Util/SingleSignOn.help">SSO</a>
                </li>
                <li class="nav-item">
                    <a class="nav-link" href="/docs/v1/Util/accounts.help">Account Creation</a>
                </li>
                <li class="nav-item">
                    <a class="nav-link" href="/docs/v1/Util/AuthDocs.help">Authentication</a>
                </li>
                <li class="nav-item">
                    <a class="nav-link" href="/docs/v1/Util/HttpStatusCodes.help">Status Codes</a>
                </li>
                <li class="nav-item">
                    <a class="nav-link" href="/docs/v1/Util/HttpHeaders.help">Headers</a>
                </li>
                <li class="nav-item">
                    <a class="nav-link" href="/test-harness">Test Keys</a>
                </li>
            </ul>
        </div>
    </nav>

    <main role="main" class="container-fluid">
        <div class="card">
            <div class="card-body">
                                    <h2>FellowshipOne API Documentation</h2>
                    <p class="tease">
                        The Fellowship One REST API is a REST-based web application that uses several open protocols and patterns to provide consumers access to secure resources.
                    </p>
                    <p>
                        STANDARDS, PROTOCOLS, and PATTERNS - nothing else. As developers we see where there is major value in sticking with something that is "tried and true". If we could use web-based patterns and protocols for a web-based API, we could not only get instant adoption, but gain the efficiencies and effectiveness of technologies that "just work".
                    </p>
                    <p>
                        This next generation of API is, oddly, based on foundations that have been in place for years. We chose <a href="http://en.wikipedia.org/wiki/Model-view-controller">MVC</a> as the application architecture, <a href="http://oauth.net/core/1.0/">OAUTH</a> protocol for authentication, <a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm">REST</a> and <a href="http://www.w3.org/Protocols/rfc2616/rfc2616.html">HTTP 1.1</a> as the transport. This API should give web developers a tool where all they have to think about is what to do with the resources. Navigate the API documentation using the links above.
                    </p>
                    <p>
                    To request a key for staging, production, or access to an additional Realm, click <a href="mailto:f1support@fellowshipone.com?subject=API%20Key%20Request&amp;body=Environment%3A%0A%0AName%3A%0A%0AEmail%3A%0A%0AChurch%20Name%3A%0A%0AChurch%20Code%3A%0A%0AApplication%20Name%3A%0A%0ADescription%3A%0A%0ARealms%3A">here</a>.
                    </p>
                                
                            </div>
        </div>
    </main>
    <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo" crossorigin="anonymous"></script>
    <script>
        window.jQuery || document.write('<script src="/docs/4.3/assets/js/vendor/jquery-slim.min.js"><\/script>')
    </script>
    <script src="/assets/js/f1-kit.bundle.min.js"></script>
    <script src="/assets/js/docs.js"></script>
</body>

</html>