--- title: Accelo API Integration on Truto slug: accelo category: CRM canonical: "https://truto.one/integrations/detail/accelo/" --- # Accelo API Integration on Truto **Category:** CRM **Status:** Beta ## Unified APIs ### Unified CRM API - **Accounts** — The accounts represent a company in a CRM. - **Contacts** — The contacts represent an existing point of contact at a company in a CRM. - **Opportunities** — The opportunities represent an opportunity in a CRM. - **Tasks** — The tasks represent a task in a CRM. - **Users** — The users represent a user in a CRM. ### Unified User Directory API - **Groups** — Groups are a collection of users in the source application. In some applications, they might also be called Teams. - **Me** — - **Users** — The User object represents a User. ### Unified Ticketing API - **Accounts** — Accounts represent the companies or organizations that you are in contact with. Accounts have one or more Contacts associated with them. - **Attachments** — Attachments are the files associated with a ticket or a comment. - **Comments** — Comments represent the communication happening on a Ticket, both between a User and a Contact and the internal things like notes, private comments, etc. A Ticket can have one or more Comments. - **Contacts** — Contact represent the external people you are in contact with. These could be customers, leads, etc. Contacts can be associated with an Account if the underlying product supports it. - **Ticket Priorities** — Ticket Priorities represent the intended order in which the Tickets should be worked on. Some products provide customizing the Ticket Priorities. - **Ticket Status** — Ticket Status represents the completion level of the Ticket. Some products provide customizing the Ticket Status. - **Ticket Types** — Ticket Types represent the classification system used by the underlying products for Tickets. Some examples are bugs, feature, incident, etc. - **Tickets** — Core resource which represents some work that needs to be carried out. Tickets are usually mapped to issues, tasks, work items, etc. depending on the underlying product. - **Workspaces** — Workspaces represent the top-level subdivision in a ticketing system. They usually have their own set of settings, tickets, statuses, priorities and users. Some of the usual terminologies used by the products for the top-level subdivision are projects, bases, spaces, workspace, etc. A Workspace could belong to an Organization. ## How it works 1. **Link your customer's Accelo account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Accelo.** The Proxy API is a 1-to-1 mapping of the Accelo API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync CRM data between your product and your customers' Accelo accounts** — If your SaaS product manages client relationships, proposals, or sales pipelines, you can use Truto's Unified CRM API to pull and push Accounts, Contacts, and Opportunities from Accelo — letting your users keep their PSA in sync without manual data entry. - **Create and manage support tickets in Accelo from your platform** — SaaS companies building AI support agents, client portals, or monitoring tools can use Truto's Unified Ticketing API to create Tickets in Accelo, attach Comments with full context, and map them to the correct client Account — so your users' service teams never miss an issue. - **Pull task assignments to power external productivity or time-tracking tools** — If your product helps teams track time or manage developer workflows, you can fetch Tasks assigned to specific users from Accelo via Truto's Unified CRM API, enabling your users' staff to work in your tool while keeping Accelo's billing and utilization data accurate. - **Build white-labeled client portals backed by Accelo data** — SaaS products offering branded client portals can pull active Tickets, Tasks, and Account details from Accelo so agencies and service firms can give their end-clients real-time visibility into project status and support requests without exposing their backend system. - **Automate deal-to-delivery handoffs from proposal software** — CPQ and proposal tools can update Opportunities in Accelo to 'Closed/Won' when a deal is signed, triggering Accelo's built-in automation to spin up projects and notify delivery teams — turning your product into the starting point of your users' entire service workflow. ## What you can build - **Two-way Account and Contact sync** — Keep company and contact records in sync between your product and your users' Accelo accounts using the Unified CRM API's Accounts and Contacts resources. - **Automated ticket creation from external events** — Create Tickets in Accelo with full context — including Comments and Account mapping — whenever an event occurs in your platform, such as a failed monitor check or an unresolved chatbot conversation. - **Opportunity status updates on deal close** — Push Opportunity stage changes back to Accelo when a proposal is signed or a deal closes in your product, triggering downstream project delivery workflows inside Accelo. - **User directory lookup for assignment mapping** — Fetch staff members from Accelo via the Unified User Directory API to map task and ticket assignments between your platform and your users' Accelo workspace. - **Real-time ticket status dashboard** — Pull Ticket Statuses, Ticket Priorities, and active Tickets from Accelo to render a live support queue or client-facing status view inside your product. - **Contextual activity logging on tickets** — Push Comments (activities) to Accelo Tickets so that chat transcripts, notes, or time entries captured in your product appear as a full audit trail inside your users' Accelo service module. ## FAQs ### What authentication method does Accelo use? Accelo's API uses OAuth 2.0 for authentication. Truto handles the full OAuth flow — including token refresh — so your end users can securely connect their Accelo accounts without you managing credentials. ### Which Truto Unified APIs are available for Accelo? Accelo is supported through three Unified APIs: the Unified CRM API (Accounts, Contacts, Opportunities, Tasks, Users), the Unified User Directory API (Groups, Me, Users), and the Unified Ticketing API (Accounts, Attachments, Comments, Contacts, Ticket Priorities, Ticket Status, Ticket Types, Tickets, Workspaces). ### Are there native Truto tools available for Accelo? No pre-built tools are available yet. Truto builds tools on request, so if you need specific API operations beyond what the Unified APIs cover — such as Accelo's project, retainer, or invoicing endpoints — you can request them. ### Does Truto handle Accelo's API pagination and rate limits? Yes. Truto abstracts away pagination and rate-limit handling for Accelo's REST API, so you can fetch complete datasets without writing retry logic or cursor management code. ### Can I access custom fields on Accelo objects through Truto? Truto's Unified APIs return standard fields across all integrations. For Accelo-specific custom fields, contact the Truto team to discuss proxy or passthrough access to the underlying Accelo API. ### What operations are supported — read-only or read-write? Truto's Unified APIs generally support both read and write operations. You can list and create Accounts, Contacts, Opportunities, Tasks, Tickets, and Comments. The exact supported operations per resource are documented in Truto's API reference.