Amenity Reserve API terms
What a community agrees to when it connects another tool to Amenity Reserve™ with an API key or a webhook endpoint.
These terms add to the community terms the community has accepted. They apply when the community makes an API key or a webhook endpoint.
1. The community’s instruction
Each API key and webhook endpoint is the community’s instruction to send the data its scopes open to the tool the community connects. The community decides which tools to connect and which scopes to grant. That tool is the community’s choice, and its own terms and privacy policy govern it. Better Seasons does not choose, run or check that tool.
2. Resident data
A key with members:read opens residents’ full names, email addresses, street addresses, role and standing. The community grants it only where its governing documents, its own policies and the law allow it to share that information with the tool. It uses that information only to run the community.
3. Keys
The community keeps its keys secret and is responsible for every request made with them until it revokes them. It revokes any key it believes has been exposed.
4. Revocation and limits
Better Seasons Inc. may suspend or revoke a key or endpoint that is leaked, abused, used against these terms, or a risk to residents or the service, and it tells the owner. Requests are rate limited.
5. Changes
Better Seasons may change the API, its limits and these API terms. It gives the owner at least 30 days’ notice by email of a change that removes a field or an endpoint or changes these terms. A change needed for security may take effect at once.
6. Everything else
The community terms otherwise apply, including section 9.