API Access Tiers
Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers who hold or seek an API access tier.
Article 1: Introduction and Scope
1.1 This document governs the API access tiers of the Platform: what each tier grants, how a tier is assigned and changed, and the consequences of use outside the granted tier. It is a program document under the Developer Agreement.
1.2 If a provision of this document conflicts with the Terms of Use, this document controls for its subject. If a provision of this document conflicts with the Developer Agreement, the Developer Agreement controls, except that this document controls for the scope of a tier grant. Policies and help pages explain this document; they do not amend it.
Article 2: Definitions
2.1 In this document, terms defined in the Developer Agreement have the same meaning, and Elevated Tier: the tier for multi-tenant and platform-scale work, granted only by written agreement, as stated in clause 4.3.
Sandbox Tier: the development tier, granting access to the Sandbox environment only, as stated in clause 4.1.
Standard Tier: the default production tier, granting production access for one tenant only, as stated in clause 4.2.
Tier: Sandbox Tier, Standard Tier, or Elevated Tier, as applicable.
Article 3: Eligibility and Registration
3.1 A Developer is eligible for a Tier only if the Developer holds a Developer registration under the Developer Agreement, has provided a verified identity and a stated use case, and is in good standing under §Developer Agreement–2.7.25.
3.2 Production access requires verification of identity and use case. Elevated Tier requires a written agreement with the Company stating the negotiated limits, support terms, and any fees.
Article 4: The Tiers as Licence Scope
4.1 Sandbox Tier. The Sandbox Tier grants access to the Sandbox environment with test data only, in accordance with the Sandbox Acceptable Use Policy. It grants no production data, no production interface, and no production webhook delivery, and no access to personal data of a Buyer or a Seller.
4.2 Standard Tier. The Standard Tier grants production API access at the Standard rate limits stated in the API Rate Limits and Quotas, webhook subscriptions for the subscribing Application's own tenant data under the Webhook Obligations, one production Application, and email support. A Standard Application may read and act on the data of exactly one tenant: the tenant that owns the Credential.
4.3 Elevated Tier. The Elevated Tier grants, as the written agreement states: negotiated rate limits in place of the Standard table; more than one production Application; eligibility to register an Application under the OAuth App Registration and Review; eligibility to list in the App Marketplace under the App Marketplace Terms; and a named support contact under the Partner Support and Incident Escalation Policy. Elevated Tier is the only Tier in which an Application may hold data for more than one tenant, and then only through the consent procedure in the OAuth App Registration and Review for each End User.
4.4 A Tier grant is a scope of the licence in the Developer Agreement. It is not an entitlement, a property right, or a guarantee of continued access at the same scope. The numeric limits that attach to each Tier are stated in the API Rate Limits and Quotas and in the technical documentation incorporated there.
Article 5: Assignment and Changes
5.1 A new Developer registration begins in the Sandbox Tier. The Company grants Standard Tier after verification under clause 3.2, and Elevated Tier only by written agreement.
5.2 A Developer may request an upgrade through the developer portal. The Company shall decide a complete request within five (5) business days. A decision to deny shall state the reason, and the Developer may apply again after addressing the reason. An upgrade takes effect when the Company issues or re-scopes the Credential, not when the Developer requests it and not when the Developer deploys. Traffic sent before the new Tier takes effect is judged under the Tier then in effect.
5.3 A Developer may request a downgrade at any time. Rate limits and data scope reduce to the lower Tier immediately on the Company's confirmation; any fee effect takes effect at the next billing cycle in accordance with the API Monetization and Usage Fees Policy. A downgrade from Elevated Tier to Standard Tier ends multi-tenant grants under the OAuth App Registration and Review, and the Developer shall delete the other tenants' data in accordance with the Data Use, Retention and Deletion.
5.4 The Company may change a Tier on notice for platform protection or as an enforcement measure under Article 9. An involuntary change shall state the reason and is subject to appeal under Article 9.
5.5 A Credential carries its Tier, its environment, and its scopes. A change of Tier changes what the Credential may do without changing the Credential itself. Revocation of the Credential ends the Tier assignment.
Article 6: Use Outside the Granted Tier
6.1 Use outside the granted Tier is a breach of the Developer Agreement and of this document. Such use includes: (a) operating a production workload on a Sandbox Credential or in the Sandbox environment; (b) dividing one Application's traffic among multiple Developer accounts, Credentials, or Applications to remain under a Tier limit or a fee threshold; (c) using one tenant's Credential to serve another tenant's data, except as clause 4.3 permits; (d) reselling, subletting, or sharing a Credential so that a second party operates at a Tier that party has not been granted; and (e) collecting another person's session credential to work around an identity binding, which is also a violation of the Partner Security Requirements.
6.2 A Developer that holds two roles, for example as a Seller and as a partner building for others, holds those roles under separate registrations. A Seller session is not a partner Credential, and a partner Credential shall not be used to administer the Developer's own Seller account outside the consent procedure in the OAuth App Registration and Review.
Article 7: Fees
7.1 Tier fees, overage rates, and paid additions, if any, are governed by the API Monetization and Usage Fees Policy. A fee is payable under this document only if the fee is stated in that document. Non-payment, where a fee applies, is governed by that document, including downgrade to the Sandbox Tier as it provides.
Article 8: Liability
8.1 Exclusion of certain damages. To the fullest extent permitted by law, neither party is liable to the other for indirect, incidental, special, punitive, or consequential damages, or for lost profits, lost revenue, or loss of goodwill, arising out of or relating to this document, even if the party has been advised of the possibility of those damages.
8.2 Cap. To the fullest extent permitted by law, the Company's total liability arising out of or relating to this document shall not exceed the greater of (a) the amounts the Developer paid to the Company under this document in the twelve months before the event giving rise to the claim, or (b) one hundred dollars ($100).
8.3 Carve-outs. This article does not limit (a) a party's indemnification obligations under this document; (b) liability for fraud or willful misconduct; (c) amounts the Developer owes for Orders, fees, chargebacks, or refunds under this document; or (d) liability that cannot be limited under applicable law.
8.4 Essential purpose. The parties agree that this article allocates risk between them, that it is an essential part of the basis of their bargain, and that it applies even if a limited remedy fails of its essential purpose.
Article 9: Indemnification
9.1 Duty. The Developer shall indemnify, defend, and hold harmless the Company and its members, managers, employees, and agents from and against every claim, demand, action, loss, liability, judgment, settlement, cost, and expense (including reasonable attorneys' fees) arising out of or relating to: (a) the Developer's breach of this document; (b) the Developer's Applications and content; (c) the Developer's violation of any law or of the rights of any person; and (d) taxes for which the Developer is responsible under this document.
9.2 Procedure. The Company shall give prompt written notice of a claim under this article. The Developer shall control the defense with counsel reasonably acceptable to the Company. The Company may participate in the defense at its own expense. The Developer shall not settle a claim in a manner that imposes any obligation or restriction on the Company, or that does not release the Company fully, without the Company's prior written consent.
9.3 Survival. This article survives the termination of this document.
Article 10: Enforcement and Appeals
10.1 Investigation. The Company may investigate any suspected violation of this document. The Developer shall cooperate with an investigation and shall produce the records this document requires the Developer to keep.
10.2 Notice. If the Company determines that the Developer has violated this document, the Company shall give written notice stating the provision violated and the facts relied on, except where notice would compromise an investigation of fraud, a safety risk, or a legal obligation.
10.3 Opportunity to cure. Where a violation is capable of cure, the Developer has ten (10) business days from notice to cure it and to confirm the cure in writing. No cure period applies to circumvention under Article 6, to fraud, to unlawful conduct, or to a violation that by its nature cannot be cured.
10.4 Measures. If a violation is established and is not cured within the period allowed, the Company may, proportionate to the violation: (a) issue a written warning; (b) move the Developer to a lower Tier or to Sandbox-only access; (c) restrict, suspend, or revoke a Credential; (d) suspend the Account or a program participation, in whole or in part; (e) terminate this document and the Account; and (f) exercise any other right or remedy available under this document or at law. Circumvention under Article 6 permits immediate revocation of the Credentials involved, without a cure period, and restriction to the Sandbox Tier pending review, in accordance with the Partner Suspension, Termination and Appeals.
10.5 Appeal. The Developer may appeal a measure under this article by written notice to legal@aapawz.com within thirty (30) days of the measure, stating the grounds and attaching the records relied on. The appeal is decided by a person who did not make the original decision. The Company's decision on appeal is final. A measure remains in effect during an appeal unless the Company directs otherwise in writing.
10.6 No waiver by delay. The Company's delay in acting on a violation is not a waiver of the violation or of any later violation of the same kind.
Article 11: Term and Termination
11.1 Term. This document takes effect when the Developer is granted a Tier and continues until terminated under this article or until the Developer Agreement terminates, whichever occurs first.
11.2 Termination by the Company. The Company may terminate this document on thirty (30) days' written notice for any reason, and immediately on written notice if the Developer materially breaches this document, engages in fraud, or becomes ineligible to participate.
11.3 Termination by the Developer. The Developer may terminate this document on thirty (30) days' written notice to support@aapawz.com, provided the Developer has no investigation outstanding.
11.4 Effect of termination. On termination: (a) the Tier grant ends and Credentials issued under it are revoked; (b) obligations that arose before termination survive until satisfied; and (c) the Company shall pay amounts owed, less amounts the Company may set off under this document, within thirty (30) days, except amounts held in connection with an open investigation or dispute.
11.5 Survival. The Definitions, Fees (for accrued amounts), Liability, Indemnification, Enforcement and Appeals (for measures taken before termination), Dispute Resolution, and General Provisions articles survive termination.
Article 12: Dispute Resolution
12.1 Any dispute arising out of or relating to this document, or to the relationship it governs, is governed by the Dispute Resolution Policy, which is incorporated into this document by reference.
Article 13: General Provisions
13.1 Amendments. The Company may amend this document by posting the amended document in the Document Center and giving notice to the Developer at the email address in the Account. An amendment that materially increases the Developer's fees or obligations takes effect thirty (30) days after notice; other amendments take effect on posting. Continued use of the Platform after the effective date of an amendment is acceptance of it. If the Developer does not accept an amendment, the Developer's remedy is to terminate under Article 11 before the amendment takes effect.
13.2 Notices. Legal notices under this document shall be sent to legal@aapawz.com. Operational notices and all other communications shall be sent to support@aapawz.com. A notice to the Company is effective when the Company acknowledges receipt or, for email, one business day after sending, whichever is earlier. Notices to the Developer are effective when sent to the email address in the Account or posted to the Account's notice facility in the portal, whichever occurs first. The Developer shall keep the email address in the Account current. DMCA notices are given as provided in the DMCA and Copyright Policy, to the designated agent at legal@aapawz.com.
13.3 Governing law. This document is governed by the laws of the State of Tennessee, without regard to its conflict-of-laws rules. Subject to the Dispute Resolution Policy, any proceeding arising out of this document shall be brought in the state or federal courts located in Shelby County, Tennessee, and the parties consent to personal jurisdiction there.
13.4 Severability. If any provision of this document is held unenforceable, the provision shall be enforced to the fullest extent permitted, and the remaining provisions continue in full effect.
13.5 Entire agreement. This document, together with the documents it incorporates by reference, is the entire agreement between the Company and the Developer for the subject it governs and supersedes every prior or contemporaneous statement, communication, or agreement on that subject, whether written or oral.
13.6 Assignment. The Developer shall not assign this document or any right or obligation under it without the Company's prior written consent, and an assignment without consent is void. The Company may assign this document to an affiliate or in connection with a sale of all or part of its business, on notice to the Developer.
13.7 Waiver. A waiver of any provision of this document is effective only in writing and only for the instance stated. No waiver is a waiver of any other provision or instance.
13.8 Interpretation. Headings are for convenience only. "Including" means "including without limitation." This document shall not be construed against a party on the ground that the party prepared it. The English-language text controls over any translation.