Create one HaloPSA ticket from a summary and optional details and routing IDs; sends the provider-required one-item array body.

Request deletion of one HaloPSA agent by numeric ID. Use only for an agent that is confirmed safe to remove; this action does not create or verify a disposable replacement.

Delete one HaloPSA appointment by numeric ID. HaloPSA also deletes its linked Exchange event unless ignore_exchange_delete is true.

Delete one HaloPSA asset by numeric ID.

Delete one HaloPSA attachment by numeric ID.

Delete one HaloPSA client contract by numeric ID.

Delete one HaloPSA customer by numeric ID. Success is reported only after HaloPSA returns the endpoint's documented HTTP 200 status.

Delete one HaloPSA invoice by numeric ID. Set bypass_accounts_sync to true to delete it in HaloPSA without synchronizing the deletion to the connected accounts system.

Delete one HaloPSA inventory or service item by numeric ID. Use only for an item that is confirmed safe to remove.

Delete one HaloPSA knowledge-base article by numeric ID. Use only for an article that is confirmed safe to remove.

Delete one HaloPSA sales opportunity by numeric ID.

Delete one HaloPSA project by numeric ID.

Delete one HaloPSA quotation by numeric ID.

Delete one HaloPSA report definition by numeric ID.

Delete one HaloPSA customer site by numeric ID.

Delete one HaloPSA ticket-status configuration record by numeric ID. Use only for a status that is confirmed safe to remove.

Delete one HaloPSA supplier by numeric ID. Use only for a supplier that is confirmed safe to remove.

Delete one HaloPSA team by numeric ID. This changes tenant-level team configuration.

Delete one HaloPSA ticket by numeric ID, optionally recording a reason. The ticket is removed from active ticket results.

Delete one HaloPSA ticket action by numeric action ID and its parent ticket ID. HaloPSA may reject deletion for protected action types; the provider's reason is returned.

Delete one HaloPSA ticket-type configuration record by numeric ID. This does not create or verify a disposable replacement.

Delete one HaloPSA end user by numeric ID.

Return one HaloPSA agent by numeric ID. Optional flags can request expanded configuration, signature, holiday-allowance, cache, or client-context data; the response preserves additional provider fields.

Return one HaloPSA appointment by numeric ID, optionally with extra detail objects.

Return one HaloPSA asset by numeric ID, optionally including activity, allowed statuses, details, diagram data, and hierarchy data.

Download one HaloPSA attachment by numeric ID.

Return one HaloPSA client contract by numeric ID, with optional expanded billing, asset, user, schedule, and period details.

Return a compact identity for the HaloPSA agent authorized by the current connection, without claims or access-control records.

Return one HaloPSA customer by numeric ID, with optional expanded, activity, ticket-type, period, and pre-pay data.

Return one HaloPSA invoice by numeric ID, optionally with extra detail objects.

Return one HaloPSA inventory or service item by numeric ID, optionally with expanded details and tenant-specific accounting data; additional provider fields are preserved.

Return one HaloPSA knowledge-base article by numeric ID, optionally with expanded details and language or organisation context.

Return one HaloPSA sales opportunity by numeric ID, optionally with extra provider detail objects.

Return one HaloPSA project by numeric ID, optionally with expanded details.

Return one HaloPSA quotation by numeric ID, optionally with expanded details or portal-view context.

Return one HaloPSA report definition by numeric ID. Optionally include definition details or load report data with the documented report context.

Return one HaloPSA customer site by numeric ID, with optional customer, permission, activity, detail, setup, and ticket-type context.

Return one HaloPSA ticket-status configuration record by numeric ID, optionally including its detailed configuration.

Return one HaloPSA supplier by numeric ID, optionally including expanded details; additional provider fields are preserved.

Return one HaloPSA team by numeric ID, optionally including agent details and expanded team objects.

Return one HaloPSA ticket by numeric ID, with core assignment and classification fields and optional expanded details and most recent action.

Get one HaloPSA ticket action by numeric action ID, optionally providing its ticket ID and requesting expanded details.

Return one HaloPSA ticket type by numeric ID. Optional flags select the documented configuration, detail, knowledge-base, team-restriction, survey, new-ticket, and ticket-context representations.

Return one HaloPSA end user by numeric ID, with optional customer, site, ticket-type, opportunity, supplier, activity, billing, asset, and detail context.

Return compact HaloPSA agent records for assignment lookup, optionally filtered by name, email address, telephone number, or team ID.

Return one page of HaloPSA appointments, optionally filtered by customer, ticket, date range, or search text.

Return one page of HaloPSA assets, optionally filtered by customer, site, user, asset type, search text, and active state.

List HaloPSA attachment metadata, optionally for one ticket.

Return one page of HaloPSA client contracts, optionally filtered by customer, site, search text, and active state.

Return one page of HaloPSA customers, optionally filtered by name and active state.

Return one page of HaloPSA invoices, optionally filtered by date, customer, site, ticket, user, or search text.

Return one page of HaloPSA inventory and service items with the provider's documented status, asset, supplier, accounting, stock, search, and ordering filters.

Return one page of HaloPSA knowledge-base articles using the provider's documented status, access, relationship, language, search, and ordering filters.

Return one page of HaloPSA sales opportunities, optionally filtered by customer, assignment, status, date range, or search text.

Return HaloPSA policy-priority mappings used to classify tickets, optionally filtered by SLA policy ID.

Return one page of HaloPSA projects. HaloPSA represents projects as ticket-like records in a tickets array.

Return HaloPSA quotations with customer, state, approval, processing, text, attachment, ordering, and page filters.

Return one page of HaloPSA report definitions with the provider's documented access, chart, customer, publication, ordering, group, search, and type filters.

Return one page of HaloPSA customer sites, optionally filtered by customer, name, and active state.

Return HaloPSA ticket statuses, optionally constrained to a ticket type or a specific ticket's valid context.

Return one page of HaloPSA suppliers with the provider's documented status, integration, ordering, search, and top-level filters.

Return HaloPSA teams available for ticket assignment, optionally limited to the current agent's teams or a department.

List HaloPSA ticket actions, optionally filtering by occurrence date range and whether attachment details are included. Set ticket_id to retrieve actions for a ticket; HaloPSA can return an empty list when it is omitted.

Return one page of HaloPSA tickets, optionally filtered by customer, site, user, status, assigned agent, or text search.

Return ticket types available for ticket classification, optionally limited to types that agents can create for a customer.

Return one page of HaloPSA end users, optionally filtered by customer, site, name, and active state.

Create or update HaloPSA agent profiles, team memberships, account enablement, administrator access, working hours, licensing, costs, notifications, and approval settings in one array request.

Create or update HaloPSA appointments in one array request. Each item with id updates that appointment and each item without id creates one. HaloPSA does not document a universally sufficient minimal create payload.

Create or update one or more HaloPSA assets. Each item with an id updates that asset; each item without an id creates a new asset.

Create or update one or more HaloPSA client contracts. Each item with an id updates that contract; each item without an id creates a contract. Creates require client_id, ref, start_date, end_date, and billingperiod.

Create or update one or more HaloPSA customers in the endpoint's array body. Each item with id updates that customer; each item without id creates one.

Create or update HaloPSA invoice records and their typed line items. This action does not capture payment, post or email invoices, create credit notes, or trigger accounting-system synchronization.

Create or update HaloPSA inventory and service items in one array request. Each item with id updates that record and each item without id creates one; mixed batches are supported and can alter inventory and accounting state.

Create or update one or more HaloPSA knowledge-base articles through POST /KBArticle. Each item with id updates that article; each item without id creates one. HaloPSA documents no universally sufficient create payload.

Upsert HaloPSA sales opportunities: each resource item with id updates that record, while each item with id omitted creates a record. HaloPSA does not document a universally sufficient minimal create payload.

Create or update HaloPSA project records, typed milestones, and tags. This action does not close projects, publish articles, send notifications, override record locks, or invoke provider-import and validation workflows.

Create or update HaloPSA quotation records and typed quotation lines. This action does not send quotations, start signing or approval, create sales orders, or invoke external commerce integrations.

Create or update HaloPSA report definitions in one array request. Each item with id updates that report and each item without id creates one; this mutates report definitions and may expose saved SQL or report output.

Create or update one or more HaloPSA customer sites. Each item with an id updates that site; each item without an id creates a site. HaloPSA does not document a universally sufficient minimal create payload.

Create or update HaloPSA ticket statuses in one array request. Set an item's id to update that exact status, or omit id to create one.

Create or update one or more HaloPSA suppliers through POST /Supplier. Each item with id updates that supplier; each item without id creates one. HaloPSA does not document a universally sufficient minimal create payload.

Create or update HaloPSA teams in one array request. Set an item's id to update that exact team, or omit id to create one.

Create or update ticket notes and work-log actions, optionally recording time or applying a ticket status, without sending email. Each resource with action_id updates that action; each resource without action_id creates one.

Create or update HaloPSA ticket types in one array request. Set an item's id to update that exact ticket type, or omit id to create one.

Create or update one or more HaloPSA end-user records without sending welcome email. Each item with an id updates that user; each item without an id creates one.