Rather than defaulting to all data being exchanged, your Ed-Fi integration should allow the users to select which API resources should be shared as part of a regular data exchange. Additionally, the user should be notified if the configuration will cause synchronization problems due to dependency order inherent in API resources.
The specific use case should be considered as well. For example, if a system integration will be supporting programs only at certain schools, then the API client should allow the configuration to be restricted in this same manner – to particular schools.
By default, API resources should be turned off and require a clear and deliberate action by a user with the proper authority to enable them. This helps ensure that your systems's user is making an active choice to provide the data, and is authorized to perform that action.