API Overview
The Text In Church API is built upon REST. Our API accepts form-encoded request bodies, returns JSON-encoded responses, uses bearer token-based authentication, and leverages standard HTTP response codes.
Getting Started
To get started, you will need to request developer access from our support team. Feel free to contact us on our support page. Once you've been given access to the developer area, you may create an API key for use in an authentication bearer token.
Base URL
All requests made to the API will have the following base URL:
https://api.textinchurch.com/API/1_0/
URLs to the API are case-sensitive.
Access
Access within the API is linked with the particular user associated with the authentication token. Whatever the user has access to see or do will be available within the API.
Current logged in user
To obtain details about the current logged in user, call the getMe.php endpoint.
https://api.textinchurch.com/API/1_0/getMe.php
Changes
While the API is dynamic, we try hard not to introduce breaking changes. Occasionally, we may make modifications that might require adjustment on your part. Any breaking changes will be listed in this documentation in the future.
Updated 12 months ago