Q1: What data can be accessed and stored within MinistryPlatform when using your API?
All database tables and fields are accessible through our API. This includes custom tables and fields unique to each organization.

Q2: What programming languages can be used with the MinistryPlatform API?
Any programming language that can utilize REST. We know of developers that have used C#/.NET and PHP, but any modern language should be able to consume our API data.

Q3: Can our developers connect directly to the MinistryPlatform Database?
Technically speaking, each self-hosted church has direct database access since MinistryPlatform is installed on a server owned and maintained by your organization. However, we strongly discourage anyone from this practice. Using the API will give you access to the identical scope of data. More importantly, it will also handle a layer of security and audit-logging that you would otherwise have to write yourselves.

Q4: What documentation/examples are available for your API?
See Application Development and Community Resources.

Q5: Are there any classes/tutorials available for consuming your API?
There are no classes or tutorials available. However, we do offer various types of Professional Services to developers and churches. See Application Development for details. Also, we frequently have a development track or several development sessions as part of our annual MinistryPlatform User Group (MPUG) conference. See MPUG for sessions regarding development.

Q6: How do I set up a Sandbox system?
For instructions on how to set up a sandbox system, see Sandboxes. Note: Beyond this documentation, setup, maintenance, updates, and troubleshooting for sandbox systems are not covered by Think Ministry Support.

Q7: Can I get software updates to my Sandbox when they are applied to my Production system?
We do not apply software updates to sandboxes, but we do offer Development Deployment updates to a Beta system (a Beta system runs on a separate subdomain). See Development Deployments.