API & webhooks
Beyond the no-code integrations in the Integrations Hub, TriostackOne offers two webhooks and four APIs for connecting your own systems. The Website Webhook is on the Leads tab of the CRM Integrations Hub; the Appointment Webhook and the Invoicing, Tickets, Blogs, and Expense APIs are on the Others tab. All six are included on every CRM plan.
This page explains what each one is for, so you can choose the right one. Endpoint, authentication, and payload details aren't published publicly — contact the team for the technical specification for your workspace before you start building.
Before you start
- Admin access to Triostack CRM, to enable the integration.
- A server-side environment to run your integration — never call TriostackOne with credentials from browser or mobile app code.
- The technical specification for the integration you're building, requested from the team.
1. Website Webhook — leads into CRM
Sends form submissions from your website into the CRM as leads, through a configurable webhook. Use it when your website isn't built on Triostack Website (where forms feed CRM natively). Leads arrive alongside those from every other source, so the sales team works them in the same pipeline.
2. Appointment Webhook — bookings into the CRM calendar
Syncs appointment and meeting bookings from external scheduling tools into the CRM calendar, so every demo and meeting sits next to the lead or customer it belongs to. If your team schedules in Google Calendar, use the Google Calendar integration instead.
3. Invoicing API
Manages invoicing through connected third-party invoicing sources alongside CRM-native invoices — for businesses that raise some invoices outside TriostackOne but want them visible with the rest.
4. Tickets API
Connects helpdesk and ticketing so customer support cases stay linked to their CRM record — giving sales and account teams visibility of open support issues.
5. Blogs API
Manages blog content published through Triostack BMS (Blog Management Service) from within the CRM. For reference, the blog on this website is powered by BMS: posts are written and published in BMS, and the site reads them server-side from the BMS integration API, authenticating with a secret API key sent as a Bearer token.
6. Expense API
Creates and tracks expense records connected to your CRM workspace, for teams that capture expenses in another system.
7. Getting the technical specification
Contact the team through the Contact page, email info@triostack.in, or call +91-8882435276. Tell us which integration you're building, the system you're connecting, and the direction data needs to flow. We'll confirm the right approach for your use case and share the current technical reference.
Best practices
- Keep API keys and secrets server-side only — in environment variables or a secrets manager, never in front-end code or a public repository.
- Rotate a key immediately if it may have been exposed, and give each integration its own key so one can be revoked without breaking the others.
- Validate and sanitize anything your system sends in, and log failures so problems are visible.
- Treat any API call that fails as retryable only when it's safe to repeat — avoid creating duplicate leads or invoices on retry.
Frequently asked questions
Is there a public REST API for every app?
Not today. The available programmatic integrations are the Website and Appointment webhooks and the Invoicing, Tickets, Blogs, and Expense APIs. Connections between TriostackOne apps are native and need no API.
Where are the endpoint and authentication details?
They aren't published publicly. Contact the team for the technical specification for your workspace.
Do the APIs cost extra?
They're part of the CRM Integrations Hub, which is included on every CRM plan, including the free trial.