Effective October 28, 2026

These API Terms apply to your use of the FieldStacker application programming interface, API keys and webhooks (together, the "API"), operated by Kiwi Alarms LLC ("the Company"). They add to our Terms of Service and Privacy Policy, which also apply. If these API Terms and the Terms of Service conflict, the Terms of Service win, except on the API-specific points covered here. You accept these API Terms when you create an API key, and by using the API. Like our Terms of Service, this page is a general template provided for transparency and is not legal advice.

1. What the API is for

The API lets a business connect its own FieldStacker account to its own systems: its CRM, website, accounting, internal tools, or its own automations in tools such as Zapier or Make. That is the only purpose it is offered for.

You may not, without our written permission:

build, sell or distribute an app, product, plugin, integration or service that other businesses use with FieldStacker;
use the API on behalf of other FieldStacker accounts, or as an agency or reseller managing several accounts;
use the API to build a product that competes with FieldStacker;
white-label FieldStacker, or embed FieldStacker data in a product or service offered to others.

Contractors. A developer or contractor you hire may build an integration for your business, using your business’s own key, for your business only. You are responsible for what they do with it.

We may revoke keys that are used in any of the ways listed above.

2. Eligibility and your keys

You need a FieldStacker account in good standing. Only the business owner can create a key.
Keys are issued per business and work only with that business’s data. Keep them secret: don’t put them in web pages, apps or public code, and don’t share them outside your business and the people working on its systems.
Your business is responsible for everything done with its keys. If a key may have been exposed, generate a new one in Settings → API & webhooks (which turns the old one off) and tell us at support@fieldstacker.com.

3. Acceptable use

Rate limits apply. Stay within the published limits and don’t try to get around them, for example with several keys.
Your own data, used normally. No scraping, and no bulk export beyond the normal use of your own data in your own systems.
No reselling. You may not resell, sublicense, rent or give others access to the API or a key.
No unlawful messages. You may not use the API, or data from it, to send unsolicited texts or emails, or in a way that breaks the Telephone Consumer Protection Act, CAN-SPAM, Do-Not-Call rules, privacy laws, or any other law that applies to how you contact people.
Your account only. No attempting to reach another account’s data, other keys, or parts of the Service you don’t have access to.
No testing on us without permission. No load testing, security testing, vulnerability scanning or penetration testing of the API or the Service without our written permission. If you find a security problem, please email us.
The acceptable use rules in our Terms of Service apply to the API too.

4. Your data and your customers

You own your data, as our Terms of Service say. When you send your customers’ information from FieldStacker to another system, or into FieldStacker from another system, you are responsible for having their consent and any other legal basis that requires, and for how that other system uses it. Tools and services you connect are third-party services under their own terms and privacy policies; we are not responsible for them, for what they do with data you send them, or for their availability.

5. Webhooks

You choose where your webhooks send data and control that address. Use an address you trust and secure, and check each delivery’s signature. We may pause a webhook that keeps failing, that answers that it is gone, or that puts the Service at risk, and we will tell you in the app when we do.

6. Changes and versioning

The API is versioned (the current version is v1). We will try to give reasonable notice before a change that would break an integration that follows these terms and the documentation, where that is practical. We may add to the API at any time, and we may change or discontinue endpoints, fields, events or limits, including when security, the law or a provider we depend on requires it.

7. Suspension

We may revoke keys, pause webhooks, or suspend or limit API access, with or without notice, for abuse, a breach of these API Terms or the Terms of Service, a security risk, conduct that puts the Service or other users at risk, or non-payment. When an account is switched off or its plan ends, its API keys stop working.

8. No warranty and limitation of liability

The API is part of the Service and is provided "as is" and "as available", without warranties of any kind, as set out in section 10 of the Terms of Service. The limitation of liability in those Terms applies to the API, to webhooks, and to any data sent through them.

9. Changes to these API Terms

We may update these API Terms from time to time. Material changes will be posted here with a new effective date, and we may ask you to accept them again before you make a new key. Continuing to use the API after a change means you accept the revised API Terms.

10. Contact

Questions about these API Terms, or asking for written permission for a use listed above? Email support@fieldstacker.com.

API Terms