How to use
Open the school’s Integrations → API Keys area with the appropriate permission. Create a labeled key for the intended integration and store the returned credential securely. Review active/inactive keys and deactivate an obsolete key through its control.
Open /documentation/api on your GiveCampus environment for API documentation. Use the documentation matching the deployment/version to construct requests. Use the documented customer APIs for your resource, such as gifts, recurring subscriptions, constituents, designations, events or contact reports. Browser-only endpoints are not a supported integration contract.
Rules and troubleshooting
Creating a key is separate from granting every product capability. Deactivation is an intentional credential change; update dependent integrations accordingly. Never paste a key into a support chat or public document.
For failures, collect endpoint/version, method, request/result ID, response status, timestamp, and a redacted payload. Do not invent request schemas, rate limits, or guarantees from route names.
Comments
0 comments
Please sign in to leave a comment.