PHPackages                             schplay/f1 - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Authentication & Authorization](/categories/authentication)
4. /
5. schplay/f1

ActiveLibrary[Authentication & Authorization](/categories/authentication)

schplay/f1
==========

Utilizes 2nd Party authentication to work with FellowshipOne's API

014PHP

Since Jun 8Pushed 11y ago1 watchersCompare

[ Source](https://github.com/schplay/fellowshipone)[ Packagist](https://packagist.org/packages/schplay/f1)[ RSS](/packages/schplay-f1/feed)WikiDiscussions master Synced 5d ago

READMEChangelogDependenciesVersions (1)Used By (0)

Fellowship One API
==================

[](#fellowship-one-api)

Interacting with Fellowship One
-------------------------------

[](#interacting-with-fellowship-one)

This package provides 2nd Party, and Vendor to Vendor authentication and the ability to make GET, POST, and PUT requests. You must build your own package/controllers to actually interact with Fellowship One data.

For 2nd party authorization, before starting, you need to have a "Portal User" account that is linked to a specific user in your Fellowship One database. You also must have a 2nd Party Application enabled in your church's Fellowship One admin section.

Installation
------------

[](#installation)

### Service Provider

[](#service-provider)

Add the following to your service provider array

```
Schplay\F1\F1ServiceProvider

```

### Configuration

[](#configuration)

Copy the configuration file

```
php artisan config:publish schplay/f1

```

Set the appropriate credentials and base URLs.

Usage
-----

[](#usage)

In any class, add `use F1;` before the class declaration.

If using 3rd party or vendor to vendor authorization, you then need to dynamically set the base url and api secret using the Config class.

The builtin `F1` façade uses Guzzle's HTTP Client + OauthPlugin to make the requests. Consult their documentation for building requests and handling responses.

For example, create a request to Fellowship One's API by using the appropriate endpoint and format:

```
$request = F1::get('v1/people/statuses.json')->send();

```

Using Guzzle, there are multiple ways to handle the response:

```
$response = $request->getBody(true);

```

Or, use Guzzle's built in `json()` method:

```
$response = $request->json();

```

Check Guzzle's documentation for more help (including leveraging Exceptions, etc).

Questions: @avr

###  Health Score

20

—

LowBetter than 14% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity6

Limited adoption so far

Community9

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 85.7% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/a104dd4551b512f08303dad65050f792232e443628a731638380a17bf2b1368d?d=identicon)[schplay](/maintainers/schplay)

---

Top Contributors

[![schplay](https://avatars.githubusercontent.com/u/993640?v=4)](https://github.com/schplay "schplay (12 commits)")[![avr](https://avatars.githubusercontent.com/u/347482?v=4)](https://github.com/avr "avr (2 commits)")

### Embed Badge

![Health badge](/badges/schplay-f1/health.svg)

```
[![Health](https://phpackages.com/badges/schplay-f1/health.svg)](https://phpackages.com/packages/schplay-f1)
```

###  Alternatives

[namshi/jose

JSON Object Signing and Encryption library for PHP.

1.8k99.6M101](/packages/namshi-jose)[league/oauth1-client

OAuth 1.0 Client Library

99698.8M106](/packages/league-oauth1-client)[bezhansalleh/filament-shield

Filament support for `spatie/laravel-permission`.

2.8k2.9M88](/packages/bezhansalleh-filament-shield)[gesdinet/jwt-refresh-token-bundle

Implements a refresh token system over Json Web Tokens in Symfony

70516.4M35](/packages/gesdinet-jwt-refresh-token-bundle)[league/oauth2-google

Google OAuth 2.0 Client Provider for The PHP League OAuth2-Client

41721.2M118](/packages/league-oauth2-google)[illuminate/auth

The Illuminate Auth package.

9327.3M1.0k](/packages/illuminate-auth)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)