For GiveCampus integrations and API.
The documented route is POST /api/contact_reports/search with a school API bearer token and a JSON search object. Replace example strings with actual external identifiers; omit filters you do not intend to apply. The documented date filters are Unix timestamps in seconds, not milliseconds. The request is asynchronous: submission returns a request ID/in-progress state, and the documented results endpoint returns the completed download. Collect the actual HTTP status, redacted response and request ID when troubleshooting; a missing screenshot does not confirm an authentication error. Never copy credentials into a knowledge-base example.
Date filters and missing results
The created_at, last_updated_at, and date_of_interaction filters include reports on or after the supplied timestamp. They are not exact-date matches. Use Unix timestamps in seconds. Normal whitespace around JSON keys does not change a valid request; a key's spelling must still match exactly.
The search returns finalized contact reports, not drafts. Reports whose primary constituent exists but lacks an external identifier are excluded from the response. If expected results are missing, check those conditions and the filters before concluding that there are no reports for the date.
The download says Request has expired
The completed request provides a separate signed download URL that expires 15 minutes after it is generated. Download the result promptly and preserve the entire URL, including its query string. An expired storage URL is different from an invalid GiveCampus API token.
Submit the original search again to create a new request, poll GET /api/results/{request_id} using the new request ID until the response is completed, and read its download_url, then download its new URL promptly. Repeatedly checking the old request returns its stored URL and does not renew it. Do not add blank placeholder filter values or change credentials solely because a download URL expired. Share only a redacted response and request ID with Support.
Comments
0 comments
Please sign in to leave a comment.