Settings and activity
72 results found
-
8 votes
An error occurred while saving the comment An error occurred while saving the comment 
Danny Stergiadis
commented
We use the API to pull tickets details, time and other fields to create invoices in QBO. But we can't pull products added to any ticket through the API as this doesnt exist as a function. Some background: When a customer orders new computers (or any hardware) we save the product details of those computers and the labour/time to setup, etc into the ticket. Right now we have to flag the ticket with a custom field in order to ensure someone visits the imported QBO Invoice and adds the products manually. This is very time consuming. Having an API to access the products by ticketID is very important.
Danny Stergiadis
supported this idea
·
-
3 votesDanny Stergiadis
supported this idea
·
-
3 votesDanny Stergiadis
supported this idea
·
-
14 votesDanny Stergiadis
supported this idea
·
-
3 votesDanny Stergiadis
supported this idea
·
-
44 votesDanny Stergiadis
supported this idea
·
-
9 votesDanny Stergiadis
supported this idea
·
-
48 votesDanny Stergiadis
supported this idea
·
-
30 votesDanny Stergiadis
supported this idea
·
-
8 votesDanny Stergiadis
supported this idea
·
-
7 votesDanny Stergiadis
supported this idea
·
-
15 votesDanny Stergiadis
supported this idea
·
-
29 votesDanny Stergiadis
supported this idea
·
-
9 votesDanny Stergiadis
supported this idea
·
-
10 votesDanny Stergiadis
supported this idea
·
-
14 votesDanny Stergiadis
supported this idea
·
-
17 votesDanny Stergiadis
supported this idea
·
-
483 votes
Hi,
We wanted to let you know that your idea is currently under review by our product team. We are evaluating its alignment with our product roadmap and its potential benefits to our users.
We appreciate your patience during this process and will update you and the public status of this suggestion once a decision has been made.
Best regards,
The Atera Team
Danny Stergiadis
supported this idea
·
-
966 votesDanny Stergiadis
supported this idea
·
-
9 votesDanny Stergiadis
supported this idea
·
Ideally, we need the ability to make a GET request to an endpoint structured similarly to: https://api.atera.com/api/v1/tickets/ticketId/billingitems (or an equivalent expansion on the existing /api/v1/tickets/{ticketId} endpoint)
This payload should return an array containing:
Product/Service ID and Name
Quantity applied
Unit price and total price
Associated cost
Exposing these billing items via the API will bridge the gap between technical execution and financial accuracy, allowing us to build a seamless, hands-off pipeline from ticket closure to invoice generation in our accounting system.