Fellowship Technologies strives to give back to the community at every turn. As such, most of our employees are involved in some form or fashion in the community in which their job pertains. Lance Dacy is the founder/organizer of the DFW Scrum User Group (recognized by the Scrum Alliance). DFW Scrum is focused on building a community of Scrum users to ensure all roles in the Scrum framework are represented and understood within the context of the barriers or struggles that some organizations face when implementing Scrum. They serve as a sounding board for new ideas or issues we all face when trying to be better today than we were yesterday. You can find out more at dfwscrum.com or follow them on Twitter.
What’s the process of getting onto using the REST API?
First of all, a request is submitted for a Key.
Applications developed using the REST API are divided into 3 categories: 1st party, 2nd party and 3rd party applications. 1st Party applications are written and made public by Fellowship Technologies. 2nd Party applications are written and made private by the Consumer and used by the Consumer’s (or Tenant’s) Users - They will be marked as Private. 3rd Party Consumer Applications are written and made public for consumption across Tenants. They will be marked as Public.
When the request is submitted, it goes through an approval process at Fellowship Technologies. If the request is approved, a Consumer Key and Secret is provided for the consumer application to use.
To begin accessing data using the API, the consumer application has to obtain an Access Token and Secret. You can read…
- Include Requirements & Contribution Sub Types
- User Case Story from Hope Community Church
- Group Search Categories and More
- Account Creation
- Single Sign On Functionality Exposed
- API Communication Value Changes
- API Enhancement: Create and Edit Groups!
- API Enhancement: Requirements Exposed
- Resource Versioning
- Enter Visitor Data via Your Church Website
- Fellowship One & Planning Center Online
- API Libraries and Sample Code
- Building a custom login for your church website using the API
- Roll Foward!
- The Agile Triangle
- Conversation Paralysis
- Picture this, image updates & creates through the REST API
- A REST API double shot : Groups and Events realms
- Increasing Software Delivery by 500%
- Quick people API realm update
- Introducing the new REST API giving realm
- Raising the bar…
- Building a Deployment Pipeline
- The World of Dev Craft
- Running Tests in Parallel with Selenium
- Abstracting Your Code to Remove Duplication
- Documentation in an Agile Environment
- Drowning in Debt
- Intro to Ruby on Rails
- API Strategy & Roadmap
- Staging/Sandbox Environment is Back up!
- Downtime in Sandbox/Staging Environment
- Android & OAuth
- F1 API Static Library with Objective-c
- Programming in F#
- NoSQL: HuMONGOus Benefits (Part 2)
- Our Scrum Team Structure
- SaaS & BI - The History & Future
- Getting Started with Android
- NoSQL: Leaving Schema Behind (Part 1)
- Your Feedback…and a $25 Gift Card!
- A Scrum Ceremony? Is this a wedding or something?
- Variables in PHP
- Data Exchange API Fixes
- F1 Check-in on the iPad
- Be the first to get the news & tips!
- An Introduction to PHP
- Working with Pop Up Windows in Selenium
- List Comprehension
- Source Control: A Time Machine For Your Source Code
- Developer Conference…Lower Price, Same Great Content!
- The Quality Assurance Team
- How does Fellowship Technologies manage complex projects?
- Developer Conference coming in May!
- Sandbox Refresh Complete
- Sandbox Refresh This Week
- Updates coming to the REST API
- Sandbox Environment Down Time
- F1Touch :: Fellowship One On The Go
- Under the Hood
- Sandbox Refresh Complete
- Sandbox Refresh Tomorrow (Oct. 2nd)
- Fellowship One Developer Forums
- Ten Commandments of API Consumption
- REST API Enhancements / Fixes deployed to Sandbox and Production 09.09.09
- Data Exchange URL cut-over complete
- Important Data Exchange URL changes
- Ron Nom Nom
- How to get started using the REST API