SeamlessHR

Access and limits

Authentication

Client ID and client secret (x-client-id / x-client-secret headers)

Plans and access

SeamlessHR customers (Africa, primarily Nigeria) with API access enabled for their company. Client ID and client secret are issued by SeamlessHR on request (support@seamlesshr.com) and grant company-wide access to the modules enabled for them.

Test environment

SeamlessHR documents a test environment at api-sandbox.seamlesshr.app; request sandbox credentials from support@seamlesshr.com.

Rate limits

SeamlessHR does not publish numeric limits. Its docs say rate limiting is usually returned as HTTP 503 with a Retry-After header; Nexra treats that as a rate limit and backs off. HTTP 429 is documented as the employee-limit error when adding employees, which this connector never does.

Pagination

Attendance uses page and perPage with meta.to and meta.total. Employees use page and limit (default 10). Job postings return 10 per page with meta.current_page and meta.last_page. Leave requests, employees on leave and leave policies return a meta paginator; Nexra sends page while meta reports more pages. Org, contract type and reference lists are single pages.

Provider events

SeamlessHR webhooks for employee created, updated and deactivated, birthdays, work anniversaries and leave request events, signed with HMAC SHA-512 in x-seamlesshr-signature. The webhook URL is configured by SeamlessHR. Flows can start the moment something happens: when a new employee is added; when an employee's details change; when an employee leaves; when a leave request is approved.

Before you build a flow

• Read-only. Adding, updating, activating, deactivating or exiting employees, creating or updating departments, job roles and contract types, loans, payments, attendance sync and performance (KPIs, objectives) writes are intentionally not implemented. Deletes are never implemented.
• The public recruitment (RMS) API covers job postings, companies, specialisations, countries and states only. Candidates, applicants, applications, stages, notes, offers and hires are not in the public API, so they cannot be read or written; no rejection, stage move, offer or hire is automated.
• Sensitive fields are never mapped: salary, net pay, pay group and grade, bank and account numbers, pension and tax PINs, loans, date of birth, age, sex, marital status, religion, state of origin, personal email, phone numbers, addresses, next of kin, qualifications, experience, photos, exit reasons and remarks, and leave reasons or proof documents. Birthdays, pay groups, payroll, ledger and pay-item endpoints are not used.
• Email addresses and phone numbers are never sent in URLs: direct reports are looked up by employee code only, and employee search refuses values that contain @ or look like phone numbers.
• No updated-since filter is documented. Employees can be filtered by creation date (date) and by employment or exit date ranges.
• Departments, job roles and contract types have no numeric ID in the API; Nexra uses the department or job role code when set, otherwise the name, and the contract type title.
• Date-range filters are sent as indexed array parameters (employment_date[0], employment_date[1]); SeamlessHR documents the employment_date[] form, which PHP parses identically.
• Attendance (clock-ins) is read from Get Attendance Records with a custom date range. It needs SeamlessHR's Time and Attendance module; where the business doesn't use it, the read returns no rows and Nexra's "Who's in today" falls back to active employees minus those on leave. Bulk Sync Attendance Records (a write) is not implemented.
• The page parameter for leave requests, employees on leave and leave policies is inferred from the meta paginator the docs show; it is not listed as a parameter. Without meta, these lists return a single page.
• Get employee puts the staff ID in the URL path, so staff IDs containing a slash (for example ADV/FTE/22/09) are refused; find them with List employees and search.
• The employee page-size maximum is not documented; Nexra caps limit at 100.
• Locations: there is no locations or branches endpoint. Employee records include branch, region and deployed state, and RMS countries and states give job-posting locations. Whether other org unit tags (for example branch) are accepted is not documented.
• RMS endpoints are documented for career pages; whether a client credential sees every job state (DRAFT, SUSPENDED) depends on SeamlessHR's configuration.

Developer reference