PHPackages                             avr/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. avr/f1

ActiveLibrary

avr/f1
======

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

371PHP

Since Oct 30Pushed 12y ago1 watchersCompare

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

READMEChangelogDependenciesVersions (1)Used By (0)

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

[](#fellowship-one-api)

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

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

This package only provides 2nd Party 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.

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

```
Avr\F1\F1ServiceProvider

```

### Configuration

[](#configuration)

Copy the configuration file

```
php artisan config:publish avr/f1

```

Set the appropriate credentials and base URLs.

Usage
-----

[](#usage)

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

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

21

—

LowBetter than 19% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity9

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% 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/ef9f24924554f62c95e2239ec94345dafc60ec8d44e4c5253c30b64e350c7632?d=identicon)[avr](/maintainers/avr)

---

Top Contributors

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

### Embed Badge

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

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

PHPackages © 2026

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