February AIContract Templates

North Carolina, US · Technology

API License Agreement
Contract Template For North Carolina, US

North Carolina API license agreement defining access credentials, permitted integration, usage limits, data handling, security, service changes and intellectual-property ownership.

Governing law: North Carolina, USPublished templateUpdated 2026-11-08
API LICENSE AGREEMENT
# API LICENSE AGREEMENT North Carolina, US Effective date: [date] Provider: [legal name], of [address] (Provider). Developer: [legal name], of [address] (Developer). ## 1. API and license Provider grants Developer during the Term a limited, nonexclusive, nontransferable, nonsublicensable and revocable license to access and use Provider's application programming interface identified in Schedule 1 (API) and its technical instructions (Documentation) solely to build and operate the application identified there (Developer Application) for the permitted business purpose and users stated there. Developer may copy Documentation only for its authorized personnel and contractors. No source code, patent, trademark, hosted-service ownership or right to resell API access is granted. Developer may not share access credentials, circumvent limits, probe for vulnerabilities, scrape outside documented endpoints, reverse engineer except to the limited extent nonwaivable law permits, interfere with the service, introduce malicious code, or use the API or its output to create an unlawful or misleading product. ## 2. Credentials and automated requests Provider will issue API keys, tokens or other access secrets (Credentials) to Developer's approved accounts. Developer will protect Credentials, use least privilege, rotate them as reasonably required and promptly revoke access for departing personnel. Developer is responsible for requests made with its Credentials until it gives Provider notice of compromise, except to the extent caused by Provider. The parties agree to conduct API transactions electronically. An automated request is authorized only if generated by the Developer Application within this Agreement and Schedule 1. Logs and technical records may evidence a request, response and time, but do not override an express written limitation or establish that data was accurate. ## 3. Usage limits and changes Rate limits, environments, supported versions, service levels and fees are in Schedule 1. Developer will implement reasonable retry, timeout, caching and error handling and will not evade a limit through multiple accounts. Provider may throttle access to protect security or availability and will use reasonable efforts to give notice of a material nonemergency limit change. Provider may modify the API. For a material backward-incompatible change, Provider will give at least [90] days' notice and maintain the prior version for that period unless a security, legal or third-party dependency issue requires earlier action. Provider may immediately suspend an endpoint or Credential posing a credible security, legal or operational risk and will explain the basis when lawful. ## 4. Data rights and restrictions Provider retains ownership of data it makes available through the API (Provider Data), subject to third-party rights. Developer retains ownership of data it lawfully submits (Developer Data). Each party grants the other only the limited rights necessary to perform this Agreement. Developer will request, collect and retain only data necessary for the permitted purpose; honor field-level restrictions and deletion instructions; not sell, reidentify, profile or combine Provider Data except as Schedule 2 expressly permits; and not represent that Provider endorses the Developer Application. Developer will display required notices and obtain legally sufficient user permissions. Provider will process Developer Data only to operate, secure and support the API or as otherwise stated in Schedule 2. ## 5. Security and incidents Each party will maintain reasonable safeguards proportionate to the data and risk, including access controls, authentication, supported software, logging, vulnerability management and secure transmission. Developer will segregate production Credentials from source repositories and public client code. A party discovering unauthorized access to the other's data or systems in its control will notify the other without unreasonable delay, provide known facts, preserve evidence, mitigate harm and cooperate with legally required notices. Neither party may notify in the other's name without authorization unless law requires it. Sector-specific or customer duties that are stricter continue to apply. ## 6. Intellectual property and feedback Provider owns the API, Documentation, Provider marks and all modifications, excluding Developer Data and Developer's independent technology. Developer owns the Developer Application and Developer marks, excluding the API, Provider Data and Provider materials. Developer grants Provider a limited license to use Developer's name and technical integration information only to provide support and describe an approved integration if Schedule 1 permits it. Developer may provide feedback voluntarily. Provider may use nonconfidential feedback without restriction, but receives no ownership of Developer's code, data or inventions merely because feedback is supplied. ## 7. Fees, support and warranties Developer will pay the fees and taxes in Schedule 1. Provider will provide the support stated there. Each party warrants authority to sign and that its supplied materials will not knowingly violate a third party's rights. Provider warrants that the API will materially conform to current Documentation during the paid Term and will use reasonable efforts to correct a reproducible material nonconformity. Except for those express promises and nonwaivable law, the API is provided as available. Provider does not guarantee uninterrupted operation, any business result or the accuracy of third-party data. Developer is responsible for testing, user-facing decisions and any regulated use of the Developer Application. ## 8. Claims, liability and term Each party will defend the other against a third-party claim that its supplied technology or data infringes rights, and Developer will defend claims caused by the Developer Application's unlawful operation or use outside this Agreement. The protected party must give prompt notice and reasonable cooperation; no settlement may admit its fault or impose nonmonetary duties without consent. The Term is [period]. Either party may terminate for material breach not cured within [15] days, or immediately for deliberate security abuse or illegality. Provider may terminate for convenience on [90] days' notice, refunding prepaid fees for the unused period. On termination, Developer will stop API access, delete Credentials and return or delete Provider Data except lawful archival copies; accrued payment, confidentiality, ownership and claim duties survive. North Carolina law governs. This Agreement and schedules are the entire agreement. Amendments must be signed. Neither party may assign without consent except to a successor assuming the duties. Notices are effective on receipt. Invalid terms will be limited. Counterparts and agreed electronic signatures are effective. PROVIDER: ____________________ Name and title: [name and title] Date: [date] DEVELOPER: ____________________ Name and title: [name and title] Date: [date] ## SCHEDULE 1 — ACCESS AND COMMERCIAL TERMS API and endpoints; Developer Application; purpose and users; environments; Credentials; versions; limits; service levels; support; fees; Term; approved trademark reference: [details]. ## SCHEDULE 2 — DATA RULES Provider Data and Developer Data; permitted fields and uses; prohibited uses; notices and permissions; retention and deletion; residency; subprocessors; incident contacts: [details].

Licensed under CC BY 4.0. Attribution is required when you publish or redistribute this Template or an adapted version to the public. Attribution is not required merely because you use or adapt the Template for your own business or legal purposes, including preparing, negotiating, signing, or exchanging an agreement with a counterparty. License details.

More templates for North Carolina, US