Integrate what exists. Build what doesn't.

Native HRIS & ticketing integrations — plus a public API for anything you want to automate beyond them.

When native isn't enough, you build

The Open API lets your team wire quipteams into anything — custom onboarding scripts, internal tools, device lifecycle flows, ticketing systems. If you can call an API, you can automate it.

  • Trigger device orders from any system, not only HRIS
  • Pull live device data into BI dashboards or internal tools
  • Build custom approval flows before an order is placed
  • Webhook any state change — shipped, delivered, retrieved
Read the API docs →
# Trigger a device order from your HRIS
POST /v1/devices/orders
{
"employee": "vijay@acme.com",
"country": "IN",
"device": "macbook-pro-14",
"enrollment": "zero-touch"
}
delivered in 4 days, ABM-enrolled
FAQ

Integrations & API questions

Common questions about our native HRIS integrations and the public API.
Which HRIS and ticketing tools does quipteams integrate with natively?

quipteams has native integrations with BambooHR, HiBob, Rippling, Workday, Deel, Gusto, Namely, Justworks, Personio, Okta, ClickUp, Jira and Zendesk among others — covering most HRIS, SSO and ticketing tools used by distributed teams. New integrations ship regularly.

What does an HRIS integration actually do for my team?

When a new hire is created or an employee is offboarded in your HRIS, quipteams automatically receives the signal and provisions or retrieves the right equipment — no manual ticket, no CSV upload, no copy-pasting. Equipment is ready before day one, and offboarding retrievals start the moment someone's termination date is set.

Is my employee data safe, and where does it live?

Employee data stays in your HRIS as the source of truth. quipteams only syncs the fields needed to provision and retrieve equipment (name, email, start/end date, location) — encrypted in transit (TLS 1.2+) and at rest (AES-256). Integration credentials are stored encrypted and scoped to the minimum permissions required. We never write back into your HRIS, and you can revoke access at any time from your dashboard.

What if my HRIS isn't on the list?

Tell us. We use a unified HRIS layer that lets us add most providers quickly without a custom build on your side. In the meantime, you can manage employees manually from the quipteams dashboard or via the public API — both work without any HRIS connected.

How long does it take to set up an integration?

Most HRIS integrations are live in under 15 minutes from your quipteams dashboard: authorize, select which employee segments to sync, done. Ticketing integrations (Jira, Zendesk, ClickUp) usually take a bit longer because we map statuses and project/board IDs — plan on 30-45 minutes with your admin on the call.

What can I do with the quipteams API?

Programmatic access to everything in the platform: create and action quotes, list and manage assets, create device actions (retrievals, transfers, wipes, deployments), add devices to inventory, browse the product and kit catalog, manage webhook subscriptions, and read employee and office data synced from your HRIS. The full API reference lives at api.quipteams.com/docs.

How do I set up API authentication?

Bearer tokens in the Authorization header. Two environments — production and sandbox — so you can test end-to-end before touching real orders. Create keys in company settings: qk_live_... for production, qk_test_... for sandbox. Keys are shown once at creation and can't be retrieved later, so store them securely. Revoke a compromised key instantly from the dashboard.

Is the API production-ready? What about rate limits?

Yes — it's a stable v1 with 24 endpoints across Quotes, Assets, Device Actions, Devices, Products & Kits, Webhooks, Employees and Offices. Each API key has a per-minute request budget; every response returns X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers so you can pace your integration. On 429s we include a Retry-After header.

Can I subscribe to real-time events?

Yes, via webhooks. Register up to 10 webhook endpoints per company, choose the events you care about (tracking updates, delivery status, device action changes), and quipteams sends signed POST requests to your endpoint. You get a signing secret at creation for verification, and there's a test endpoint to confirm your URL is reachable before going live.

Do I need engineering resources to use it?

For HRIS sync and native integrations, no — it's all no-code from the dashboard. For the public API directly, yes: it's a REST API with JSON, Bearer auth and cursor pagination, designed for IT teams with dev capacity or teams using iPaaS tools like Zapier, Make, n8n or Workato. We have a Postman collection so your engineer can be testing calls within 5 minutes.

Got questions?

Grab 10 minutes with Andy. Bring your hardest country. Brazil, India, wherever, we'll walk you through it.

Schedule now