A laptop ordering API connects your ITSM or HR system directly to your device supplier, for example a Device as a Service provider like Everphone.
When HR adds a new employee, the order goes out automatically. The laptop arrives preconfigured, and status, serial number and delivery date flow back into your system. Nobody writes an email, nobody maintains a spreadsheet.
The biggest benefit is not convenience but reliability. An order sent by email can sit unread in an inbox, be mistyped or go out too late. With an API that doesn't happen, because the order is created straight from the onboarding ticket.
For the laptop to actually be ready on day one, the supplier has to work just as automatically after that. If someone there sets up every device by hand, the order arrives faster, but the laptop doesn't.
What a laptop ordering API does
The API turns an event in your system into an order with your supplier. The event might be "new joiner", "role change" or "leaver". The order might be "ship a laptop", "replace a device" or "start a return".
The return channel matters just as much. A good API doesn't only confirm "order received". It also reports which device, with which serial number, is on its way to whom. Only then does your ITSM know which asset belongs to which person without anyone entering it by hand.
At Everphone this runs through a REST API that connects to common ITSM tools, including ServiceNow, Jira, Freshservice, Ivanti, Matrix42 and Topdesk. HR systems and SAP can be connected too.
How a laptop order via API works
Here's an example: Lena starts in sales in three weeks. This is how her laptop reaches her once the integration is in place.
- HR adds Lena to the HR system. This creates an onboarding ticket in your ITSM.
- The ITSM recognises the role "sales" and knows which device bundle goes with it: say, a 14-inch business laptop, a smartphone and a headset.
- The API passes on the order with role, device bundle, start date and delivery address. That can be the office or Lena's home address.
- The laptop is preconfigured. For Windows devices that means registration in Windows Autopilot, for Macs in Apple Business Manager. Lena signs in with her work account on first start, and the device pulls its policies and apps on its own.
- Status and serial number are written back to the ticket, so shipping and delivery can be tracked there.
IT has one job in this process: deciding once which role gets which device bundle. After that, every further order runs without them.
The same principle covers the rest of the device lifecycle. A "broken display" ticket triggers a replacement. A leaver triggers the return, including a shipping label and certified data wiping.
API, portal or email: a comparison
There are three ways to order laptops. At Everphone, two of them lead into the same system: whatever you order in the Everphone portal is visible to your API, and whatever comes in via the API shows up in the portal.
| Email / form | Everphone portal | API from your ITSM | |
|---|---|---|---|
| Trigger | A person writes the order | A person clicks to order | An event in your ITSM or HR system |
| Source of errors | Typos, forgetting | Forgetting | Wrong mapping of role to device bundle (one-off) |
| Device data | Entered manually | Automatically in the portal | Automatically in the portal and your ITSM |
| Setup | None | None | One-off integration |
| Right for you if … | you rarely order | you order regularly but don't want to connect an ITSM | onboardings already start as tickets |
The portal is not a stopgap. If you don't want to connect an ITSM or only order a few laptops a quarter, it's the right place. And if you add the API later, you keep working on the same data.
What to look for in a laptop ordering API
Almost every provider mentions an "API" on their website these days. These questions separate a real integration from an order form with an endpoint.
Does the API cover the whole lifecycle?
Ordering is the easy part. What matters is whether replacements, upgrades, extensions and returns run through the API too. Otherwise you'll be back to emails within three months.
Does data come back?
Ask about serial numbers, delivery status and device assignment. Without a return channel, your IT team keeps maintaining asset data by hand.
How does authentication work?
OAuth 2.0 is the standard. A static API key that someone emails around is not.
Is there a test environment?
Without a sandbox, you test with real orders. Your accounts team will notice.
What happens behind the API?
Is the laptop really shipped preconfigured, with Autopilot registration, staging and BIOS settings? Or does it arrive in its original box, leaving IT to set it up after all?
Which manufacturers can you order?
An API that only lets you order one brand ties your fleet to that brand. For a mixed fleet of Windows laptops and MacBooks, you need a provider that works across manufacturers.
Ordering laptops via API with Everphone
Everphone rents out laptops, smartphones and tablets as Device as a Service. For notebooks and PCs the range covers Apple, Dell, HP and Lenovo. You can order in the Everphone portal or directly from your ITSM via the REST API. The API costs nothing extra.
The integration is simple. You get access tokens, documentation and a sandbox, and the API uses OAuth 2.0. Together with your ITSM team you define which events trigger which order. Our article on the ServiceNow integration shows what that looks like in practice.
The real work happens behind the API. Laptops arrive fully set up, with Autopilot registration and staging. Shipping is free, to the office or any address you choose. Faulty devices are replaced, returned devices are wiped to certified standards and refurbished. Instead of a purchase price, you pay a monthly rental fee, with repairs, replacements and management included.
You'll find more on renting laptops, PCs and accessories on our Workplace as a Service page.
Who a laptop ordering API is for
A laptop ordering API pays off when three things come together: you order devices regularly, you have an ITSM or HR system where onboardings already start as tickets, and your IT team spends noticeable time on orders, follow-ups and asset tracking.
If you only order a few laptops a year, you don't need an integration. You simply order in the Everphone portal and get the same devices with the same service.
Our recommendation: don't start with ordering, start with offboarding. A late order costs a few days. A laptop that disappears when someone leaves costs money and is a data protection risk. Once your API triggers returns reliably, you've fixed the most expensive mistake.
Frequently asked questions
Can I order laptops directly from ServiceNow?
Yes. With the Everphone REST API, events in ServiceNow, such as an onboarding ticket, automatically trigger a laptop order. Status and device data are sent back to ServiceNow.
Does the ordering API work with systems other than ServiceNow?
Yes. The API isn't tied to a particular ITSM. Jira, Freshservice, Ivanti, Matrix42, Topdesk, SAP and HR systems are among the systems it connects to.
Does the laptop arrive ready to use?
Yes. Windows laptops are registered in Windows Autopilot, Macs in Apple Business Manager. On first start, the employee signs in with their work account and the device loads policies and apps from your MDM.
What does the API cost?
Nothing extra. At Everphone the API is part of the service. You pay the monthly rental for your devices; connecting your ITSM costs nothing on top.
Do I need an API if I only order a few laptops?
Usually not. For a handful of orders a year, the Everphone portal is all you need. The API comes into its own when onboardings and offboardings happen regularly. Because the portal and API share the same data, you can add the API at any time.