Nimbus API Skill

Nimbus WFM API authentication uses token-based access via REST endpoints. Obtain a valid token first, then include it in subsequent requests to OData and REST endpoints for employee, shift, activity, and schedule operations.

Nimbus WFM uses a non-standard CRUD pattern where POST handles both create and update operations rather than PUT or PATCH. This design choice affects how you structure integration requests for user management and shift operations.

ScheduleShift endpoints expect local times as input; the API automatically calculates and returns UTC times. Misaligning time zones or sending UTC directly causes scheduling errors, so verify your client sends local times consistently.

Nimbus endpoints use inconsistent field naming—some use Description, others Name—for similar data. Review endpoint-specific documentation to map the correct field names for Employees, Activities, and Shifts to avoid integration failures.

Nimbus WFM has limited server-side filtering for Deleted flags; client-side filtering is often necessary. Plan your integration to fetch data and filter locally rather than relying on server-side deletion queries.

Nimbus WFM provides OData endpoints for Employees, Shifts, Activities, and ScheduleShifts, while authentication and some user and shift operations use dedicated REST endpoints. Choose the appropriate endpoint type based on your integration requirements.