Everhour integrations

Everhour integrations

→

Everhour → AFAS Profit

Everhour to AFAS integration: approved weekly timesheets as project costing in AFAS, leave back in planning

→

Everhour → Nmbrs

Everhour to Nmbrs integration: approved hours of hourly paid staff as variable hours, leave back in planning

→

Everhour → Visma Raet YouForce

Everhour to YouForce integration: approved clocked hours of hourly paid staff to payroll

→

Workday → Everhour

Workday to Everhour integration: approved time off and balances from Workday in Everhour, approved timesheets back to Workday

→

HiBob → Everhour

HiBob to Everhour integration: approved time off and balances from Bob in Everhour's resource planner

→

Personio → Everhour

Personio to Everhour integration: approved absences from Personio as time off in Everhour

Systems you can connect Everhour with

How KoppelHet connects to Everhour

REST API (JSON) on api.everhour.com, marked as beta by Everhour itself; version through the X-Accept-Version header. Endpoints for users (read only), projects, tasks, time records per team, user or project, timecards, timesheets with approval, time off and assignments in the resource planner, clients, invoices and expenses. Webhooks for events including api:time:updated and api:timer:stopped. Rate limit 100 requests per 10 seconds per key; above that 429 with Retry-After.

Authentication: API-sleutel uit het profiel van een gebruiker, in de header X-Api-Key; API-gebruik vraagt een betaald abonnement

Objects we connect

• Users
• Time records per project and task
• Timecards (clock in and out) and timesheets with approval
• Time off and time off types
• Projects, clients and budgets

What a Everhour integration does

• AFAS Profit, HiBob, Personio → to Everhour

  Leave from the HR system in the planning

  Approved leave from AFAS, HiBob or Personio arrives in Everhour as time off, so capacity planning works with who is actually there.

  Everhour → AFAS Profit integrationHiBob → Everhour integrationPersonio → Everhour integrationLeave, absence and time

• Everhour → to Nmbrs, Loket

  Approved hours to payroll

  Once the week is approved, clocked hours of hourly paid employees go to Nmbrs or Loket, per payroll period.

  Everhour → Nmbrs integrationLoket integrationsLeave, absence and time

• Everhour → to Exact Online, Unit4 ERP

  Project hours to finance

  Hours per project and employee go to Exact Online or Unit4, so project costs in the accounts match what was booked.

  Exact Online integrationsUnit4 ERP integrationsHR to ERP

What to watch for

• The API key belongs to one user and works with that user's rights. Use an account for the integration that may see the whole team's hours.
• The documentation describes no way to create users through the API. New employees are invited in Everhour itself; the integration matches them on email address.
• Everhour calls the API beta. Test the integration after a change on Everhour's side, or set a fixed version in the request.

In your IT landscape

• Runs as a managed integration on the KoppelHet platform, next to your existing integration layer. No VPN into your network.
• Only the fields in the design you approve are transferred. The platform keeps no register of its own.
• Tested first in the test or acceptance environment where there is one. You choose the go-live moment.
• ISO 27001 certified, hosted in Amsterdam. When the contract ends you receive the configuration and the audit logs.

Implementation, architecture and compliance

Processes with this system

• Leave, absence and time