...
Connection information: Connection date, volunteer’s comments, answers to custom questions, shifts selected, the source that generated the connection. See full schema of Connection detail here. By default, VolunteerMatch only provides connection generated by youyour app. If you need data on connections generated from another source (i.e. VolunteerMatch hosted public site), your API key will need to have special configuration applied.
Volunteer’s information: email address, first and last name, zip code, skills etc. See full schema of Volunteer/Person detail here.
Opportunity details: Title, location, description, cause area etc. See full schema of Opportunity Detail here.
Organization details: Organization name, classification, ein, classification, cause area etc. See full schema of Organization Detail here.
...
Please see our public repository in Github for sample code and getting started instructions.
All development and testing must be done on our stage environment (stage.volunteermatch.org) using a stage API Key.
Connections made in this environment will not be sent to our nonprofit partners and protects them from SPAM.
Note that our stage database contains test data, and is not representative of our live network. Testing or demoing connection functionality on production quality data can only be made using special systems. VolunteerMatch will provide this upon request when you are ready to release.
If a client key is NO longer active, the following response will be returned: 401 Your API key is inactive.