RepairShopr

Deletes an Appointment Type by ID -- Required permission: Global Admin via DELETE /appointment_types/{id}

Deletes an Appointment by ID -- No special permissions required. via DELETE /appointments/{id}

Deletes a Canned Response -- Required permission: Ticket Canned Responses - Manage via DELETE /canned_responses/{id}

Deletes a Contact -- Required permission: Customers - Edit Single-Customer Users can only access own contacts. via DELETE /contacts/{id}

Deletes a Contract by ID -- Required permission: Contracts - Delete via DELETE /contracts/{id}

Deletes a Payment Profile via DELETE /customers/{customer_id}/payment_profiles/{id}

Deletes a Phone by ID -- Required permission: Customers - Edit Single-Customer Users can only access own. via DELETE /customers/{customer_id}/phones/{id}

Deletes a Customer by ID -- Required permission: Customers - Delete via DELETE /customers/{id}

Deletes an Estimate by ID -- Required permission: Estimates - Delete via DELETE /estimates/{id}

Deletes a Line Item -- Required permission: Estimates - Edit via DELETE /estimates/{id}/line_items/{line_item_id}

Deletes an invoice by ID -- Returns 200 even if the delete fails via DELETE /invoices/{id}

Deletes an a line item of an invoice by ID -- This deletes an existing Invoice's line item via DELETE /invoices/{id}/line_items/{line_item_id}

Deletes a Portal User by ID -- Required permission: Global Admin via DELETE /portal_users/{id}

Deletes a Product Image via DELETE /products/{id}/delete_image

Deletes a Product SKU by ID -- Required permission: Products - Edit via DELETE /products/{product_id}/product_skus/{id}

Deletes/Clears an RMM Alert by ID -- Required permission: RMM Alerts - Delete Single-Customer Users can only access own RMM Alerts. via DELETE /rmm_alerts/{id}

Deletes a Schedule by ID -- Required permission: Recurring Invoices - Delete via DELETE /schedules/{id}

Removes a Line Item from an Invoice Schedule -- Required permission: Recurring Invoices - Edit `POST /schedules/{id}/remove_line_item` is an older alias for this endpoint and behaves identically. via DELETE /schedules/{id}/line_items/{schedule_line_item_id}

Deletes a Ticket by ID -- Required permission: Tickets - Delete Single-Customer Users can only access own tickets. via DELETE /tickets/{id}

Deletes a Worksheet Result -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Single-Customer Users can only access own tickets. via DELETE /tickets/{ticket_id}/worksheet_results/{id}

Deletes a Wiki Page by ID -- Required permission: Documentation - Delete via DELETE /wiki_pages/{id}

Returns a paginated list of Appointment Types -- Required permission: Global Admin via GET /appointment_types

Retrieves an Appointment Type by ID -- Required permission: Global Admin via GET /appointment_types/{id}

Returns a paginated list of Appointments -- Required permission: Appointments - View All (see-own never restricted) via GET /appointments

Retrieves an Appointment by ID -- No special permissions required. via GET /appointments/{id}

Get Caller ID via GET /callerid

Returns a list of Canned Responses with a query -- Required permission: Ticket Canned Responses - Manage via GET /canned_responses

Returns the settings for Canned Responses -- Required permission: Ticket Canned Responses - Manage Single-Customer Users can only access own canned responses. via GET /canned_responses/settings

Returns a paginated list of Contacts -- Required permission: Customers - View Detail Single-Customer Users can only access own contacts. via GET /contacts

Retrieves a Contact by ID -- Required permission: Customers - View Detail Single-Customer Users can only access own contacts. via GET /contacts/{id}

Returns a paginated list of Contracts -- Required permission: Contracts - List/Search Every contract in the list carries the same covered-item fields as `GET /contracts/{id}`. Covered items are part of the contract payload: * `product_price_overrides` — the covered products with their contracted rate (`price_retail_cents` or `discount_percentage`) and their block-list status (`blacklisted`, meaning the product is billed separately from the contract). * `non_billable_product_ids` — products covered by the contract and therefore not billed on their own. * `schedule_ids` — the recurring invoice schedules this contract governs. Link a schedule to a contract by sending `contract_id` to the Schedule endpoints. via GET /contracts

Retrieves a Contract by ID -- Required permission: Contracts - Edit Covered items are part of the contract payload: * `product_price_overrides` — the covered products with their contracted rate (`price_retail_cents` or `discount_percentage`) and their block-list status (`blacklisted`, meaning the product is billed separately from the contract). * `non_billable_product_ids` — products covered by the contract and therefore not billed on their own. * `schedule_ids` — the recurring invoice schedules this contract governs. Link a schedule to a contract by sending `contract_id` to the Schedule endpoints. via GET /contracts/{id}

Returns a paginated list of Assets -- Required permission: Assets - List/Search Single-Customer Users can only access own assets. via GET /customer_assets

Returns a list of Assets for a specific contact -- Required permission: Assets - List/Search Returns a list of assets associated with a specific contact ID. via GET /customer_assets/assets_by_contact/{contact_id}

Retrieves an Asset by ID -- Required permission: Assets - View Details Single-Customer Users can only access own assets. via GET /customer_assets/{id}

Retrieves installed applications for an Asset -- Required permission: Assets - List/Search Single-Customer Users can only access own assets. Returns a paginated list of software installed on the asset. The `installed_at` date falls back to `created_at` when no explicit installation date is recorded. via GET /customer_assets/{id}/installed_applications

Retrieves Windows patch data for an Asset -- Required permission: Assets - List/Search Single-Customer Users can only access own assets. via GET /customer_assets/{id}/patches

Retrieves Assets by ID -- Required permission: Assets - List/Search Single-Customer Users can only access own assets. via GET /customer_assets/chat_information_by_ids

Returns a paginated list of customers -- Required permission: Customers - List/Search Single-Customer Users can only access own customer (self). via GET /customers

Returns a paginated list of customers for autocomplete query via GET /customers/autocomplete

Returns a paginated list of Payment Profiles via GET /customers/{customer_id}/payment_profiles

Retrieves a Payment Profile by ID via GET /customers/{customer_id}/payment_profiles/{id}

Returns a paginated list of Phones -- Required permission: Customers - View Detail Single-Customer Users can only access own. via GET /customers/{customer_id}/phones

Retrieves a Customer by ID -- Required permission: Customers - View Detail Single-Customer Users can only access own customer (self). via GET /customers/{id}

Returns latest Customer -- Required permission: Customers - Edit Single-Customer Users can only access own customer (self). via GET /customers/latest

Returns a paginated list of Estimates -- Required permission: Estimates - List/Search via GET /estimates

Retrieves an Estimate by ID or number -- Required permission: Estimates - View Details via GET /estimates/{id}

Returns a paginated list of Invoices -- Required permission: Invoices - List/Search via GET /invoices

Retrieves an Invoice by ID or Number -- Required permission: Invoices - View Details via GET /invoices/{id}

Returns the associated ticket for an invoice -- Required permissions: "Invoices - View Details" and "Tickets - View Details" via GET /invoices/{id}/ticket

Returns a paginated list of Part Orders -- Required permission: Parts Orders - List/Search via GET /items

Returns a paginated list of Leads -- Required permission: Leads - List/Search via GET /leads

Retrieves a Lead by ID -- Required permission: Leads - List/Search via GET /leads/{id}

Returns a paginated list of Line Items -- Required permission: Global Admin via GET /line_items

Returns the current user via GET /me

Returns a paginated list of Ticket Forms -- Required permission: Ticket Workflows - Manage via GET /new_ticket_forms

Retrieves a Ticket Form -- Required permission: Tickets - Create via GET /new_ticket_forms/{id}

Returns a paginated list of Payment Methods -- All Users except Co-Managed Support Users may use this action. via GET /payment_methods

Returns a paginated list of Payments -- Required permission: Payments - View List via GET /payments

Retrieves a Payment by ID -- Required permission: Payments - View List via GET /payments/{id}

Returns a paginated list of Portal Users -- Required permission: Global Admin via GET /portal_users

Returns a paginated list of Products -- Required permission: Products - List/Search via GET /products

Returns a Product by Barcode -- Required permission: Products - List/Search via GET /products/barcode

Retrieves a Product by ID -- Required permission: Products - List/Search via GET /products/{id}

Returns a paginated list of Product_serials -- Required permission: Products - List/Search via GET /products/{product_id}/product_serials

Returns a list of Product SKUs -- Required permission: Products - List/Search via GET /products/{product_id}/product_skus

Returns a paginated list of Product Categories -- Required permission: Products - List/Search via GET /products/categories

Returns a paginated list of Purchase Orders -- Required permission: Purchase Orders - List/Search via GET /purchase_orders

Retrieves a Purchase Order by ID -- Required permission: Purchase Orders - View Details via GET /purchase_orders/{id}

Returns a paginated list of RMM Alerts -- Required permission: RMM Alerts - List Single-Customer Users can only access own RMM Alerts. via GET /rmm_alerts

Retrieves an RMM Alert by ID -- Required permission: RMM Alerts - List Single-Customer Users can only access own RMM Alerts. via GET /rmm_alerts/{id}

Returns a paginated list of Invoice Schedules -- Required permission: Recurring Invoices - List via GET /schedules

Retrieves a Schedule by ID -- Required permission: Recurring Invoices - List via GET /schedules/{id}

Search all the things -- Additional permissions required depending on search results type: - Customer, Contact, Asset: "Customers - List/Search" - Lead: Leads - List/Search - Invoice: Invoices - List/Search - Estimate: Estimates - List/Search - Ticket: Tickets - List/Search - Product: Products - List/Search - Purchase Order, Vendor: Purchase Orders - List/Search - Report: Reports - View - Wiki: Documentation - Allow Usage via GET /search

Returns a list of Account Settings with rollout via GET /settings

Returns Printing Settings via GET /settings/printing

Returns Tabs Settings via GET /settings/tabs

Returns a paginated list of Ticket Blueprints -- Required permission: Ticket Blueprints - Manage Returns only blueprints available for ticket creation (hidden_for_ticket_creation: false). via GET /ticket_blueprints

Returns a paginated flat list of comments across multiple tickets -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Returns a flat, paginated list of comments across multiple tickets sorted by ticket_id ASC, created_at DESC. All comments for a given ticket are adjacent in the response, with the newest comments first within each ticket. Comments can be scoped to specific tickets using a saved Ticket View (ticket_search_id) and/or direct ticket filters such as customer_id, status, etc. Comment-level date filters use the `comment_` prefix to distinguish them from the ticket-level date filters that share similar names (e.g. created_after). Single-Customer Users can only access comments for their own tickets. via GET /ticket_comments

Returns a paginated list of Ticket Timers -- Required permission: Ticket Timers - Overview via GET /ticket_timers

Returns a paginated list of Tickets -- Required permission: Tickets - List/Search Single-Customer Users can only access own tickets. via GET /tickets

Retrieves a Ticket by ID -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Single-Customer Users can only access own tickets. via GET /tickets/{id}

Returns Comments for a Ticket -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Single-Customer Users can only access comments for their own tickets. via GET /tickets/{id}/comments

Returns a paginated list of Worksheet Results -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Single-Customer Users can only access own tickets. via GET /tickets/{ticket_id}/worksheet_results

Retrieves a Worksheet Result by ID -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Single-Customer Users can only access own tickets. via GET /tickets/{ticket_id}/worksheet_results/{id}

Returns Tickets Settings via GET /tickets/settings

Returns a paginated list of Timelogs -- Users with permission "Timelogs - Manage" may see timelogs for any/all users. Otherwise, results scoped to current user. via GET /timelogs

Returns last Timelog -- Users with permission "Timelogs - Manage" may see timelogs for any/all users. Otherwise, results scoped to current user. via GET /timelogs/last

Retrieves an existing User Device by UUID via GET /user_devices/{id}

Returns a paginated list of Users via GET /users

Retrieves an existing User by ID via GET /users/{id}

Returns a paginated list of Vendors -- Required permission: Vendors - List via GET /vendors

Retrieves a Vendor Page -- Required permission: Vendors - View Details via GET /vendors/{id}

Returns a paginated list of Wiki Pages -- Required permission: Documentation - Allow Usage via GET /wiki_pages

Retrieves a Wiki Page -- Required permission: Documentation - Allow Usage via GET /wiki_pages/{id}

Updates a Canned Response -- Required permission: Ticket Canned Responses - Manage via PATCH /canned_responses/{id}

Updates an existing Ticket Timer by ID -- Required permission: Ticket Timers - Overview via PATCH /ticket_timers/{id}

Creates an Appointment Type -- Required permission: Global Admin via POST /appointment_types

Creates an Appointment -- No special permissions required. via POST /appointments

Creates a new Canned Response -- Required permission: Ticket Canned Responses - Manage via POST /canned_responses

Creates a Contact -- Required permission: Customers - Edit Single-Customer Users can only access own contacts. via POST /contacts

Creates a Contract -- Required permission: Contracts - Edit A complete contract — top-level attributes, covered items with their contracted rates, the block-list and the non-billable products — is created in this one call. Covered items are part of the contract payload: * `product_price_overrides` — the covered products with their contracted rate (`price_retail_cents` or `discount_percentage`) and their block-list status (`blacklisted`, meaning the product is billed separately from the contract). * `non_billable_product_ids` — products covered by the contract and therefore not billed on their own. * `schedule_ids` — the recurring invoice schedules this contract governs. Link a schedule to a contract by sending `contract_id` to the Schedule endpoints. via POST /contracts

Creates an Asset -- Required permission: Assets - Create Single-Customer Users can only access own assets. via POST /customer_assets

Creates a Customer -- Required permission: Customers - Create via POST /customers

Creates a Payment Profile via POST /customers/{customer_id}/payment_profiles

Creates a Phone -- Required permission: Customers - Edit Single-Customer Users can only access own. via POST /customers/{customer_id}/phones

Creates an Estimate -- Required permission: Estimates - Create via POST /estimates

Convert an Estimate to an Invoice -- Required permissions: "Estimates - View Details" and "Invoices - Create" via POST /estimates/{id}/convert_to_invoice

Sends an Estimate to a Customer -- Required permission: Estimates - View Details via POST /estimates/{id}/email

Adds a Line Item to an Estimate -- Required permission: Estimates - Edit via POST /estimates/{id}/line_items

Queues a print job for an Estimate -- Required permission: Estimates - View Details via POST /estimates/{id}/print

Creates an Invoice -- Required permission: Invoices - Create `subtotal`, `total`, `tax`, `balance_due`, `is_paid`, `verified_paid`, `tech_marked_paid`, `pdf_url`, `customer_business_then_name` and `hardwarecost` are computed from the line items and payments. They are returned on every response but ignored in a request; this endpoint has never accepted them. via POST /invoices

Sends invoice to customer -- Required permission: Invoices - View Details via POST /invoices/{id}/email

Creates a new line item -- Required permission: Invoices - Edit via POST /invoices/{id}/line_items

Queues a print job for an invoice -- Required permission: Invoices - View Details via POST /invoices/{id}/print

Creates a Lead -- Required permission: None via POST /leads

Creates a new Ticket for a Ticket Form -- Required permission: Tickets - Create via POST /new_ticket_forms/{id}/process_form

Authorize a User with One Time Password via POST /otp_login

Creates a Payment -- Required permission: Payments - Create via POST /payments

Creates a Portal User -- Required permission: Global Admin via POST /portal_users

Creates an Invitation for a Portal User -- Required permission: Global Admin via POST /portal_users/create_invitation

Creates a Product -- Required permission: Products - Create via POST /products

Creates a Product Image -- Required permission: Products - Edit via POST /products/{id}/add_images

Creates a Product Serial -- Required permission: Products - Edit via POST /products/{product_id}/product_serials

Adds Product Serials to a Line Item -- Required permission: Products - List/Search Additional permissions required depending on "record_type": - LineItem: "Invoices - Edit" or "Estimates - Edit" - TicketLineItem: Tickets - Edit via POST /products/{product_id}/product_serials/attach_to_line_item

Creates a Product SKU -- Required permission: Products - Edit via POST /products/{product_id}/product_skus

Creates a Purchase Order -- Required permission: Purchase Orders - Edit via POST /purchase_orders

Adds a Product to a Purchase Order -- Required permission: Purchase Orders - Edit via POST /purchase_orders/{id}/create_po_line_item

receive purchase_order -- Required permission: Purchase Orders - Edit via POST /purchase_orders/{id}/receive

Creates an RMM Alert -- Required permission: RMM Alerts - Create Single-Customer Users can only access own RMM Alerts. via POST /rmm_alerts

Mutes an RMM Alert by ID -- Required permission: RMM Alerts - Clear/Manage Single-Customer Users can only access own RMM Alerts. via POST /rmm_alerts/{id}/mute

Schedules a Script on an Asset -- Required permission: Scripts - Execute Single-Customer Users can only access own assets. via POST /rmm/public_scripts/{asset_id}/schedule

Creates an Invoice Schedule -- Required permission: Recurring Invoices - New Accepts every settable field on a schedule, so a schedule can be fully configured in one call. Add its line items afterwards with `POST /schedules/{id}/line_items`, or seed them from an existing invoice by passing `invoice_id`. `id`, `account_id`, `created_at`, `updated_at` and `last_run` are read-only. So are `subscription_status` and `recurring_type_id`, which are maintained for you: the first is recomputed from the linked contract and the unpaid invoice count on every run, and the second is what selects the billing engine for the whole schedule. Every id in the request is checked against your account before anything is written, so a rejected request changes nothing. Errors come back as `{"error": ["Location can't be found", ...]}` with status 422. via POST /schedules

Adds a Line Item to an Invoice Schedule (deprecated) -- Required permission: Recurring Invoices - Edit **Deprecated.** Identical to `POST /schedules/{id}/line_items`, which matches the Invoice and Estimate APIs. Kept for existing integrations; use the nested route instead. via POST /schedules/{id}/add_line_item

Adds a Line Item to an Invoice Schedule -- Required permission: Recurring Invoices - Edit Most fields only apply to one kind of line, chosen with `recurring_type_id`; the descriptions say which. `POST /schedules/{id}/add_line_item` is an older alias for this endpoint and behaves identically. via POST /schedules/{id}/line_items

Removes a Line Item from an Invoice Schedule (deprecated) -- Required permission: Recurring Invoices - Edit **Deprecated.** Identical to `DELETE /schedules/{id}/line_items/{schedule_line_item_id}`, which matches the Invoice and Estimate APIs. Kept for existing integrations; use the nested route instead. via POST /schedules/{id}/remove_line_item

Creates tickets from a Blueprint -- Required permission: Ticket Blueprints - Create Ticket From Blueprint Creates a parent ticket and child tickets from the blueprint, assigned to the given customer. Returns the parent ticket ID and array of child ticket IDs. via POST /ticket_blueprints/{id}/apply

Creates a Ticket Timer that starts running -- Required permission: Ticket Timers - Overview Creates a Ticket Timer that starts directly in status_running (start_time is set to now, end_time is left unset). The timer always belongs to the authenticated technician — any client-supplied user_id is ignored. A technician holds at most one active timer per ticket. If they already have a running or paused timer on the ticket it is resumed and returned with a 200 rather than a second timer being created, and the request body is ignored. An omitted or null `billable` resolves to the account's "time is non-billable by default" setting, matching the Web App. via POST /ticket_timers

Pauses a running Ticket Timer -- Required permission: Ticket Timers - Overview Pauses a running Ticket Timer. Returns a 422 if the timer is not currently running. via POST /ticket_timers/{id}/pause

Starts (or resumes a paused) Ticket Timer -- Required permission: Ticket Timers - Overview Starts a Ticket Timer that has never been started, or resumes a paused one. Returns a 422 if the timer is already running or has been stopped. via POST /ticket_timers/{id}/start

Stops a running or paused Ticket Timer -- Required permission: Ticket Timers - Overview Stops a running or paused Ticket Timer. Returns a 422 if the timer is already stopped. If the account has `ticket_timer_charge_by_default` enabled, this also creates the ticket line item for the charged time. via POST /ticket_timers/{id}/stop

Creates a Ticket -- Required permission: Tickets - Create Sending `parent_id` additionally requires: Ticket Parent-Child - Edit. Requests that send it without that permission, or on an account without parent/child tickets enabled, are rejected with 403. Single-Customer Users can only access own tickets. via POST /tickets

Creates a Ticket Line Item -- Required permission: Tickets - Edit Single-Customer Users can only access own tickets. via POST /tickets/{id}/add_line_item

Attach a file to a Ticket -- Required permission: Tickets - Edit Single-Customer Users can only access own tickets. via POST /tickets/{id}/attach_file_url

Charges a Ticket Timer -- Required permission: Ticket Timers - Overview via POST /tickets/{id}/charge_timer_entry

Adds a Comment to a Ticket -- Required permission: Tickets - Edit Single-Customer Users can only access own tickets. via POST /tickets/{id}/comment

Deletes a Ticket Attachment -- Required permission: Tickets - Edit Single-Customer Users can only access own tickets. via POST /tickets/{id}/delete_attachment

Deletes a Ticket Timer -- Required permission: Ticket Timers - Overview via POST /tickets/{id}/delete_timer_entry

Prints a Ticket by ID -- Required permission: Tickets - View Details Single-Customer Users can only access own tickets. via POST /tickets/{id}/print

Deletes a Ticket Line Item -- Required permission: Tickets - Edit Single-Customer Users can only access own tickets. via POST /tickets/{id}/remove_line_item

Create a Ticket Timer for a Ticket -- Required permission: Ticket Timers - Overview via POST /tickets/{id}/timer_entry

Creates Worksheet Result -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Single-Customer Users can only access own tickets. via POST /tickets/{ticket_id}/worksheet_results

Creates a User Device via POST /user_devices

Creates a Vendor -- Required permission: Vendors - New via POST /vendors

Creates a Wiki Page -- Required permission: Documentation - Create via POST /wiki_pages

Updates an existing Appointment Type by ID -- Required permission: Global Admin via PUT /appointment_types/{id}

Updates an existing Appointment by ID -- No special permissions required. via PUT /appointments/{id}

Updates an existing Contact -- Required permission: Customers - Edit Single-Customer Users can only access own contacts. via PUT /contacts/{id}

Updates an existing Contract by ID -- Required permission: Contracts - Edit Covered items are part of the contract payload: * `product_price_overrides` — the covered products with their contracted rate (`price_retail_cents` or `discount_percentage`) and their block-list status (`blacklisted`, meaning the product is billed separately from the contract). * `non_billable_product_ids` — products covered by the contract and therefore not billed on their own. * `schedule_ids` — the recurring invoice schedules this contract governs. Link a schedule to a contract by sending `contract_id` to the Schedule endpoints. via PUT /contracts/{id}

Updates an existing Asset by ID -- Required permission: Assets - Edit Single-Customer Users can only access own assets. via PUT /customer_assets/{id}

Updates a Payment Profile via PUT /customers/{customer_id}/payment_profiles/{id}

Updates an existing Phone by ID -- Required permission: Customers - Edit Single-Customer Users can only access own. via PUT /customers/{customer_id}/phones/{id}

Updates an existing Customer by ID -- Required permission: Customers - Edit Single-Customer Users can only access own customer (self). via PUT /customers/{id}

Updates an existing Estimate by ID -- Required permission: Estimates - Edit via PUT /estimates/{id}

Updates a Line Item -- Required permission: Estimates - Edit via PUT /estimates/{id}/line_items/{line_item_id}

Updates an existing invoice by ID -- This updates an existing Invoice, all parameters overwrite existing params via PUT /invoices/{id}

Updates an a line item of an invoice by ID -- This updates an existing Invoice's line item, all parameters overwrite existing params via PUT /invoices/{id}/line_items/{line_item_id}

Updates an existing Lead by ID -- Required permission: None via PUT /leads/{id}

Updates an existing Portal User by ID -- Required permission: Global Admin via PUT /portal_users/{id}

Updates an existing Product by ID -- Required permission: Products - Edit via PUT /products/{id}

Updates a Location Quantity -- Required permission: Products - Edit Quantities via PUT /products/{id}/location_quantities

Updates an existing Product Serial by ID -- Required permission: Products - Edit via PUT /products/{product_id}/product_serials/{id}

Updates an existing Product SKU by ID -- Required permission: Products - Edit via PUT /products/{product_id}/product_skus/{id}

Updates a Purchase Order -- Required permission: Purchase Orders - Edit Updates allowed fields on a Purchase Order. Only the following fields may be modified: `status`, `general_notes`, `shipping_cents`, `delivery_tracking`, `vendor_id`. via PUT /purchase_orders/{id}

Updates an existing Invoice Schedule by ID -- Required permission: Recurring Invoices - Edit Accepts the same fields as `POST /schedules`. Only the fields you send are changed; omitted fields are left alone. Changing `customer_id` on a schedule that already has a `contract_id` or a `payment_id` requires sending a matching one too, or an empty one to unlink — otherwise the schedule would keep pointing at another customer's contract or card. `id`, `account_id`, `created_at`, `updated_at` and `last_run` are read-only. So are `subscription_status` and `recurring_type_id`, which are maintained for you: the first is recomputed from the linked contract and the unpaid invoice count on every run, and the second is what selects the billing engine for the whole schedule. Every id in the request is checked against your account before anything is written, so a rejected request changes nothing. Errors come back as `{"error": ["Location can't be found", ...]}` with status 422. via PUT /schedules/{id}

Updates a Line Item -- Required permission: Recurring Invoices - Edit Accepts the same fields as adding one. Only the fields you send are changed. via PUT /schedules/{id}/line_items/{schedule_line_item_id}

Updates an existing Ticket by ID -- Required permission: Tickets - Edit Sending `parent_id` additionally requires: Ticket Parent-Child - Edit. Requests that send it without that permission, or on an account without parent/child tickets enabled, are rejected with 403. Send an empty `parent_id` to unlink the Ticket from its parent. Single-Customer Users can only access own tickets. via PUT /tickets/{id}

Updates an existing Ticket Line Item -- Required permission: Tickets - Edit Single-Customer Users can only access own tickets. via PUT /tickets/{id}/update_line_item

Updates an existing Ticket Timer -- Required permission: Ticket Timers - Overview via PUT /tickets/{id}/update_timer_entry

Updates a Worksheet Result -- Required permissions: "Tickets - View Details" or "Tickets - View 'Their Ticket' Details (assigned to them)" Single-Customer Users can only access own tickets. The `answers` object accepts one or more field updates. Each key should be the field's slug, and the value should be an object containing `value` (the new field value) and optionally `user` (who made the change). If `user` is not provided, it defaults to the API token owner. via PUT /tickets/{ticket_id}/worksheet_results/{id}

Updates a Timelog -- Users with permission "Timelogs - Manage" may see timelogs for any/all users. Otherwise, results scoped to current user. via PUT /timelogs

Updates an existing User Device by UUID via PUT /user_devices/{id}

Updates an existing Vendor page by ID -- Required permission: Vendors - Edit via PUT /vendors/{id}

Updates an existing Wiki Page by ID -- Required permission: Documentation - Edit via PUT /wiki_pages/{id}