Developer Agreement
Effective Date: October 15, 2026 Version: 1.0 Applies to: All Developers and partners who access or use the Platform application programming interface or developer tools.
Article 1: Introduction and Scope
1.1 This document is the master agreement between All About Pawz, LLC (the "Company") and each Developer. It governs access to and use of the application programming interface (the "API") and the developer tools the Company makes available, and it states the licence under which that access is granted and the obligations that attach to it.
1.2 The Developer accepts this document by registering for developer access, by accepting credentials, or by accessing or using the API or developer tools after this document has been posted. A Developer that does not accept this document shall not access or use the API or developer tools.
1.3 If a provision of this document conflicts with the Terms of Use, this document controls for API and developer-tool use. If a provision of this document conflicts with a more specific document in §API Access Tiers–2.7.25 for the subject that document governs, the more specific document controls for that subject. Policies and help pages explain this document; they do not amend it, and in any conflict this document prevails, except as the preceding sentences provide.
Article 2: Definitions
2.1 In this document Account: the account a person or business establishes with the Company to use the Platform.
API: the programmatic interfaces the Company publishes for developer use, as described in the technical documentation for the Platform. The API does not include the Site, a portal interface, or any internal data service of the Company.
Application: software built or operated by a Developer that accesses the API, including an integration, a connector, an automation, an automated agent, and a marketplace application.
Company: All About Pawz, LLC, a Tennessee limited liability company.
Credentials: an API key, a client secret, a session credential, a signing secret, or any other credential the Company issues to or accepts from a Developer for access to the API.
Developer: a person or business that accesses or uses the API or developer tools, whether directly or through an Application, and any contractor or service provider acting on that person's or business's behalf for that purpose.
End User: a Buyer, a Seller, or another person whose data an Application accesses or whose account an Application acts on.
Platform: the websites, applications, and services the Company operates under the name All About Pawz, including aapawz.com.
Production: the live environment of the Platform that serves End Users and holds production data.
Sandbox: the test environment of the Platform, governed by the Sandbox Acceptable Use Policy.
Seller: a person or business the Company has accepted to offer products or services through the Platform.
Site: aapawz.com and its subdomains.
Article 3: Eligibility and Registration
3.1 The Developer shall be at least 18 years of age or a legal entity in good standing. The Developer shall provide complete and accurate registration information, including a legal identity and a monitored contact address, and shall keep that information current.
3.2 The Company may require verification of identity and of the stated use case before granting access, and may deny access where the applicant cannot be identified as a real legal person or entity, where registration is made through a shell entity or a misrepresented identity, or where the applicant is ineligible under this document. Anonymous integration is not permitted: every Application shall be attributable to a Developer the Company can contact.
3.3 A Seller that accesses the API for the Seller's own store does so as a Developer under this document for that use. Acceptance of the Selling Terms of Service does not replace acceptance of this document for a separate developer registration, and a Solution Provider's acceptance binds the provider firm in accordance with the Solution Provider Program.
Article 4: Licence Grant
4.1 Subject to this document and to §API Access Tiers–2.7.25, the Company grants the Developer a limited, non-exclusive, non-transferable, revocable licence to access and use the API and developer tools solely to build, test, and operate Applications that interoperate with the Platform.
4.2 The licence is limited to (a) the interfaces and data the Developer's Credentials and access tier authorize, in accordance with the API Access Tiers; (b) the scopes granted to each Credential, in accordance with the API Key Management and Rotation and the OAuth App Registration and Review; and (c) the purpose stated in the Developer's registration.
4.3 The licence does not create a partnership, a joint venture, or an agency. The Developer is not an agent of the Company and shall not represent otherwise. The licence does not constitute an endorsement of an Application.
4.4 The licence covers the API as published. The Company's internal systems, databases, and data services are not licensed under this document. Access that reaches past the published API into an internal system is outside the licence, whether or not the access succeeds. The Developer shall not use a credential issued for internal or service use of the Company, and possession or use of such a credential by the Developer is a material breach of this document and a compromise event under the Breach Notification Requirements.
Article 5: Licence Restrictions
5.1 The Developer shall not: (a) sublicense API access to a third party except through an Application approved under the OAuth App Registration and Review; (b) resell raw API access as a standalone service; (c) use the API to operate a competing marketplace; (d) copy or replicate the Platform catalog or other Platform data for a purpose outside the Application's stated function, which is governed by the Scraping Prohibition; (e) access data of a tenant, a Seller, or an End User other than the tenant, Seller, or End User the Developer's Credentials authorize; (f) forge, alter, or re-create a Credential or a session token, or assist another person to do so; or (g) circumvent a rate limit, an access control, or another technical measure of the Platform.
5.2 The technical rules for API use, including authentication, are stated in the API Policies. The Developer shall comply with the API Policies as technical terms of this licence. A conflict between the API Policies and this document is resolved in favour of this document for the legal obligation, and the Developer shall seek clarification from the Company at support@aapawz.com rather than resolve the conflict unilaterally.
Article 6: Incorporated Program Terms
6.1 The following documents are incorporated into this document by reference and form part of the terms of the licence. The Developer shall comply with each document that applies to the Developer's use: API Access Tiers; API Rate Limits and Quotas; API Key Management and Rotation; OAuth App Registration and Review; Webhook Obligations; Data Use, Retention and Deletion; Scraping Prohibition; SDK License Terms; Solution Provider Program; Automated Access and Agent Disclosure; App Marketplace Terms; App Listing Standards; Partner Revenue Share Policy; Partner Code of Conduct; Partner Security Requirements; Vulnerability Disclosure Policy; Breach Notification Requirements; Deprecation and Breaking Changes Policy; Sandbox Acceptable Use Policy; Partner Suspension, Termination and Appeals; Integration Certification Policy; API Monetization and Usage Fees Policy; Partner Support and Incident Escalation Policy; and Developer Brand and Trademark Use (Developer Brand and Trademark Use Policy).
6.2 Lack of knowledge of an incorporated document is not a defence to breach of it. The Developer shall keep a current record of the incorporated documents that apply to each Application the Developer operates.
Article 7: Data Licence and Its Limits
7.1 Data returned by the API remains the property of the Company, the Seller, or the End User to whom it belongs, as applicable. The API grants the Developer a limited licence to use that data only as the Data Use, Retention and Deletion permits: to provide the Application to the End User who authorized it, and for no other purpose.
7.2 The Developer acquires no ownership interest in data obtained through the API by receiving it, storing it, or computing a result from it. A result the Developer computes from Platform data belongs to the Developer as to its presentation, and the underlying data remains subject to clause 7.1.
7.3 Aggregated and anonymized data derived from API use belongs to the Company. The Developer shall not publish Platform data as a standalone dataset, feed, or interface. Retention, caching, and deletion of data obtained through the API are governed by the Data Use, Retention and Deletion.
Article 8: Developer Obligations
8.1 The Developer is responsible for the acts and omissions of its Applications, its contractors, its subprocessors, and any automated agent it operates, as the Developer's own acts and omissions.
8.2 The Developer shall maintain the integration the Developer operates: the Developer shall follow deprecation notices under the Deprecation and Breaking Changes Policy, shall handle rate-limit responses in accordance with the API Rate Limits and Quotas, shall verify webhook signatures in accordance with the Webhook Obligations, shall meet the Partner Security Requirements, shall give breach notice in accordance with the Breach Notification Requirements, and shall maintain a working incident contact in accordance with the Partner Support and Incident Escalation Policy.
8.3 An Application shall fail safely when the API is unavailable. The Developer shall design the Application to queue, to retry with backoff, and to report its status to its users, rather than to fail silently or to record a partial operation as complete.
8.4 The Developer shall keep records of the Developer's API use, Credentials, data handling, and compliance decisions sufficient to answer an audit under the Data Use, Retention and Deletion and the Partner Security Requirements, and shall produce those records on the Company's request within the period the governing document states.
Article 9: Company Rights
9.1 The Company may monitor, log, throttle, and rate-limit API traffic for security, abuse prevention, and compliance. The Company is not required to give notice before throttling traffic that violates the API Rate Limits and Quotas or that presents a security risk.
9.2 The Company may change, deprecate, or discontinue an element of the API in accordance with the Deprecation and Breaking Changes Policy. Except as that document provides, the form of an interface, a request, or a response is not a contractual commitment.
9.3 Except as the API Access Tiers or the Partner Support and Incident Escalation Policy expressly states, the Company does not guarantee a level of availability for the API.
Article 10: Intellectual Property
10.1 Nothing in this document transfers ownership of the Company's intellectual property. The API design, the data model, the interface structure, the event catalog, and Platform content remain the property of the Company or its licensors.
10.2 The Developer retains ownership of its Application. The Developer grants the Company a royalty-free, worldwide licence to use the Application's name, description, screenshots, and listing assets for directory, certification, and marketplace purposes under the App Marketplace Terms. The Company shall not misrepresent the function of the Application in such use.
10.3 The Developer's use of the Company's names and marks is governed by the Developer Brand and Trademark Use (Developer Brand and Trademark Use Policy). No right to use a Company mark arises from this document except as that document permits.
10.4 Platform content returned by the API, including category, brand, catalog, and pricing data, remains Platform content. The Developer may display that content only inside the Application's stated function.
Article 11: Fees
11.1 Fees for API access, tiers, and usage 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. No other charge of any kind is payable, and the Company shall not impose a fee that that document does not state.
Article 12: Liability
12.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.
12.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).
12.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.
12.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 13: Indemnification
13.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, including an End User whose data the Application accessed; and (d) taxes for which the Developer is responsible under this document.
13.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.
13.3 Survival. This article survives the termination of this document.
Article 14: Enforcement and Appeals
14.1 Investigation. The Company may investigate any suspected violation of this document or of an incorporated document. The Developer shall cooperate with an investigation and shall produce the records this document requires the Developer to keep.
14.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.
14.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 fraud, to scraping in violation of the Scraping Prohibition, to sale or disclosure of Platform data, to circumvention of a technical control, to forgery or theft of a Credential, to a risk to the safety of a person or an animal, to unlawful conduct, or to a violation that by its nature cannot be cured.
14.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) restrict, suspend, or revoke a Credential, a scope, or an access tier, in whole or in part; (c) suspend or remove an Application or a listing; (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. Suspension, termination, and appeals procedure under this article is further governed by the Partner Suspension, Termination and Appeals, which controls for that procedure in the event of a conflict.
14.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.
14.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 15: Term and Termination
15.1 Term. This document takes effect when the Developer registers for developer access or first accesses the API, whichever occurs first, and continues until terminated under this article.
15.2 Termination by the Company. The Company may terminate this document and the Account 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.
15.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 and has completed the deletion duties in clause 15.4.
15.4 Effect of termination. On termination: (a) the licence in Article 4 ends and every Credential is revoked; (b) the Developer shall cease API access and shall delete Platform and End User data in accordance with the Data Use, Retention and Deletion and shall certify deletion as that document requires; (c) obligations that arose before termination, including payment, record-keeping, and indemnification obligations, survive until satisfied; and (d) 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.
15.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, together with Articles 7 and 10.
Article 16: Dispute Resolution
16.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 17: General Provisions
17.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 15 before the amendment takes effect.
17.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.
17.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.
17.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.
17.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.
17.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.
17.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.
17.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.