Skip to content

Partner API Terms ​

Effective date: October 12, 2026 · Version: 2026-10

These Partner API Terms (the "API Terms") apply to your use of the landplan.io Partner API at https://landplan.io/api/partner/v1, together with its documentation, API keys, webhooks and data (together, the "API").

The API is provided by NewSeptic, LLC, doing business as landplan.io ("landplan.io", "we" or "us"). The API Terms add to our Terms of Service and Privacy Policy, which also apply. If the API Terms conflict with the Terms of Service, the API Terms govern for the API. A signed agreement with us, such as an Enterprise contract, governs over both where it says so.

1. Accepting these Terms ​

You accept these API Terms when you ask for API access, issue or use an API key, or call the API. If you accept them for a company or organization, you confirm that you have authority to bind it, and "you" means that company or organization.

2. Access and API keys ​

  1. Your client. We set up an API client for your landplan.io account or your Enterprise organization, with a plan and the scopes you may use. We decide whether to grant, change or turn on live access.
  2. Keys are secret. You are responsible for all use of your API keys and for all fees they incur.
    • Keep keys on your servers. Never put them in web pages, mobile apps or public code.
    • Do not share keys outside your organization.
    • Revoke a key at once if you think it has been exposed, and tell us at support@landplan.io.
  3. Who a key acts as. A key acts as the account or organization it belongs to, with that account's access, and never with landplan.io staff rights. Calls made with your key are treated as your calls.
  4. Test keys are free and return sample output, marked Sample: true. Do not use test output in production or show it to your customers as real results.

3. Permitted use ​

You may use the API to build and run your own applications and services ("Your Applications") that use the API's results, for your business and for your own customers, within your plan and scopes.

4. Restrictions ​

You will not, and will not help anyone else to:

  1. go over or get around your plan's limits, rate limits or quotas, for example by using several clients or keys to avoid them;
  2. resell, sublicense or give access to the API itself, or to your keys, or offer a service whose main purpose is to pass API results through to others as a substitute for the API;
  3. use the API to copy, scrape or build a database of landplan.io's rules, product catalog, prices or other data, or to build a product that competes with landplan.io;
  4. reverse engineer the API or the Service, or test their security, without our written permission;
  5. send data you have no right to send, malware, or requests meant to disrupt or overload the API;
  6. present API results as a stamped design, a soil evaluation, a permit, a quote or a guarantee (section 7); or
  7. use the API in violation of any law, including privacy, consumer protection and anti-spam laws.

5. Fees, units and invoices ​

  1. Plans and units. Live calls use units according to the published price for each operation. They count against your plan's included units, and units beyond them are charged at your plan's overage rate.
    • Units are charged only for successful calls, and once per Idempotency-Key.
    • Test keys are never charged.
    • Plan prices, included units, overage rates and limits are those shown in the Partner API documentation or agreed with you in writing.
  2. Invoices. We invoice monthly for your plan's fee plus any overage units. Invoices are due within 30 days of the invoice date, in U.S. dollars, and do not include taxes, which you are responsible for.
  3. Late payment. If an invoice is not paid when due, we may suspend live keys until it is paid.
  4. Price changes. We may change API prices, units or plans with at least 30 days' notice by email. Changes apply from your next billing month.
  5. Disputes. If you think an invoice is wrong, tell us within 30 days of receiving it. The usage records we keep for each call are used to settle the question.

6. Your data and your customers ​

  1. Your data. You own the data you send through the API ("API Data"). You grant us the same license over API Data that the Terms of Service give us over Your Content. We use API Data to:

    • answer your calls
    • meter and bill your use
    • keep the API secure
    • create aggregated data, as described in the Terms of Service

    We do not sell API Data.

  2. Personal information. If you send personal information, such as names or addresses, you confirm that you:

    • have a lawful basis to send it to us
    • have given any notices the law requires
    • send only what the call needs

    You are responsible for the privacy and security of personal information in Your Applications.

  3. Your customers. You are responsible for Your Applications and for your relationship with your customers. This includes your own terms, privacy notices, support, and any claims about results that you make to them.

7. Results are preliminary ​

  1. Feasibility answers, designs, estimates, product recommendations and market data from the API are automated and preliminary.
    • They are not a soil evaluation, an engineered or stamped design, a permit, a quote, or advice.
    • A licensed designer and the local authority decide what can be built.
  2. You will show your users that results are preliminary, in words with this meaning, wherever you display them.
  3. Results are based on Third-Party Data, including the USDA NRCS soil survey, and on rules that may be incomplete or out of date.
    • Keep the data sources and attributions included in the results.
    • Do not remove the Preliminary flags or similar notices from results you pass on.

8. Caching and storage ​

You may store API results for as long as you need them for Your Applications and your records. However:

  • refresh any result before relying on it for a new decision, because the underlying data and rules change; and
  • do not store results to avoid paying for calls you would otherwise make, or to build a dataset that breaks section 4.

9. Webhooks ​

  1. Webhooks are sent only to the public HTTPS address you give us, signed with your client's signing secret.

  2. You are responsible for:

    • checking each delivery's signature before trusting it
    • keeping the signing secret confidential
    • answering promptly

    We retry failed deliveries for a limited time. After that, the event is available only through the API.

10. Changes, versions and availability ​

  1. Versions. Changes that would break a client get a new API version, such as /api/partner/v2. We may add fields to existing answers at any time, and Your Applications must ignore fields they do not know.
  2. Deprecation. We will give at least 90 days' notice by email before we retire an API version or remove an operation, unless a law, a security risk or a data provider requires a shorter time.
  3. Availability. We work to keep the API available, but we do not promise that it will be uninterrupted or error-free unless a written agreement with you includes a service level.

11. Monitoring, suspension and termination ​

  1. We monitor use of the API to meter it, keep it secure, and check compliance with these API Terms.

  2. We may limit, suspend or revoke your keys, with notice where reasonable, if:

    • you breach these API Terms or the Terms of Service;
    • you do not pay;
    • your use creates a security, legal or performance risk; or
    • an Enterprise organization leaves its plan or becomes read-only.
  3. You may stop using the API and revoke your keys at any time. Fees for use up to that time remain due.

  4. When your access ends:

    • stop calling the API;
    • delete your keys; and
    • stop displaying results as current, except for records you must keep.

    Sections 4 to 8, 11 and 12 continue after access ends.

12. Disclaimers, liability and indemnity ​

  1. The API is part of the Service. The disclaimers, limits of liability and governing-law terms of the Terms of Service apply to it, including Ohio law and the courts of Stark County, Ohio. For the API, the fees in the liability cap include the API fees you paid in the 12 months before the claim.
  2. You will defend, indemnify and hold harmless NewSeptic, LLC from claims arising out of:
    • Your Applications;
    • your use of the API or its results, including what you tell your customers about them;
    • API Data you send; or
    • your breach of these API Terms.

13. Changes to these API Terms ​

We may update these API Terms. If a change is material, we will give you at least 30 days' notice by email before it takes effect. If you keep using the API after that, you accept the updated API Terms.

14. Contact ​

NewSeptic, LLC (landplan.io), 1997 Applegrove St NW, North Canton, Ohio 44720. API questions: support@landplan.io.

Land & Septic Planning Software