API Rate Limits and Quotas
Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers who access the Platform application programming interface.
Article 1: Introduction and Scope
1.1 This document states the rate limits and quotas that govern API use as terms of the licence in the Developer Agreement. The limits are obligations, not guidance: a Developer that exceeds a limit, or that acts to defeat a limit, breaches this document whether or not harm results.
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 rate limits and quotas. 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 Call: one HTTP request to the API, counted in accordance with Article 5.
Quota: the maximum number of Calls a Developer account may make in a stated period, aggregated across every Credential on the account.
Rate Limit: the maximum rate of Calls a Credential may make in a rolling window, as stated in the technical documentation incorporated by Article 3.
Article 3: The Limits as Terms
3.1 Every authenticated API Call is measured against the calling Credential. The sustained rate, the burst allowance, and the monthly Quota for each Tier, and any lower per-interface limit for an expensive operation, are stated in the Core Concepts and in the API reference entries for the interfaces concerned, and are incorporated into this document by reference. The Developer shall comply with the limit that applies to the Credential and to the interface called; where two limits apply, the lower limit governs.
3.2 Limits are expressed as rolling windows. A Call counts if it falls inside the trailing window, and the oldest Calls cease to count continuously. The Developer shall not time or shape traffic to exploit a window boundary.
3.3 A burst allowance permits a brief rate above the sustained rate for the period the technical documentation states. It is not a second sustained rate, and the Developer shall not operate at the burst rate as a normal rate.
3.4 A monthly Quota aggregates across every Credential on the Developer account. Dividing traffic among Credentials does not multiply the Quota. A delivery the Company sends to the Developer under the Webhook Obligations does not count against the Developer's Quota; a Call the Developer makes to the API after receiving a delivery does count.
3.5 An Elevated Application acting for many Sellers draws from one account-level Quota. The Company measures the Credential; the Developer shall allocate capacity within the Application fairly among the Sellers it serves.
Article 4: Responses and Client Duties
4.1 The Company states the applicable limit, the remaining capacity, and the time at which capacity becomes available in the response information the technical documentation describes. The time stated by the Company is authoritative. A Developer whose system clock differs shall allow the margin the technical documentation states before treating capacity as available.
4.2 A request over the limit is rejected. The rejection states the period after which the Developer may retry. The Developer shall: (a) stop sending; (b) wait the full stated period; and (c) resume at a reduced pace with increasing intervals between retries and variation in those intervals. Retrying immediately, retrying on a fixed short loop, or distributing retries to defeat the rejection is a violation of Article 6, not a defect to be excused.
4.3 A sustained rate of rejections above the threshold stated in the technical documentation is evidence of a defective integration. The Company may intervene through support, and the Developer shall correct the client or accept a further reduction of the Credential's limit.
Article 5: Counting Rules
5.1 One HTTP request is one Call, with the following rules: (a) each page of a paginated result is one Call; (b) a retried request counts again, except as clause 5.2 provides; (c) a request the Company failed to answer counts if it reached the measuring point, and the Developer shall not assume a waiver of the count; (d) a request rejected before authentication does not count against the Quota, and repeated unauthenticated requests are governed by the Partner Security Requirements as abuse; and (e) a redelivered webhook event is not a Call by the Developer.
5.2 Where an interface accepts a key by which the Developer identifies a single logical operation, a retry carrying the same key within the period the technical documentation states returns the original result without performing the operation twice and counts as one Call. A retry without such a key is a new Call and a new operation, and the risk of omission is the Developer's.
Article 6: Circumvention
6.1 Circumvention of a Rate Limit or a Quota is a violation of this document independent of harm. Circumvention includes: (a) spreading one Application's load among multiple Credentials, accounts, or Applications to evade a limit or a Quota; (b) rotating keys, network addresses, client identifiers, or egress paths to evade throttling; (c) distributing load for the purpose of defeating a limit; (d) replaying a request the Company rejected for a limit instead of observing the stated retry period; (e) ignoring a retry signal, including a stated retry period in a rejection; and (f) using a Sandbox Credential or environment to serve production traffic in order to avoid a production limit.
6.2 The distinction between a defect and circumvention is intent and persistence. A client that observes retry signals but contains an error is a defective integration under clause 4.3. A client that detects a rejection and routes around it is circumvention under clause 6.1.
Article 7: Changes to Limits
7.1 A Developer may request an increase of a sustained rate with ten (10) business days' notice to support@aapawz.com, stating the use case and the expected traffic shape. The Company shall grant or deny the request in writing. An increase takes effect on the date the grant states; traffic before that date is judged under the limit then in effect.
7.2 A temporary increase for a launch, a migration, or incident recovery is granted in writing with an expiry time. On expiry the standard limit applies immediately, without a taper. A Developer that requires an extension shall request it before expiry.
7.3 The Company may lower a limit on notice for protection of the Platform, including during an incident. An emergency reduction during an active incident takes effect immediately, with notice given as soon as practicable, and the reduction and its reason are recorded and reviewable under Article 10.
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, including traffic and retry records for the Credentials concerned.
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. Throttling and rejection for a limit are protective measures and are not, without more, a determination of violation.
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, 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) throttle, suspend, or revoke a Credential; (c) suspend the Account or a program participation, in whole or in part; (d) terminate this document and the Account; and (e) exercise any other right or remedy available under this document or at law. Procedure is further governed by 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 first accesses the API 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 rights granted under this document end and Credentials 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, 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.