If you aren't providing any personally identifiable information, and privacy of the data isn't a concern... because file counts are pretty benign...
On something like AWS, you could setup the security group to allow access only from 1 source
x.instructure.com and then a CORS setup in your service to match.
REST Security Cheat Sheet - OWASP
Management endpoints
- Restrict access to these endpoints by firewall rules or use of access control lists.
Cross-Origin Resource Sharing (CORS) is a W3C standard to flexibly specify what cross-domain requests are permitted. By delivering appropriate CORS Headers your REST API signals to the browser which domains, AKA origins, are allowed to make JavaScript calls to the REST service.