AlignBooks is a cloud accounting and ERP product from Align Info Solutions Pvt. Ltd., aimed at Indian small and mid-sized businesses. It covers sales invoicing, purchase, finance and GST, inventory with batch and serial tracking, point of sale, payroll, job work, discrete production, asset tracking and CRM, with an add-on marketplace storefront and a mobile selling app called AlignCart. For a retailer or distributor running it, AlignBooks holds the sales invoices, item master, stock by branch and warehouse, customer ledger and receipts.
AlignBooks advertises a developer API and sells it as a plan feature, which is more than most vendors in this part of the catalogue do. What it does not do is publish anything about it: no developer portal, no endpoint list, no authentication guide, no SDK and no Postman collection could be found. The practical finding is that an API exists, that it is gated to the most expensive plan, and that the contract has to come from the vendor.
At a glance
The useful commercial fact for scoping: on the published plan comparison read on 2026-09-22, API Integration is ticked only for the ERP and Enterprise plan and crossed for Basic, Premium, Ultima, Certified Professional and Education. If the brand is on anything below that plan, the first step is a plan upgrade, not an integration call. Shopify and WooCommerce integration is a separate row and is ticked for the ERP and Enterprise plan as well as the Certified Professional and Education plans.
What it is
Align Info Solutions Pvt. Ltd. sells AlignBooks as a true cloud product with a desktop and mobile companion. The web application runs at solution.alignbooks.com as an Angular single page application, with related hosts for CRM (crmservice.alignbooks.com), payments (payment.alignbooks.com), customer and vendor self service (cvss.alignbooks.com), training (learn.alignbooks.com) and support (care.alignbooks.com). Document print formats are served separately from docs.alignbooks.in on port 9701.
The plan ladder is Basic, Premium, Ultima and ERP with Enterprise, plus free Certified Professional and Education tiers. Plans are also capped by document volume: the published comparison shows a maximum of 1,200 business to business sales invoices a year on Basic rising to 20,000 on the ERP and Enterprise plan, read on 2026-09-22. That cap matters for any integration that will post documents, since a connector can burn the allowance quickly.
Two first party products sit next to the core and are relevant because they are the vendor's own answer to the commerce question. AlignBooks Marketplace is an add-on storefront where "all product details, product groups, brands, pricing, discounts will be automatically populated into your store" and "any orders placed in the Marketplace will be available in AlignBooks and dispatch/billing will automatically be updated". AlignCart is a mobile storefront app with the same synchronisation story, including stock levels, GST and Razorpay or Paytm payments. Both demonstrate that inbound order creation and outbound catalogue and stock reads exist internally.
API access
There is no developer signup, no console and no published key issuance flow. What is known:
- The feature exists and is named. The AlignBooks features page lists "Open Developer API: Enhance available functionalities and your operational controls by developing your own applications and integrating them through two-way APIs."
- It is plan-gated. The published price list shows API Integration on the ERP and Enterprise plan only.
- The route to it is the vendor or a certified partner. AlignBooks maintains a certified partner and certified professional network with published directories, and routes customisation through them.
What was checked and found absent, on 2026-09-22:
- No
api,docs,developerorhelpsubdomain ofalignbooks.comresolves. A certificate transparency search returns only the apex and a wildcard, so no developer host has ever been issued a certificate under that domain. alignbooks.com/Views/documentation.htmllinks only to end user PDF manuals: Adjustment Journal, Chart of Accounts, Receipt and Payment Voucher, Transfer Journal, Branch Issue, Branch Issue Receipt, Branch Issue Request, Item Master, Material Issue, Material Receipt, Stock Adjustment, Customer Master, Sales Credit Note, Sales Debit Note, Sales Dispatch, Sales Estimate, Sales Invoice, Sales Payment Receipt, Sales Price List, Sales Return, and the setup guides. Useful as an object inventory, useless as an API reference.- Postman public search returns no AlignBooks collection and no request against any AlignBooks host.
- GitHub has no AlignBooks owned organisation, repository or SDK.
- The Wayback Machine holds no archived AlignBooks URL containing "api".
- The web application's JavaScript bundle references only AlignBooks' own application hosts and does not expose a documented API base path.
No API version, deprecation policy or SDK is published in any language.
Authentication
Not published. No token endpoint, header name, key format, scope model or lifetime has been made public by AlignBooks or any third party, and none can be stated here without inventing it.
What can be said safely: because AlignBooks is genuinely multi-tenant cloud rather than per-customer on-premise, expect a single shared API host and a per-tenant credential, which is a better starting position than the on-premise Indian ERPs in this catalogue. Expect the credential to be issued inside the product's user or setup area on the ERP and Enterprise plan. Confirm both with the vendor.
Multi-account handling, for several selling entities, is unknown. AlignBooks supports multiple branches and multiple financial years within a subscription, so ask specifically whether an API credential is scoped to a company, a branch or a subscription.
Objects we can read
No endpoint is published for any object. What follows is the object inventory taken from AlignBooks' own user documentation and module pages, so that a scoping call can ask for the right things by the vendor's own names.
Orders
Sales Estimate, Sales Order and Sales Dispatch are distinct documents, separate from the invoice. The plan comparison lists "List Based Estimates", "Order" and "Dispatch" as sales management features.
Order items and invoices
Sales Invoice is the billing document, with bill to bill payment matching, multiple price and discount lists, salesman or agent based billing, dimension based billing and time sheet based billing depending on plan. GST and e-invoice generation against the government invoice registration portal are built in on the higher plans.
Products and listings
Item Master, with pre-configured item and SKU support, inventory attributes, batch and serial wise inventory, and multiple units. Sales Price List is a separate document type, so price lives in its own object rather than only on the item.
Inventory
Stock by branch and warehouse. Material Receipt, Material Issue, Stock Adjustment, Branch Issue, Branch Issue Request and Branch Issue Receipt are the movement documents. Multi branch and warehouse are plan-gated features.
Returns and cancellations
Sales Return, Sales Credit Note and Sales Debit Note, each a separate document with its own user manual.
Payments and settlements
Sales Payment Receipt, Receipt and Payment Voucher, Journal Voucher, Expense Journal, and bill to bill payment matching. There is no marketplace settlement object; settlement data would have to come from the channel.
Customers
Customer Master, plus a customer and vendor self service portal at cvss.alignbooks.com on the higher plans. All customer fields are PII.
Locations
Branches and warehouses, capped by plan: the published comparison shows a maximum of five branches or locations on Ultima and ten on the ERP and Enterprise plan, read on 2026-09-22.
Sample responses are not published for any of these, and no field name can be quoted, because AlignBooks has never published one.
Writing back: listings, price and stock
For AlignBooks, read this as pushing sales orders, invoices and stock adjustments in.
The vendor's own wording is "two-way APIs", which asserts that writes are supported. The strongest indirect evidence is AlignBooks Marketplace and AlignCart: both take customer orders outside the ERP and land them in AlignBooks, with dispatch and billing flowing back, which means an inbound order path exists in the product. Shopify and WooCommerce also appear as plan features, which means AlignBooks already operates a connector that writes external orders into the ledger.
What is not published: the endpoint, the request body, which document types accept a write (sales order, sales invoice, stock adjustment, material receipt), batch sizes, idempotency and how a write is confirmed. None of that can be stated here.
Two practical cautions for whoever scopes this:
- Document volume is metered per plan. A write connector consumes the sales invoice allowance. Establish the cap and the overage terms before designing a posting frequency.
- Stock should move through the stock adjustment and material movement documents, not through a hypothetical "set stock" call. Ask for those document types by name.
If no API is available on the customer's plan, the documented fallbacks are the product's own data import feature, which appears as a plan row, and the Shopify or WooCommerce connector where the channel matches.
Webhooks and notifications
Nothing published. No event catalogue, no subscription mechanism, no signature scheme and no retry policy. Email notification appears in the plan comparison, but that is user notification inside the product, not a machine callback.
Until the vendor says otherwise, plan for polling. Because AlignBooks is a shared multi-tenant cloud, a poll is cheaper and safer than it would be against an on-premise installation, but a sensible starting cadence is still every 15 minutes for sales documents, hourly for stock and daily for masters, and it must be agreed with the vendor once real limits are known.
Rate limits and pagination
Not published. No quota number, no header, no page size and no cursor model has been made public.
The only published numbers that behave like limits are commercial rather than technical: the per-plan annual caps on business to business and business to consumer sales invoices, and the per-plan caps on users and branches. Treat those as the real constraint until the vendor supplies a technical one.
Mapping to the unified model
No AlignBooks field name has ever been published, so no mapping table can be given with real field names. The table below maps unified fields to AlignBooks document and master names so that a vendor conversation can be specific. Every right-hand cell is a document or master name, not a field name.
Gaps and open questions
- Everything technical is unverified. The existence of the API rests on two first party marketing statements and one plan comparison row. No endpoint, header or field name has ever been published by anyone.
- Whether the API is REST with JSON is an inference from the product's architecture, not a fact.
- Whether API access on the ERP and Enterprise plan is included or charged as an extra is not stated on the price list.
- Whether API-created documents count against the plan's annual invoice caps is unknown and is a material commercial question.
- The credential scope, company, branch or subscription, is unknown.
- Whether a sandbox or test company exists separately from the free trial is unknown.
- No rate limit, pagination model or error format is published.
- The Shopify and WooCommerce integration is listed as a plan feature but its mechanism is not described anywhere. If a brand needs only those two channels, that route may be shorter than a custom integration and is worth pricing first.
- AlignBooks has a certified partner network. A partner who has already built against the API is likely to be the fastest source of a real contract, faster than the vendor's sales channel.
Sources
- AlignBooks features page, read 2026-09-22. Source of the "Open Developer API" and "two-way APIs" statement
- AlignBooks price list and plan comparison, read 2026-09-22. Source of the API Integration plan gating, the Shopify and WooCommerce gating, and the per-plan invoice, user and branch caps
- AlignBooks documentation index, read 2026-09-22. Source of the document and master inventory
- AlignBooks Marketplace page, read 2026-09-22. Source of the statement that marketplace orders land in AlignBooks and that dispatch and billing flow back
- AlignCart page, read 2026-09-22
- AlignBooks enterprise page, read 2026-09-22, which identifies the application host
solution.alignbooks.com - AlignBooks sitemap, read 2026-09-22
- DNS and certificate transparency checks on 2026-09-22: no
api,docs,developerorhelphost underalignbooks.com; certificate transparency returns only the apex and a wildcard - Postman public search for
alignbooks, run 2026-09-22: no collection and no request - GitHub repository and code search for
alignbooks, run 2026-09-22: no vendor owned repository or SDK - Wayback Machine index for
alignbooks.com, queried 2026-09-22: no archived URL containing "api"