Skip to content

Helpdesk

Jitbit
API integration

Ship Helpdesk features without building the integration. Full Jitbit API access via Proxy, normalized data through Unified APIs, and 60+ MCP-ready tools for AI agents — all extensible to your exact use case.

Talk to us
Jitbit

Use Cases

Why integrate with Jitbit

Common scenarios for SaaS companies building Jitbit integrations for their customers.

01

Embed helpdesk context inside your CRM

Give account executives and CS managers a live view of a customer's Jitbit tickets on their contact record, so they walk into calls knowing about open issues before pitching renewals or upsells.

02

Power an AI support copilot for Jitbit teams

Let your AI product read incoming tickets, draft replies, and post them as internal 'For Techs Only' comments — giving Jitbit-using support teams AI assistance without changing their existing workflow.

03

Automate MSP time-tracking and invoicing

Pull granular time-spent logs from Jitbit tickets and roll them up by company, so your billing or PSA product can generate accurate monthly invoices for MSPs and IT consultancies.

04

Sync device inventory into support workflows

Push hardware from your RMM or device management platform into Jitbit as assets, assign them to the right users, and attach them to tickets so IT agents see device context the moment a ticket is filed.

05

Link support tickets to engineering work

Connect your issue tracker or project management tool to Jitbit so customer-reported bugs can be linked, sub-ticketed, and tagged — closing the loop between support and engineering.

What You Can Build

Ship these features with Truto + Jitbit

Concrete product features your team can ship faster by leveraging Truto’s Jitbit integration instead of building from scratch.

01

Two-way ticket sync

Create, update, search, and close Jitbit tickets from your product using the ticket endpoints, keeping status, priority, assignee, and custom fields aligned in both systems.

02

AI-drafted internal replies

Post AI-generated response drafts as internal comments with ForTechsOnly enabled, so technicians see suggestions without exposing them to end users.

03

Customer 360 ticket widget

Resolve a Jitbit user by email or username and render their open ticket count, history, and company mapping inside your CRM or customer success UI.

04

Billable-hours rollup for MSPs

Aggregate time-spent entries across tickets by company and technician to feed invoicing, reporting, and utilization dashboards.

05

Asset provisioning pipeline

Create assets from your RMM, assign them to users, and automatically attach the right device to any ticket the user opens.

06

Custom field automation

Read available ticket, user, and asset custom fields, then set them individually or in bulk to drive routing, categorization, and enrichment logic from your platform.

SuperAI

Jitbit AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

list_all_jitbit_authorization

Test Jitbit authentication by verifying the current user's credentials. Returns the authenticated helpdesk user object including UserID, Username, Email, FirstName, LastName, IsAdmin, IsTech, IsManager, and LastSeen.

list_all_jitbit_tickets

List Jitbit helpdesk tickets with optional filters by category, status, date, assignee, tag, and more. Returns: UserName, FirstName, LastName, UserID, CompanyID, CompanyName, Email, Username, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Max 300 per page.

get_single_jitbit_ticket_by_id

Get details of a single Jitbit ticket by id. Returns: Attachments, Tags, Status, OnBehalfUserName, SubmitterUserInfo, CategoryName, AssigneeUserInfo, TicketID, UserID, AssignedToUserID, IssueDate, Subject, Body, Priority, StatusID, CategoryID, DueDate, ResolvedDate, StartDate, TimeSpentInSeconds, UpdatedByUser, UpdatedByPerformer, UpdatedForTechView, IsCurrentCategoryForTechsOnly, Username,…

create_a_jitbit_ticket

Create a new ticket in Jitbit. Returns the created ticket ID. Required: categoryId, body, subject, priorityId.

update_a_jitbit_ticket_by_id

Update one or many ticket parameters in Jitbit by id. Returns an empty 204 response on success. Required: id. Subject and body are editable by admins or technicians only.

jitbit_tickets_add_secondary_assignee

Add a secondary assignee to a Jitbit ticket. Returns an empty 204 response on success. Required: ticket_id, user_id.

jitbit_tickets_close

Close a Jitbit ticket by id. Offers an option to close silently without sending email notifications. Returns 200 OK on success with no response body. Required: ticket_id.

jitbit_tickets_search

Search Jitbit tickets by text query with optional filters for creator, category, status, assignee, and date range. Returns: IssueID, Priority, StatusID, IssueDate, Subject, Status, UpdatedByUser, UpdatedByPerformer, CategoryID, UserName, Technician, FirstName, LastName, DueDate, TechFirstName, TechLastName, LastUpdated, UpdatedForTechView, UserID, CompanyID, CompanyName, AssignedToUserID,…

jitbit_tickets_merge

Merge two Jitbit tickets together. The secondary ticket is merged into the primary ticket and the original secondary ticket is deleted. This action is irreversible. Returns 200 OK on success with no response body. Required: ticket_id, secondary_ticket_id.

jitbit_tickets_link

Link two Jitbit tickets together as related. Returns 200 OK on success with no response body. Required: ticket_id, other_ticket_id.

jitbit_tickets_unlink

Unlink two related Jitbit tickets. Returns 200 OK on success with no response body. Required: ticket_id, other_ticket_id.

jitbit_tickets_add_subticket

Make one Jitbit ticket a subticket of another by linking a child ticket to a parent ticket. Returns an empty 204 response on success. Required: parent_ticket_id, child_ticket_id.

jitbit_tickets_remove_subticket

Remove a subticket relationship from a Jitbit ticket by child ticket ID. Returns an empty 204 response on success. Required: child_ticket_id.

jitbit_tickets_list_linked

List tickets linked as related to a given Jitbit ticket. Returns: TicketID, Subject, StatusID, UpdatedByUser, UpdatedByPerformer, CompanyID, UserID, Username, FirstName, LastName, IssueDate, Email, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id.

jitbit_tickets_list_subtickets

List first-level subtickets for a given Jitbit ticket. Returns: IssueID, Priority, StatusID, IssueDate, Subject, Status, UpdatedByUser, UpdatedByPerformer, CategoryID, UserName, Technician, FirstName, LastName, DueDate, TechFirstName, TechLastName, LastUpdated, UpdatedForTechView, UserID, CompanyID, CompanyName, AssignedToUserID, ResolvedDate, SectionID, Category, Origin, Email, HasChildren,…

jitbit_tickets_get_parent

Get the parent ticket of a given Jitbit ticket. By default returns the parent ticket ID as plain text (zero if none found); with return_full_ticket set to true, returns the full ticket JSON including TicketID, Subject, Body, Status, Priority, IssueDate, CategoryID, AssignedToUserID, and Attachments. Required: ticket_id.

jitbit_tickets_add_tag

Add a tag to a Jitbit helpdesk ticket. The tag can be new or existing. Returns 200 OK on success with no response body. Required: tag_name, ticket_id.

list_all_jitbit_stats

Get overall statistics for the Jitbit ticketing system, including counts of open, closed, new, unassigned, and unanswered tickets. Returns: TotalTickets, Closed, InProcess, NewTickets, Unanswered, Unassigned, Unclosed, HandledByMe, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech,…

list_all_jitbit_priorities

List all Jitbit ticket priorities, including standard and custom ones. Returns: PriorityID, Name, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager.

list_all_jitbit_companies

List all companies in Jitbit. Returns: CompanyID, Name, EmailDomain, Notes, UserID, Username, Email, FirstName, LastName, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager.

jitbit_ticket_custom_fields_set

Set a single custom field value on a Jitbit ticket. Returns an empty 200 response on success; an error message is returned otherwise. Required: ticket_id, field_id, value. For checkboxes pass true or false, for dropdowns pass the option ID, for dates pass a date string in any format.

jitbit_ticket_custom_fields_set_many

Set multiple custom field values on a Jitbit ticket in one request. Returns 200 OK on success with no response body; an error message is returned otherwise. Required: ticket_id. Pass each custom field as a cf key (e.g., cf1624) with its value in the request body.

list_all_jitbit_ticket_custom_fields

List all custom fields and their values for a Jitbit ticket. Returns: FieldName, FieldID, Type, UsageType, Value, ValueWithOption, Mandatory, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id.

list_all_jitbit_attachments

List all file attachments for a Jitbit ticket. Returns: FileName, FileID, FileSize, IssueID, UserID, Url, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id.

create_a_jitbit_attachment

Attach a file to a Jitbit ticket via multipart form upload. Returns: FileName, FileID, FileSize, IssueID, UserID, Url, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id, uploadFile.

delete_a_jitbit_attachment_by_id

Delete a file attachment from a Jitbit ticket by file ID. Returns an empty 204 response on success. Required: id.

jitbit_attachments_download

Downloads a specific attachment file using the file's direct path, which is typically provided in the response of the message listing endpoint. The actual path must be replaced with the URI or download link of the attachment.

jitbit_ticket_subscribers_add

Add a new subscriber to a Jitbit helpdesk ticket. Returns an empty 200 response on success. Required: ticket_id, user_id.

jitbit_ticket_subscribers_remove

Remove a subscriber from a Jitbit helpdesk ticket. Returns a 200 OK response on success with no response body. Required: ticket_id, user_id.

list_all_jitbit_ticket_subscribers

List subscribers for a Jitbit helpdesk ticket. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: ticket_id.

list_all_jitbit_categories

List all Jitbit helpdesk categories the current user has permissions to see. Returns: CategoryID, Name, SectionID, Section, NameWithSection, ForTechsOnly, FromAddress, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager.

jitbit_categories_list_techs

List all possible assignees (technicians) for a Jitbit helpdesk category. Returns: UserID, Username, FirstName, LastName, TicketsAssigned, FullNameAndLogin, FullName, Email, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: category_id.

create_a_jitbit_category

Create a new Jitbit helpdesk category. Returns the resulting category ID as a plain text integer with a 200 OK response. Required: name.

list_all_jitbit_ticket_templates

Get the ticket template (pre-filled subject and body) for a category in JitBit. Returns: Subject, Body, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Returns null if no template is configured for the category. Required: category_id.

list_all_jitbit_category_custom_fields

List all custom fields available in a Jitbit ticket category, including dropdown options. Returns: FieldName, FieldID, Type, UsageType, ForTechsOnly, Mandatory, OrderByNumber, ShowInGrid, SelectionComboOptions, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager.…

list_all_jitbit_ticket_integration_data

Get all external integration data (Jira, GitHub, GitLab, Bitbucket, Asana, Trello, VSO, Harvest, Basecamp) linked to a Jitbit ticket. Returns: BitbucketIssueUrl, JiraIssueUrl, GitHubIssueUrl, AsanaTaskUrl, TrelloCardUrl, VSOWorkItemUrl, HarvestProjectUrl, GitLabIssueUrl, BasecampTodoUrl, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent,…

list_all_jitbit_time_spent

List time spent log entries for a Jitbit ticket. Returns all individual time entries logged against the ticket. Returns: UserID, UserName, StatusID, TimeSpentInSeconds, Date, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id.

create_a_jitbit_time_spent

Add a new time spent entry to a Jitbit ticket, logged under the current user. Returns 200 OK with 'ok' on success, or an error message on failure. Required: ticket_id, time_spent_in_seconds.

create_a_jitbit_comment

Post a comment to a Jitbit helpdesk ticket. Returns the created comment object including CommentID, IssueID, UserID, UserName, Email, Body, CommentDate, ForTechsOnly, IsSystem, and Recipients. Required: ticket_id, body.

update_a_jitbit_comment_by_id

Update an existing Jitbit comment by id. The caller must be the comment author, a category tech, or an admin. Returns: CommentID, IssueID, UserID, UserName, Email, FirstName, LastName, IsSystem, CommentDate, ForTechsOnly, Body, TicketSubject, Recipients, Username, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen,…

list_all_jitbit_comments

List comments for a Jitbit helpdesk ticket. Returns: CommentID, IssueID, UserID, UserName, Email, FirstName, LastName, IsSystem, CommentDate, ForTechsOnly, Body, TicketSubject, Recipients, Username, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: ticket_id.

list_all_jitbit_comment_templates

List all available comment templates (canned responses) in Jitbit, optionally filtered by ticket category. Returns: TemplateId, Body, Name, CategoryIDs, GroupID, GroupName, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager.

list_all_jitbit_users

List all Jitbit helpdesk users. Returns per record: UserID, Username, Email, FirstName, LastName, CompanyName, CompanyId, LastSeen, IsAdmin, Disabled, IsTech, IsManager.

get_single_jitbit_user_by_id

Get a single Jitbit user by id. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: id.

jitbit_users_get_by_email

Get a single Jitbit user by email address. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: email.

jitbit_users_get_by_username

Get a single Jitbit user by username. Returns: UserID, Username, Password, Email, FirstName, LastName, Notes, Location, Phone, Department, CompanyName, IPAddress, HostName, Lang, UserAgent, AvatarURL, Signature, Greeting, CompanyId, CompanyNotes, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager, PushToken, FullNameAndLogin, FullName. Required: username.

create_a_jitbit_user

Create a new Jitbit helpdesk user. Returns the newly created user's userId. Required: email.

update_a_jitbit_user_by_id

Update a Jitbit user by id. All parameters except the user ID are optional. Returns an empty 200 response on success. Required: id.

delete_a_jitbit_user_by_id

Delete a Jitbit user by id. This action is irreversible. Returns an empty 200 response on success. Required: id.

jitbit_users_merge

Merge two Jitbit users together, moving the from-user's data into the to-user. This action is irreversible. Returns an empty 200 response on success. Required: from_user_id, to_user_id.

jitbit_user_custom_fields_set

Set a custom field value for a Jitbit user. Pass the value as a string — for checkboxes pass true or false, for dropdowns pass the option ID, and for dates pass a date string in any format. Returns a 200 OK status on success or an error message on failure. Required: user_id, field_id, value.

jitbit_user_custom_fields_list_custom_fields

List all custom fields configured for a Jitbit user. Returns an array of custom field objects including FieldName, FieldID, Type, and Value. Required: user_id.

list_all_jitbit_assets

Get a single Jitbit asset by id. Returns the full asset object including ItemID, ModelName, Manufacturer, Type, SerialNumber, Quantity, CompanyID, Tickets, AssignedUsers, and Fields. Required: id.

create_a_jitbit_asset

Create a new asset in Jitbit. Returns the created asset object including ItemID, ModelName, Manufacturer, Type, SerialNumber, Quantity, and CompanyID. Required: model_name.

update_a_jitbit_asset_by_id

Update an existing asset in Jitbit by id. Returns the updated asset object including ItemID, ModelName, Manufacturer, Type, SerialNumber, Quantity, and CompanyID. Required: id, model_name.

jitbit_assets_assign_to_user

Assign a Jitbit asset to a user. Returns a plain-text 200 OK on success or an error message otherwise. Required: asset_id, user_id.

jitbit_assets_unassign_from_user

Unassign a Jitbit asset from a user. Returns a plain-text 200 OK on success or an error message otherwise. Required: asset_id, user_id.

jitbit_assets_add_to_ticket

Add an asset to the 'assets involved' list of a Jitbit ticket. Returns an empty 200 response on success. Required: asset_id, ticket_id.

jitbit_assets_remove_from_ticket

Remove a related asset from a Jitbit ticket. Returns an empty response on success. Required: asset_id, ticket_id.

jitbit_assets_enable

Enable a JitBit asset by its asset ID, reactivating it in the helpdesk system. Returns an empty response on success. Required: asset_id.

jitbit_assets_disable

Disable a JitBit asset by its asset ID, deactivating it in the helpdesk system. Returns an empty response on success. Required: asset_id.

jitbit_asset_custom_fields_set

Set a custom field value on a Jitbit asset. Returns 200 OK on success or an error message on failure. Required: asset_id, field_id, value.

create_a_jitbit_kb_article

Create a new Knowledge Base article in Jitbit. Returns: ArticleId, UserID, Username, Email, FirstName, LastName, Notes, Location, Phone, IPAddress, HostName, Lang, UserAgent, Signature, Greeting, IsAdmin, Disabled, SendEmail, IsTech, LastSeen, IsManager. Required: category_id, body, subject, for_techs_only.

update_a_jitbit_kb_article_by_id

Update a Jitbit knowledge base article by id, modifying its category, body, subject, and technician-only visibility. Returns an empty 200 response on success. Required: id, category_id, body, subject.

Why Truto

Why use Truto’s MCP server for Jitbit

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 650+ integrations.

01

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

02

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

03

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

04

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

05

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

06

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

Unified APIs

Unified APIs for Jitbit

Skip writing code for every integration. Use Truto’s category-specific Unified APIs out of the box or customize the mappings with AI.

Unified Ticketing API

Attachments

Attachments are the files associated with a ticket or a comment.

View Docs

Collections

Tickets and contacts can be grouped into Collections. Collection resource usually maps to the various grouping systems used in the underlying product. Some examples are lists, projects, epics, etc. You can differentiate between these grouping systems using the type attribute of a Collection.

View Docs

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.

View Docs

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.

View Docs

Organizations

Organization represents the company or the entity using the ticketing system. An Organization can have one or more Workspaces and Users.

View Docs

Ticket Priorities

Ticket Priorities represent the intended order in which the Tickets should be worked on. Some products provide customizing the Ticket Priorities.

View Docs

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.

View Docs

Users

Users represent the people using the underlying ticketing system. They are usually called agents, team members, admins, etc.

View Docs

How It Works

From zero to integrated

Go live with Jitbit in under an hour. No boilerplate, no maintenance burden.

01

Link your customer’s Jitbit account

Use Truto’s frontend SDK to connect your customer’s Jitbit account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

02

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

03

Call our API, we call Jitbit

Truto’s Proxy API is a 1-to-1 mapping of the Jitbit API. You call us, we call Jitbit, and pass the response back in the same cycle.

04

Unified response format

Every response follows a single format across all integrations. We translate Jitbit’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Jitbit on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

Does the Jitbit integration work with both cloud and self-hosted deployments?

Yes. Jitbit offers both a cloud-hosted SaaS and an on-premises version, and the API is available on both. Your end users connect their own Jitbit instance, so the same integration works whether they're on Jitbit's cloud or running it inside their own network.

How do internal notes vs. public replies work through the API?

Use create_a_jitbit_comment and pass the ForTechsOnly flag to control visibility. Setting it to true posts an internal note (ideal for AI drafts, diagnostic logs, or automation metadata), while false posts a customer-visible reply.

Can we read and write Jitbit custom fields?

Yes. You can list ticket, user, and asset custom field definitions and write values using jitbit_ticket_custom_fields_set, jitbit_ticket_custom_fields_set_many, jitbit_user_custom_fields_set, and jitbit_asset_custom_fields_set — useful for syncing enrichment data or routing signals from your product.

How do we map a customer in our product to their Jitbit user and company?

Call jitbit_users_get_by_email or jitbit_users_get_by_username to resolve a Jitbit UserID and its associated CompanyId. From there you can list tickets for that user, check disabled status, and group activity by company for MSP-style multi-tenant reporting.

Is Jitbit exposed through Truto's Unified Ticketing API?

Yes. Jitbit is available through the Unified Ticketing API with normalized models for Tickets, Comments, Attachments, Users, Organizations, Ticket Priorities, Collections, and Fields — so you can ship a single ticketing integration surface and get Jitbit alongside other helpdesks. You can also drop down to Jitbit-specific tools when you need capabilities like assets, time tracking, or ticket linking.

Can we link, merge, or create sub-tickets between related issues?

Yes. Jitbit supports linking tickets, merging duplicates, and creating parent/subticket relationships via jitbit_tickets_link, jitbit_tickets_merge, jitbit_tickets_add_subticket, and related endpoints — useful for connecting support tickets to engineering work or consolidating duplicate reports.

Jitbit

Get Jitbit integrated into your app

Our team understands what it takes to make a Jitbit integration successful. A short, crisp 30 minute call with folks who understand the problem.