The API Access and Usage Agreement is a ready-to-use technology & digital template you can send for signature in minutes. It is written for 2 signers (provider and developer) and, by default, expires 30 days after it is sent if left unsigned. It covers two signers, agreement. Like every Abundera Sign template it is a convenience draft structured for ESIGN Act and UETA compliance, not a substitute for legal advice. Each signed copy is sealed with PAdES-LTA digital signatures, dual RFC 3161 timestamps, and a tamper-evident evidence package in WORM storage.
Document Preview
# API Access and Usage Agreement **Effective Date:** ___________ This API Access and Usage Agreement ("Agreement") is entered into by and between: **API Provider:** ___________ ("Provider") **Developer/Integrator:** ___________ ("Developer") ## 1. API Services **API Name/Product:** ___________ **API Description:** ___________ **API Base URL:** ___________ **API Version:** ___________ ## 2. Access Credentials (a) Provider shall issue Developer API credentials (API keys, OAuth tokens, or other authentication mechanisms) upon execution of this Agreement. (b) Developer shall keep all API credentials confidential and shall not share, publish, or expose credentials in client-side code, public repositories, or insecure environments. (c) Developer shall immediately notify Provider if credentials are compromised or suspected to be compromised. (d) **Authentication Method:** ___________ ## 3. Usage Limits and Rate Limiting **Plan/Tier:** ___________ **Rate Limit:** ___________ **Monthly Quota:** ___________ (a) Developer shall not exceed the rate limits or quotas specified above. Provider may throttle, queue, or reject requests that exceed these limits.