[Autotask] Count tickets matching optional filters. Returns the total number of matching tickets without fetching ticket data. Useful for dashboards, reporting, and checking result set size before paginating with at_list_tickets.

[Autotask] Create a new service ticket. Requires at minimum a title and company ID. Returns the created ticket with its assigned ID. This creates data visible to helpdesk staff and end users. Use at_list_companies to find valid company IDs.

[Autotask] Retrieve a single ticket by its numeric ID. Returns full ticket details including title, status, priority, queue, company, assigned resource, due date, and custom fields. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] List tickets for a specific company. Useful for reviewing a client's current issues or full ticket history. Requires a valid company ID -- use at_list_companies to find IDs.

[Autotask] List open tickets with Critical (priority 1) or High (priority 2) priority. Useful for urgent triage. Note: priority IDs may vary by Autotask instance -- this uses 1 (Critical) and 2 (High) as common defaults.

[Autotask] List open tickets (status is not Complete). Convenience tool that filters out completed tickets. Note: Autotask status IDs vary by instance -- this uses status != 5 (Complete) as a common default. If your instance uses different status IDs, use at_list_tickets with a custom filter instead.

[Autotask] List open tickets that are past their due date. Useful for identifying overdue work items that need immediate attention.

[Autotask] List tickets updated within the last 24 hours. Useful for monitoring recent helpdesk activity without filtering by status or priority.

[Autotask] List tickets assigned to a specific resource. Use this to view a technician's current workload. Requires a valid resource ID -- use at_list_resources to find IDs.

[Autotask] Query tickets with optional filters. Returns paginated ticket summaries including ID, title, status, priority, queue, company, and assigned resource. Use this to browse tickets or narrow results before fetching full details with at_get_ticket. Pass typed filter parameters or a raw filterJson string for advanced queries.

[Autotask] List open tickets with no assigned resource. Useful for triage queues -- shows tickets waiting to be dispatched.

[Autotask] Search tickets by title keyword. Returns tickets whose title contains the search term. Use this when looking for tickets by keyword or description rather than structured filtering with at_list_tickets.

[Autotask] Update an existing ticket via PATCH. Provide the ticket ID and a JSON object of fields to update. The id field is automatically included. Returns the updated ticket. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] Add a checklist item to an existing ticket. Checklist items represent discrete tasks or steps within a ticket. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] Add a note to an existing ticket. Notes can be internal or published to the customer portal. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] Retrieve a single ticket note by its numeric ID. Returns the full note including title, description, note type, publish settings, and timestamps. Requires a valid note ID -- use at_list_ticket_notes to find IDs.

[Autotask] List checklist items for a specific ticket. Returns checklist items including ID, item name, completion status, and sort order. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] List notes for a specific ticket. Returns paginated note summaries including ID, title, description, note type, and timestamps. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] Update an existing ticket checklist item via PATCH. Commonly used to mark items as complete. Provide the checklist item ID and a JSON object of fields to update. The id field is automatically included. Requires a valid checklist item ID -- use at_list_ticket_checklist_items to find IDs.

[Autotask] Update an existing ticket note via PATCH. Provide the note ID and a JSON object of fields to update. The id field is automatically included. Requires a valid note ID -- use at_list_ticket_notes to find IDs.

[Autotask] Add a charge to an existing ticket. Charges represent billable or non-billable costs associated with the ticket. Provide a JSON object with charge fields. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] Retrieve a single ticket charge by its numeric ID. Returns full charge details including charge type, billing code, units, rate, amount, and timestamps. Requires a valid charge ID -- use at_list_ticket_charges to find IDs.

[Autotask] List additional contacts associated with a ticket. Returns contact IDs and resource associations beyond the primary contact. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] List charges on a specific ticket. Returns charge summaries including ID, charge type, billing code, amount, and timestamps. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] Update an existing ticket charge via PATCH. Provide the charge ID and a JSON object of fields to update. The id field is automatically included. Requires a valid charge ID -- use at_list_ticket_charges to find IDs.

[Autotask] Count service calls matching optional filters. Returns the total number of matching service calls without fetching data.

[Autotask] Create a new service call for dispatch/scheduling. Returns the created service call with its assigned ID.

[Autotask] Create a new task for a service call. Returns the created task with its assigned ID.

[Autotask] Link an existing ticket to a service call. Returns the created association record.

[Autotask] Delete a service call by its numeric ID. This permanently removes the service call.

[Autotask] Retrieve a single service call by its numeric ID. Returns full service call details including status, scheduled times, and assignments.

[Autotask] Query resources assigned to service call tasks. Returns resource assignment details. Use filterJson to narrow by service call task ID.

[Autotask] Query tasks associated with service calls. Returns task details including assignments and status. Use filterJson to narrow by service call ID.

[Autotask] Query tickets linked to service calls. Returns ticket associations. Use filterJson to narrow by service call ID.

[Autotask] Query service calls with optional filters. Returns paginated service call summaries used for dispatch and scheduling. Use filterJson for advanced queries.

[Autotask] Update an existing service call. The id field is automatically included. Returns the updated service call.

[Autotask] Link an additional configuration item to a ticket. Returns the created association record. Include ticketID and configurationItemID.

[Autotask] Create a change request approval for a ticket. Returns the created approval record.

[Autotask] Create an RMA credit for a ticket. Returns the created RMA credit record.

[Autotask] Assign a secondary resource to a ticket. Returns the created assignment record. Include ticketID and resourceID in the JSON.

[Autotask] Associate a tag with a ticket. Returns the created tag association record. Include ticketID and tagID.

[Autotask] Retrieve a single ticket note attachment by its numeric ID. Returns attachment metadata including filename and content type.

[Autotask] Query additional configuration items linked to tickets. Filter by ticketID to see CIs for a specific ticket.

[Autotask] Query change request approvals for tickets. Filter by ticketID to see approvals for a specific ticket.

[Autotask] Query the audit history for tickets. Returns a log of changes including who made changes and when. Filter by ticketID to see history for a specific ticket.

[Autotask] Query attachments on ticket notes. Filter by noteID or ticketID to narrow results.

[Autotask] Query RMA credits associated with tickets. Filter by ticketID to see credits for a specific ticket.

[Autotask] Query secondary resources assigned to tickets. Returns resource assignment records. Filter by ticketID to see secondary resources for a specific ticket.

[Autotask] Query tag associations for tickets. Filter by ticketID to see tags on a specific ticket.

[Autotask] Get total count of companies matching optional filters. Returns a count object. Useful for pagination planning or dashboards.

[Autotask] Create a new company record. Returns the created company with its assigned ID. The JSON must include at minimum companyName and companyType. Use at_list_companies to verify creation.

[Autotask] Retrieve full details for a single company by ID. Returns company info including name, type, status, address, and custom fields. Requires a valid company ID -- use at_list_companies or at_search_companies to find IDs.

[Autotask] List companies that are currently active. Filters on isActive=true. Useful for client roster views and service reporting.

[Autotask] Query companies with optional filters and pagination. Returns company summaries including ID, name, type, and status. Use this to discover company IDs for filtering contacts, tickets, configurations, and other company-scoped data.

[Autotask] List to-do items associated with a specific company. Returns to-do details including title, status, and due date. Requires a valid company ID.

[Autotask] List companies of type Customer (companyType=1). Useful for client roster views, billing reviews, and service reporting.

[Autotask] List companies of type Prospect (companyType=3). Useful for sales pipeline reviews -- shows companies that are potential customers but not yet active clients.

[Autotask] Search companies by name. Returns matching companies where the company name contains the search text. Use this when you know the company name but not the ID.

[Autotask] Update an existing company's fields. Returns the updated company. The JSON must include the company id field. Use at_get_company to check current values before updating.

[Autotask] Add a new location to a company. Returns the created location with its assigned ID. The JSON should include at minimum a name and address fields.

[Autotask] Add a note to a company. Returns the created note with its assigned ID. Useful for recording important information about a client. Note: Autotask's CompanyNotes entity marks actionType, assignedResourceID, startDateTime, and endDateTime as required; start/end default to the current time, but many instances also require actionType and assignedResourceID (supply them via the parameters below).

[Autotask] Retrieve a single company attachment by its numeric ID. Returns attachment metadata including filename, size, and content type.

[Autotask] Retrieve full details for a single company location by ID. Returns location info including name, address, phone, and whether it is the primary location.

[Autotask] Retrieve a single company site configuration by its numeric ID. Returns full configuration details.

[Autotask] List alerts for a specific company. Returns alert details including type, severity, and message. Requires a valid company ID.

[Autotask] List attachments for a specific company. Returns attachment metadata including filename, size, and content type. Filter by parentID (company ID).

[Autotask] List locations for a specific company. Returns location details including name, address, and contact info. Requires a valid company ID -- use at_list_companies or at_search_companies to find IDs.

[Autotask] List notes for a specific company. Returns note details including title, description, and timestamps. Requires a valid company ID.

[Autotask] List site configurations for a specific company. Returns configuration details for company sites. Filter by companyID.

[Autotask] List teams assigned to a specific company. Returns team details including resource assignments. Requires a valid company ID.

[Autotask] Update an existing company location's fields. Returns the updated location. Use at_get_company_location to check current values before updating.

[Autotask] Update an existing company site configuration. The id field is automatically included. Returns the updated configuration.

[Autotask] Get total count of contacts matching optional filters. Returns a count object. Useful for pagination planning or dashboards.

[Autotask] Create a new contact record. Returns the created contact with its assigned ID. The JSON should include at minimum firstName, lastName, and companyID.

[Autotask] Create a new contact group. Returns the created group with its assigned ID. Include at minimum a name field.

[Autotask] Add a contact to a contact group. Returns the created membership record. Include contactGroupID and contactID.

[Autotask] Delete a contact group by its numeric ID. This permanently removes the group.

[Autotask] Retrieve full details for a single contact by ID. Returns contact info including name, email, phone, company, and custom fields. Requires a valid contact ID -- use at_list_contacts or at_search_contacts to find IDs.

[Autotask] List contacts belonging to a specific company. Returns contact details including name, email, and phone. Requires a valid company ID -- use at_list_companies or at_search_companies to find IDs.

[Autotask] Query billing product associations for contacts. Returns products linked to contacts for billing purposes.

[Autotask] List contacts belonging to a specific contact group. Filter by contactGroupID to see members.

[Autotask] List contact groups with optional filters. Returns group details including name and description. Useful for organizing contacts into categories.

[Autotask] Query contacts with optional filters and pagination. Returns contact summaries including ID, name, email, phone, and company association. Use this to discover contact IDs for tickets and other contact-scoped operations.

[Autotask] Search contacts by name or email address. Returns matching contacts where first name, last name, or email contains the search text. Use this when you know the contact name or email but not the ID.

[Autotask] Update an existing contact's fields. Returns the updated contact. Use at_get_contact to check current values before updating.

[Autotask] Update an existing contact group. The id field is automatically included. Returns the updated group.

[Autotask] Get total count of configuration items matching optional filters. Returns a count object. Useful for pagination planning or asset inventory dashboards.

[Autotask] Add a note to a configuration item. Returns the created note with its assigned ID. Useful for documenting asset changes, maintenance records, or audit trails.

[Autotask] Create a new configuration item (asset) record. Returns the created CI with its assigned ID. The JSON must include at minimum referenceTitle and companyID. Use at_list_ci_types and at_list_ci_categories to find valid reference values.

[Autotask] Retrieve full details for a single configuration item (asset) by ID. Returns CI info including title, type, serial number, company, and custom fields. Requires a valid CI ID -- use at_list_configuration_items or at_search_configuration_items to find IDs.

[Autotask] List configuration items that are currently active. Filters on isActive=true. Useful for current asset inventory views, excluding retired or decommissioned equipment.

[Autotask] List notes associated with a specific configuration item. Returns note details including title, description, and created date. Requires a valid CI ID.

[Autotask] List all configuration items (assets) for a specific company. Filters CIs by companyID. Useful for asset inventory reviews or pre-ticket context gathering.

[Autotask] Query configuration items (assets) with optional filters and pagination. Returns CI summaries including ID, title, type, company, and status. Use this to discover configuration item IDs for asset management.

[Autotask] Search configuration items by title, serial number, or reference number. Returns matching CIs where the referenceTitle contains the search text. Use this when you know a device name but not the ID.

[Autotask] Update an existing configuration item's fields. Returns the updated CI. The JSON must include the CI id field. Use at_get_configuration_item to check current values before updating.

[Autotask] List configuration item categories with optional filters. Returns category details including name and description. Useful for discovering valid category values when creating or updating CIs.

[Autotask] List user-defined field (UDF) associations for a specific configuration item category. Returns UDF metadata including field names, types, and picklist values. Use at_list_ci_categories to find valid category IDs.

[Autotask] List DNS records associated with a configuration item. Returns DNS record details including hostname, record type, and value. Requires a valid CI ID.

[Autotask] List items related to a configuration item. Returns relationship details including related item type and ID. Useful for understanding asset dependencies and connections.

[Autotask] List SSL certificates associated with a configuration item. Returns certificate details including subject, issuer, and expiration date. Requires a valid CI ID.

[Autotask] List configuration item types with optional filters. Returns type details including name and description. Useful for discovering valid type values when creating or updating CIs.

[Autotask] Get total count of contracts matching optional filters. Returns a count object. Useful for pagination planning or contract portfolio dashboards.

[Autotask] Create a new contract record. Returns the created contract with its assigned ID. The JSON must include at minimum contractName, companyID, and contractType. Use at_list_contracts to verify creation.

[Autotask] Retrieve full details for a single contract by ID. Returns contract info including name, type, status, dates, and billing details. Requires a valid contract ID -- use at_list_contracts or at_search_contracts to find IDs.

[Autotask] List contracts that are currently active. Filters on status=1 (Active). Useful for service delivery dashboards and identifying contracts that are currently in effect.

[Autotask] List all contracts for a specific company. Filters contracts by companyID. Useful for service delivery reviews, billing audits, and understanding a company's contract portfolio.

[Autotask] Query contracts with optional filters and pagination. Returns contract summaries including ID, name, type, status, and company. Use this to discover contract IDs for service delivery and billing management.

[Autotask] Search contracts by name. Returns matching contracts where the contract name contains the search text. Use this when you know the contract name but not the ID.

[Autotask] Update an existing contract's fields. Returns the updated contract. The JSON must include the contract id field. Use at_get_contract to check current values before updating.

[Autotask] Add a charge to a contract. Returns the created charge with its assigned ID. The JSON must include at minimum contractID, name, and unitCost. Use at_list_contract_charges to verify creation.

[Autotask] List billing rules configured for a contract. Returns rule details including frequency, amount, and effective dates. Useful for understanding recurring billing schedules.

[Autotask] List hour blocks associated with a contract. Returns block details including hours purchased, hours used, and effective dates. Useful for tracking prepaid hour consumption.

[Autotask] List charges posted against a contract. Returns charge details including description, amount, and date. Useful for billing reviews and expense tracking.

[Autotask] List milestones associated with a contract. Returns milestone details including title, due date, and status. Useful for tracking contract deliverables and project timelines.

[Autotask] List notes associated with a contract. Returns note details including title, description, and created date. Useful for reviewing contract documentation and communication history.

[Autotask] List rates configured for a contract. Returns rate details including role, rate amount, and billing type. Useful for billing reviews and rate card analysis.

[Autotask] List retainers associated with a contract. Returns retainer details including amount, period, and usage. Useful for tracking retainer consumption and billing.

[Autotask] List service bundles associated with a contract. Returns bundle details including name and included services. Useful for reviewing bundled service agreements.

[Autotask] List services associated with a contract. Returns service details including name, price, and quantity. Useful for understanding what services are included in a contract.

[Autotask] Get total count of projects matching optional filters. Returns a count object. Useful for pagination planning or dashboards.

[Autotask] Create a new project record. Returns the created project with its assigned ID. The JSON must include at minimum projectName and companyID. Use at_list_projects to verify creation.

[Autotask] Retrieve full details for a single project by ID. Returns project info including name, status, company, dates, budget, and custom fields. Requires a valid project ID -- use at_list_projects or at_search_projects to find IDs.

[Autotask] List projects with Active or New status. Filters on status values 1 (New) and 3 (Active). Useful for workload reviews and resource planning -- excludes completed, cancelled, and inactive projects.

[Autotask] List all projects for a specific company. Returns projects filtered by company ID. Use at_list_companies or at_search_companies to find valid company IDs.

[Autotask] Query projects with optional filters and pagination. Returns project summaries including ID, name, status, company, and dates. Use this to discover project IDs for filtering phases, tasks, notes, and charges.

[Autotask] Search projects by name. Returns matching projects where the project name contains the search text. Use this when you know the project name but not the ID.

[Autotask] Update an existing project's fields. Returns the updated project. The project id field is set automatically from the projectId parameter. Use at_get_project to check current values before updating.

[Autotask] Create a phase under a project via POST /Projects//Phases. Provide the phase as a JSON object in fieldsJson. Writable fields: title (required), startDate, dueDate, description, parentPhaseID, externalID. estimatedHours and isScheduled are read-only in Autotask and cannot be set here. Returns Autotask's itemId envelope.

[Autotask] Create a new task within a project. Returns the created task with its assigned ID. The JSON must include at minimum title and projectID. The projectId parameter is merged into the JSON automatically.

[Autotask] Delete a phase from a project via DELETE /Projects//Phases/. This is permanent. Phases on Baseline-type projects are read-only in Autotask and cannot be deleted. Use at_list_project_phases to find phase IDs.

[Autotask] Retrieve full details for a single project phase by ID. Returns phase info including title, dates, status, and description. Requires a valid phase ID -- use at_list_project_phases to find IDs.

[Autotask] Retrieve full details for a single project task by ID. Returns task info including title, status, assigned resource, estimated hours, and description. Requires a valid task ID -- use at_list_project_tasks to find IDs.

[Autotask] List charges on a project. Returns charge details including name, amount, date, and billing status. Requires a valid project ID -- use at_list_projects or at_search_projects to find IDs.

[Autotask] List notes on a project. Returns note details including title, description, publish type, and created date. Requires a valid project ID -- use at_list_projects or at_search_projects to find IDs.

[Autotask] List phases within a project. Returns phase summaries including ID, title, start/end dates, and status. Requires a valid project ID -- use at_list_projects or at_search_projects to find IDs.

[Autotask] List tasks within a project. Returns task summaries including ID, title, status, assigned resource, and estimated hours. Requires a valid project ID -- use at_list_projects or at_search_projects to find IDs.

[Autotask] Update an existing project phase via PATCH /Projects//Phases. fieldsJson must include the phase id along with the fields to change. Writable fields: title, startDate, dueDate, description, parentPhaseID, externalID. estimatedHours and isScheduled are read-only in Autotask and cannot be set here. Use at_get_project_phase to check current values before updating.

[Autotask] Update an existing project task's fields. Returns the updated task. The task id field is set automatically from the taskId parameter. Use at_get_project_task to check current values before updating.

[Autotask] Get total count of time entries matching optional filters. Returns a count object. Useful for utilization reporting and pagination planning.

[Autotask] Create a new time entry record. Returns the created time entry with its assigned ID. The JSON must include at minimum resourceID, dateWorked, and hoursWorked. Use at_list_time_entries to verify creation.

[Autotask] Retrieve full details for a single time entry by ID. Returns time entry info including resource, ticket, date worked, hours, summary, and billing fields. Requires a valid time entry ID -- use at_list_time_entries to find IDs.

[Autotask] List time entries from the last N days. Defaults to the last 7 days. Useful for recent activity reviews and timesheet audits across all resources.

[Autotask] List time entries for a specific resource within an optional date range. Useful for utilization reports and timesheet reviews. Use at_list_resources to find valid resource IDs.

[Autotask] List time entries logged against a specific ticket. Returns time entry details including resource, hours, date, and summary. Requires a valid ticket ID -- use at_list_tickets or at_search_tickets to find IDs.

[Autotask] Query time entries with optional filters and pagination. Returns time entry summaries including ID, resource, ticket, date worked, hours, and billing status. Use this to browse time entries or narrow results before fetching full details.

[Autotask] Update an existing time entry's fields. Returns the updated time entry. The time entry id field is set automatically from the timeEntryId parameter. Use at_get_time_entry to check current values before updating.

[Autotask] Retrieve full details for a single resource (technician) by ID. Returns resource info including name, email, title, department, and active status. Requires a valid resource ID -- use at_list_resources or at_search_resources to find IDs.

[Autotask] List resources that are currently active. Filters on isActive=true. Useful for staffing views, dispatch boards, and resource assignment -- excludes inactive or terminated staff.

[Autotask] List resource roles with optional filters. Returns role details including ID, name, and description. Roles define billing rates and capacity for resources on projects and tickets.

[Autotask] List skills assigned to a specific resource. Returns skill details including skill name and proficiency level. Useful for skill-based routing and capacity planning. Requires a valid resource ID -- use at_list_resources to find IDs.

[Autotask] List resources (technicians/staff) with optional filters and pagination. Returns resource summaries including ID, name, email, and active status. Use this to discover resource IDs for filtering time entries, tickets, and tasks.

[Autotask] Search resources by name or email. Returns matching resources where the first name, last name, or email contains the search text. Use this when you know a technician's name or email but not their ID.

[Autotask] Get total count of opportunities matching optional filters. Returns a count object. Useful for pipeline dashboards and sales reporting.

[Autotask] Create a new opportunity record. Returns the created opportunity with its assigned ID. The JSON must include required fields such as title and companyID. Use at_list_opportunities to verify creation.

[Autotask] Retrieve full details for a single opportunity by ID. Returns opportunity info including title, status, amount, probability, projected close date, and custom fields. Requires a valid opportunity ID -- use at_list_opportunities or at_search_opportunities to find IDs.

[Autotask] List opportunities for a specific company. Returns all opportunities linked to the given company ID. Useful for account reviews and company-level sales history.

[Autotask] List opportunities that are currently open (not won or lost). Useful for active sales pipeline views and forecasting.

[Autotask] Query opportunities with optional filters and pagination. Returns opportunity summaries including ID, title, status, amount, and probability. Use this to discover opportunity IDs for detailed lookups.

[Autotask] Search opportunities by title. Returns matching opportunities where the title contains the search text. Use this when you know the opportunity name but not the ID.

[Autotask] Update an existing opportunity's fields. Returns the updated opportunity. The JSON must include the opportunity id field. Use at_get_opportunity to check current values before updating.

[Autotask] Create a new quote record. Returns the created quote with its assigned ID. The JSON must include required fields such as name and opportunityID. Use at_list_quotes to verify creation.

[Autotask] Add a line item to an existing quote. Autotask writes quote lines under their quote, so the JSON must include quoteID. Required: quoteID, quantity, isOptional, lineDiscount, percentageDiscount and unitDiscount. Set exactly one of productID, chargeID, laborID, expenseID, shippingID, serviceID or serviceBundleID to say what the line sells. name is required except on Service and Service Bundle lines (quoteItemType 11 or 12). Optional: unitPrice, unitCost, description, isTaxable, periodType, taxCategoryID. averageCost, highestCost, markupRate, sortOrderID and totalEffectiveTax are read-only and are set by Autotask. Returns the created item's ID. Use at_list_quote_items to see the quote's lines.

[Autotask] Delete one line item from a quote. This cannot be undone: the line and its pricing are removed from the quote. The quote is found from the item itself. Use at_list_quote_items to confirm the item ID first.

[Autotask] Retrieve full details for a single quote by ID. Returns quote info including name, description, line items, totals, and approval status. Requires a valid quote ID -- use at_list_quotes to find IDs.

[Autotask] Retrieve full details for a single sales order by ID. Returns sales order info including status, line items, and linked opportunity. Requires a valid sales order ID -- use at_list_sales_orders to find IDs.

[Autotask] Query quotes with optional filters and pagination. Returns quote summaries including ID, name, status, total, and associated opportunity. Use this to discover quote IDs for detailed lookups.

[Autotask] Query sales orders with optional filters and pagination. Returns sales order summaries including ID, status, and associated opportunity. Use this to discover sales order IDs for detailed lookups.

[Autotask] Update an existing quote's fields. Returns the updated quote. The JSON must include the quote id field. Use at_get_quote to check current values before updating.

[Autotask] Update fields on one quote line item. Only the fields you send change. The quote is found from the item itself, so quoteID is optional. Read-only fields (averageCost, highestCost, markupRate, sortOrderID, totalEffectiveTax) cannot be set. Returns the updated item's ID. Use at_list_quote_items to find item IDs and check current values.

[Autotask] Create a new appointment/calendar entry. Returns the created appointment with its assigned ID. The JSON should include at minimum a title, start date/time, and end date/time. This creates a calendar entry visible to assigned resources.

[Autotask] Retrieve a single appointment by its numeric ID. Returns full appointment details including title, description, start/end times, and assigned resource. Requires a valid appointment ID -- use at_list_appointments to find IDs.