APIs
61 TopicsInconsistent monetary information for Japan via Billing v2 API
Hi, we have a presence in different Equinix data centers and retrieve billing information via the Billing v2 API. We observed that the information we obtain for the Japan invoice (and that one only) has inconsistent (dare I say wrong?) tax amount values across time: For invoices from 2024-02 (oldest I have) until 2024-05 (which is not downloadable anymore due to the 12 month limit but I have a local copy) the Japanese line items behave exactly like all others we can observe, namely: non-zero taxAmount (10% of recurringAmount) and recurringAmount + taxAmount = totalAmount. For invoices from 2024-06 until 2024-08 (both in the snapshot I had from a few months ago and the one I just took now) the Japanese line items now still has a non-zero taxAmount (10% of recurringAmount) but totalAmount = recurringAmount. Checking a few entries we saw that the netAmount is the same as in previous entries which makes me assume that the totalAmount does not include any tax amount. For invoices from 2024-09 onward the Japanese line items now all have taxAmount = 0 and totalAmount = recurringAmount. This means that we are unable to obtain any tax information from the invoice other than assuming that the 10% applies to all line items. Furthermore, this data is inconsistent with the reality that there is tax to be paid. Could you explain why the data is so inconsistent, changing multiple times withing a few months? Could you also explain why the data for invoices since 2024-06 is inconsistent with the reality? Is there any resource where changes in the API are documented and where I could have learned about these changes? What can we expect moving forward? Should we expect the data to change again, hopefully to be correct again as it was pre 2024-06? Thanks JonasSolved73Views0likes3CommentsBilling v2 API deprecation?
Hello, today I noticed that on the API documentation overview page it says that the Billing_v2 API is Deprecated. I can't find any further information on that and also noticed that, in contrast to the WorkVists_v1 API which is marked in the same way, no deprecation information can be found on the actual documentation page. Would you be able to provide some more information on the deprecation or links to where I can find it? I'm especially interested in whether this API is actually going to be disabled in the future and if there's any alternative to obtain invoice information programmatically and machine-readable. Thanks, JonasSolved110Views1like3CommentsECP APIs Cage Clean Up on a Smart Hands Order
In this video, how to create a basic Smart Hands Cage Clean up order in sandbox environment using Equinix Smart Hands APIs. We'll start by obtaining an Access Token using the Equinix Authentication APIs. Next, we'll identify the location details for the Smart Hands order. Then we'll place the Smart Hands Cage Clean up Order using the location details obtained in the previous step. We''ll finish by entering the usernames of the Ordering, Technical, and Notification contact(s). For more documentation on APIs, visit docs.equinix.com5Views0likes0CommentsECP APIs Creating an Unlisted Smart Hands Order
In this video, how to create a basic unlisted Smart Hands Order in Sandbox environment using Equinix Smart Hands APIs. We'll start by obtaining an Access Token using the Equinix Authentication API. Next, we'll identify the location details for the Smart Hands Order (IBX, Cage, and Account). Then we'll place the unlisted Smart Hands Order. Finally, we'll enter the usernames for Notification, Technical, and Ordering contacts. For more documentation on APIs, visit docs.equinix.com6Views0likes0CommentsECP APIs Creating an Inbound Shipment Order
In this video, we'll show you how to create a basic Inbound Shipment order in sandbox environment using Equinix Shipment APIs. We'll start by obtaining an Access Token using the Equinix Authentication API. Next we'll identify the destination for this Shipment Order. Then we'll create the Inbound Shipment order and enter the information we've obtained in previous steps. We'll finish by entering the contact information usernames. For more documentation on APIs, visit docs.equinix.com7Views0likes0CommentsECP APIs Creating an Outbound Shipment Order
In this video, we'll show you how to create a basic Outbound Shipment order in the sandbox environment using Equinix Shipment APIs. First we'll obtain an Access Token using Equinix Authentication APIs. Then we'll identify the place of departure for the shipment order, taking note of the IBX, cage ID, and account number. Next we'll create the Outbound Shipment order, using the details we obtained earlier. Finally, we'll enter the usernames of the Ordering and Notification contacts. For more documentation on APIs, visit docs.equinix.com5Views0likes0CommentsECP APIs Creating a Trouble Ticket
In this video, we'll show you how to create a basic Trouble Ticket in the sandbox environment using Equinix Trouble Ticket APIs. We'll start by obtaining an Access Token using the Equinix authentication API. Then we'll identify the Trouble Ticket categories available to us and note the Trouble Ticket problem code. Next, we'll find the location of the issue for this Trouble Ticket. Using all of the information gathered in the previous steps, we'll create a Trouble Ticket. For more documentation on APIs, visit docs.equinix.com6Views0likes0CommentsDo not notify via email after scheduled report is generated
Hi, I'm using the reports v1 API to generate ONE_TIME reports and every time the report is finished, I get an email telling me as much. However, I want to prevent this email from going out every time. I've figured out that I can use the parameters array with name notifyEmails to add additional emails that should be notified but I can't seem to be able to remove the email tied to my account. Is there any way to achieve what I want?155Views0likes4Comments