Manage custom endpoints over the API, and build against a documented error contract. Learn More
September 09, 2026
/insites/api/v2/endpoints, gated by the instance API key. Every endpoint must carry at least one authorization policy (no public-by-omission), the slug and file path are namespace-validated, inputs are allow-listed, and each change is recorded in the event stream. Documented under the new API section in the API docs.{% function %}, and when to use a controller instead of the HTTP API. Includes explicit guidance for AI assistants so generated on-instance Liquid uses controllers rather than HTTP calls.{API_KEY} placeholder consistently across every endpoint and module..md to a documentation URL now redirects to the real Markdown version instead of returning HTML with a markdown content type. Fixed the CMS, Forms, Permissions, and Stripe reference sections rendering another module's content.params: params named argument, so the example is copy-paste-valid.& in cURL example URLs and example data, instead of an HTML-escaped &.company.name) is documented as returning an error.
September 09, 2026
September 09, 2026
/data/api/v2; the /databases prefix is deprecated.
September 09, 2026
env add now connects to instances on the Insites dedicated stack as well as the shared stack, and works out which one an instance belongs to from its URL.-s, --stack <stack> option on env add to set the stack explicitly when an instance uses a custom domain the CLI cannot classify.env list now shows which stack each environment belongs to.check command: lint your Liquid. check run reports offenses grouped by file with the offending lines shown, exits 1 when anything is found, and supports -a autofix, -c to filter to named checks, -f text|json, and -s for errors only. check init writes a configuration file for disabling checks or changing their severity, and check update-docs refreshes the Liquid documentation the linter validates against.logs command. insites-cli logs <environment> returned "unknown command".logsv2 reports failing with a file-not-found error for every report.logsv2 alerts add failing to send Slack alerts.logsv2 command reporting errors as an empty {}. A missing environment or bad token now prints the real message.insites-cli <command> --help showing the general command list instead of that command's own help.deploy, sync, and modules targeting the wrong Partner Portal for environments on the dedicated stack.env add run reports which stack it selected.logs and logsv2 now have distinct descriptions in the help output.
July 02, 2026
is_percentage_processing_fee flag (default: false / fixed amount). The processing_fee_amount is automatically computed server-side on every save using the order/quote base (subtotal + tax + shipping − discounts, clamped to $0). Applies across the v2 API, CSV import, and quote-to-order conversion.quote_number is now automatically generated from the record ID on creation. The field is no longer required on POST or CSV import.Quotes
items[] flattened to canonical shape; id added to all nested objectsquote_status defaults to Draft when not supplied; enum and reference integrity validation added; quote_contact_id correctly derived; geo_json cascade fixedquote_number now enforceditems[] flattened; id added to nested objectsOrders
items[] flattened to canonical shape; doc examples correcteditems[] flattened in response; *_contact_id fields removed (not in schema); geo_json cascade fixeditems[] flattened in response; order_company correctly marked as not requiredOrder Items
order.uuid now rejectedpage/size required flags corrected; 400 example fixed; nested id fields addedOrder Discounts
id added to nested order and discount objects across GET list, GET single, DELETEOrder Shipping Packages
Payments
id added; stale enum values removed; 404 shape correctedid fixedQuote Discounts
id added to nested quote and discount objectsQuote Items
id added to nested objects in DELETE 200 doc exampleQuote Shipping Packages
page/size correctly marked Optionalid added to nested objectsSystem Fields
Custom Fields
id validation addedConfiguration
livemode rejectedmeasurement_unit and weight_unitFreight Suppliers
page/size correctly marked Optional in GET list docProducts
effective_price is now always computed server-side on create/update and cannot be overridden via the API or CSV importeffective_price on all existing products and variants using paginated queries (500 per page) to avoid table locksid sub-field added to all nested relation objects (order, quote, contact, company, discount, product, product variant) across orders and quotes v2 API responses and doc examplesIs Percentage Processing Fee columnitems[] on orders and quotes has been flattened from { id, properties: { uuid, ... } } to a flat object { id, uuid, ... } across all endpoints (GET list, GET single, POST, PATCH, DELETE). Any client reading item.properties.* will break.quote_number is now required on quotes PATCH.*_contact_id fields removed from Orders POST — these were not in the order schema and are no longer accepted.processing_fee_amount is now server-computed on every save. Any client-supplied value is ignored and overwritten. Clients should stop sending this field and read it back from the response.effective_price — effective_price on products and product variants now always stores the ex-tax active list price. Previously it stored the raw sale_price or regular_price regardless of tax-inclusive flags.
is_tax_included, is_sale_price_tax_included, or is_variant_sale_price_tax_included set to true will see effective_price change after the backfill migration runs.effective_price will reorder. Re-test any storefront listing, sort, or price-range filter that reads this field.effective_price is read-only. It is computed server-side on every create/update; values sent in POST/PATCH bodies or CSV imports are ignored and overwritten — read it back from the response.total_price is unchanged. It stays tax-inclusive.Insites is an Application Development Platform that brings together all the tools and building blocks in one platform, allowing you to easily create engaging and sophisticated applications in lighting speed.
The Insites Console is the starting point and home for all the projects you build with Insites. You can manage all your applications from this central location, creating both Staging and Production Instances. Invite your team to collaborate on projects together, manage billing, install Apps from the Marketplace, and find Insites experts from the Partner Directory.
To get started with Insites, follow this step-by-step guide that takes less than ten minutes. We can’t wait to see what you create!
Your journey with Insites starts with the creation of an Insites Console account. Go to https://console.insites.io/sign-up to create your account. After providing your details, check your email inbox for an account activation email and click on the 'Activate Account' link. Clicking on the link verifies and activates your Insites account and opens the Insites Console.
Invite your team to collaborate with you and leverage their skills and expertise to build, support, and improve applications hosted on Insites. To add your teammates to the Insites Console, go to the 'People' tab and select + Invite User. They will receive an email invitation and simply need to accept and create a password.
For each of your applications you can create instances in one of two environments, Staging or Production. Create multiple instances per application to follow your development standards. For example, use staging Instances to develop and test applications, then push to a production Instance.
To create an Instance, go to the 'Instances' tab within the Console and click on the + Create Instance button and fill out the relevant details. To keep projects organized and manage permissions for your team you can group instances together in folders.
You can start your application from scratch or leverage pre-built templates and Apps from the Marketplace.
For many situations, it may be faster and more cost-effective to buy an application and then customize it, rather than build it from the ground up.
To install an App, navigate to the 'Marketplace' tab within the Console and select Purchase on the relevant App. You can install multiple Apps on an Instance, and installation only takes a few minutes.
Well done on completing the steps and getting started with Insites. We are excited to have you onboard. You can view our detailed documentation at https://docs.insites.io and API Docs at https://apidocs.insites.io. If you need assistance our friendly support team are on standby for any questions you may have.
Don’t forget to check out the Insites Partner Directory for expert help with any of your applications, or if you are interested in selling your Applications on the marketplace contact us for details. Have a great day and build something special!
Didn't quite find what you are looking for or have feedback on how we can make the content better then we would love to hear from you. Please provide us feedback and we will get back to you shortly.