UKG Ready API Integration Vol.2

These are the list of integration use cases supported by Knit for UKG Ready API as part of the HRIS category

Get Pay Calculation Profiles

ID: get_pay_calculation_profiles
Operation: read
Entities: profile, pay calculation profile, company
Summary: The 'Get Pay Calculation Profiles' API returns a list of Pay Calculation Profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profiles, each with an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Categories

ID: get_pay_categories
Operation: read
Entities: timesheet, pay category, company
Summary: The Get Pay Categories API returns a list of defined pay categories in a specified company. It requires the company ID as a path parameter and additional query parameters including the date of the timesheet, the timesheet owner ID, and the type of record to assign the pay category to. The response includes an array of items, each containing an ID, name, code, and description of the pay category.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Grades

ID: get_pay_grades
Operation: read
Entities: profile, pay grade, company
Summary: The Get Pay Grades API returns a list of pay grades for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of pay grade objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status for successful requests, while 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable are possible error responses.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Information

ID: get_pay_information
Operation: read
Entities: pay information, employee, company
Summary: The Get Pay Information API retrieves the pay information of an employee. It requires two path parameters: 'cid' for the company identifier and 'aid' for the account identifier. The API checks for access rights based on the security profile in the company settings. The response includes detailed pay information such as job details, eligibility for benefits, payroll classification, and more. The API returns various HTTP status codes including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Period

ID: get_pay_period
Operation: read
Entities: employee, pay period, company
Summary: The Get Pay Period API allows the caller to retrieve a specific pay period by its ID. It requires two path parameters: 'cid', which is the company identifier, and 'pay_period_id', which is the identifier for the pay period. The response includes details about the pay period such as the pay period profile, EIN details, total employees, locked employees, available employees, and various dates related to the pay period. The response is returned in JSON format and includes fields like 'start_date', 'end_date', 'pay_date', 'submit_date', and 'process_date'. The API returns a 200 OK response on success, and may return errors such as 400 Bad Request, 403 Forbidden, or 503 Service Unavailable in case of validation errors, security errors, or service unavailability, respectively.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Period Profiles

ID: get_pay_period_profiles
Operation: read
Entities: pay period profile, company
Summary: The 'Get Pay Period Profiles' API returns a list of Pay Period Profiles for a specified company. It requires a path parameter 'cid' which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable errors under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Periods

ID: get_pay_periods
Operation: read
Entities: pay period, company
Summary: The Get Pay Periods API allows the caller to retrieve a list of pay periods for a specified company, identified by the company ID (cid) in the path parameters. The response includes details about each pay period, such as the pay period profile ID, EIN details, total employees, locked employees, available employees, start and end dates, pay date, submit date, process date, and whether the period is locked. The API returns a 200 OK response on success, and may return 400 Bad Request, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Prep Profiles

ID: get_pay_prep_profiles
Operation: read
Entities: profile, company
Summary: The Get Pay Prep Profiles API retrieves a list of Pay Prep Profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API returns a 200 OK status on success, with potential error responses including 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Statement

ID: get_pay_statement
Operation: read
Entities: pay statement, employee, company
Summary: The Get Pay Statement API retrieves detailed information about an employee's pay statement. It requires the company ID (cid), payroll ID, and pay statement ID as path parameters. The response includes details such as employee account ID, pay date, status, type, pay period start and end dates, deductions, earnings, messages, and payments. The API returns various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Statement Types

ID: get_pay_statement_types
Operation: read
Entities: pay statement type, company
Summary: The 'Get Pay Statement Types' API endpoint is used to fetch a list of supported pay statement types for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of items, each containing an 'id' and a 'display_name' representing different pay statement types. The API returns a 200 OK status on success, while 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable are possible error responses.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Statements

ID: get_pay_statements
Operation: read
Entities: payroll, pay statement, company
Summary: The Get Pay Statements API retrieves information about all payroll pay statements for a specified company and payroll. It requires two path parameters: 'cid' which is the company identifier and 'id' which is the payroll identifier. The response includes an array of pay statements, each containing details such as employee account ID, pay date, status, type, pay period start and end dates, and a self-link. The API returns various HTTP status codes including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Pay Types

ID: get_pay_types
Operation: read
Entities: pay type, company
Summary: The Get Pay Types API endpoint is used to fetch a list of pay types for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of pay types, each with an 'id', 'name', and 'external_id'. The API returns a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Payroll

ID: get_payroll
Operation: read
Entities: payroll, company
Summary: The Get Payroll API retrieves detailed information about a specific payroll for a company. It requires two path parameters: 'cid', which is the company identifier, and 'id', which is the payroll identifier. The response includes details such as the payroll's name, pay date, type, status, and whether it is billable. The API returns various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Payroll Batch Types

ID: get_payroll_batch_types
Operation: read
Entities: payroll batch type, company
Summary: The 'Get Payroll Batch Types' API endpoint is used to fetch a list of supported payroll batch types for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of items, each containing an 'id', 'display_name', and 'active' status. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Payroll Export Formats

ID: get_payroll_export_formats
Operation: read
Entities: payroll, pay period, company
Summary: The Get Payroll Export Formats API allows the caller to retrieve a list of available payroll export formats for a specified pay period. The export format is necessary for the Export Payroll API to define the layout of the resulting Payroll Interface File. The response includes basic information about each format and details of any user prompts configured. Values for each user prompt must be specified at runtime when calling the Export Payroll API. The user must have permission to run pay-prep and requires at least one of the following subsystems: PR or TLM. The API requires two path parameters: 'cid' (company identifier) and 'pay_period_id' (pay period identifier). The response includes a list of payroll export formats, each with an ID, name, file type, format type, and optional user prompts.
Input Fields: Input Fields
Output Fields: Output Fields

Get Payroll Export Status

ID: get_payroll_export_status
Operation: read
Entities: payroll export, pay period, company
Summary: The Get Payroll Export Status API allows the caller to retrieve the status of a payroll export job. It requires the company ID (cid), pay period ID (pay_period_id), and job ID (job_id) as path parameters. The response includes the job's status, total processes, completed successes, completed errors, last modified timestamp, and a temporary download link if the export is completed. The download link is valid for 10 minutes and contains an encrypted authentication token for secure access. The API returns various HTTP status codes, including 200 for success, 403 for security errors, 404 if not found, and 503 if the service is unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Payroll Types

ID: get_payroll_types
Operation: read
Entities: payroll type, company
Summary: The Get Payroll Types API endpoint is used to fetch a list of supported payroll types for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response returns a list of payroll types, each with an 'id' and 'display_name'. The API can return various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Payrolls

ID: get_payrolls
Operation: read
Entities: type, payroll, company
Summary: The Get Payrolls API endpoint is used to fetch a list of payrolls for a specified company. The endpoint requires a path parameter 'cid', which is the company identifier. The response includes an array of payroll objects, each containing details such as id, name, pay_date, start_date, end_date, type, status, ein, and billable status. The type and ein are objects with their own properties. The response also includes a '_links' object with a 'self' link for each payroll.
Input Fields: Input Fields
Output Fields: Output Fields

Get Paystatement Population

ID: get_paystatement_population
Operation: read
Entities: paystatement, profile, company
Summary: The Get Paystatement Population API returns a list of paystatement population profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable errors under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Performance Review

ID: get_performance_review
Operation: read
Entities: profile, performance review, company
Summary: The Get Performance Review API returns a list of Performance Review Profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Points Profiles

ID: get_points_profiles
Operation: read
Entities: profile, point, company
Summary: The Get Points Profiles API returns a list of Points profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of profile items, each with an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Position

ID: get_position
Operation: read
Entities: profile, position, company
Summary: The Get Position API retrieves the details of a specific position within a company, identified by the company ID (cid) and position ID (positionId). The API endpoint is accessed via a GET request to the specified URL. The path parameters 'cid' and 'positionId' are required to identify the company and position respectively. The response includes detailed information about the position, such as position ID, name, title, payroll code, currency details, and various profiles associated with the position. The API returns a 200 OK response on success, with a detailed JSON object containing all the position details. In case of errors, it may return 401 Unauthorized, 403 Forbidden, 404 Not Found, or 503 Service Unavailable, depending on the issue encountered.
Input Fields: Input Fields
Output Fields: Output Fields

Get Position Assignments Changed

ID: get_position_assignments_changed
Operation: read
Entities: position assignment, assignee, company
Summary: The 'Get Position Assignments Changed' API retrieves information about position assignments that have been created, modified, or deleted within a specified timeframe for a given company. The API requires a path parameter 'cid' which is the company identifier. The response includes detailed information about each assignment, such as assignment ID, position details, assignee information, compensation details, and more. The response status can be 'CREATED', 'MODIFIED', or 'DELETED'. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Positions

ID: get_positions
Operation: read
Entities: profile, position, company
Summary: The Get Positions API returns information about all active and effective positions as of a specified date, or today if no date is provided. It allows consumers to specify the details they want for each position, with basic details returned by default. The API requires a path parameter 'cid' to specify the company, which can be referenced by company id, unique id, or short name. The response includes a list of positions with detailed attributes, budgets, reporting positions, job details, and various profiles. The API returns a 200 OK response on success, with possible error responses including 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Premium Shifts

ID: get_premium_shifts
Operation: read
Entities: premium, shift, company
Summary: The Get Premium Shifts API returns a list of defined shift premiums for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of shift premium objects, each containing an 'id', 'name', 'code', and 'description'. The response schema also includes a '_total_count' field indicating the total number of items.
Input Fields: Input Fields
Output Fields: Output Fields

Get Process Records Status

ID: get_process_records_status
Operation: read
Entities: process record, pay period, company
Summary: The 'Get Process Records Status' API allows the caller to retrieve the processing status of the 'Process Records' business step. It requires the path parameters 'cid' (company identifier), 'pay_period_id' (pay period identifier), and 'job_id' (job identifier) to be specified. The response includes the status of the process, a summary of results, the total number of processes, and the number of successful and erroneous completions. The response status can be one of 'NONE', 'NEW', 'RUNNING', 'DONE', 'FAILED', or 'CANCELED'. Possible HTTP response codes include 200 (OK), 403 (Forbidden), 404 (Not Found), and 503 (Service Unavailable).
Input Fields: Input Fields
Output Fields: Output Fields

Get Project Information

ID: get_project_information
Operation: read
Entities: project, employee, company
Summary: The Get Project Information API endpoint returns detailed information about a specific project within a company. The project management functionality must be enabled in the company. The API requires two path parameters: 'cid', which is the company identifier, and 'projectId', which is the project identifier. The response includes various details about the project such as its name, business purpose, percent completion, description, start and end dates, cost center list ID, budget amount, status, employees, managers, and associated EIN details. The API returns a 200 OK response on success, and may return errors such as 401 Unauthorized, 403 Forbidden, 404 Not Found, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Project Metrics

ID: get_project_metrics
Operation: read
Entities: metric, project, company
Summary: The Get Project Metrics API endpoint returns information related to the project metrics. It requires the project management functionality to be enabled in the company. The API takes two path parameters: 'cid', which is the company identifier, and 'projectId', which is the project identifier. The response includes details such as the project name, budget logged, remaining budget, total budget amount, remaining days, and currency code. The API returns various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource does not exist, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get PTO Request

ID: get_pto_request
Operation: read
Entities: pto request, employee, company
Summary: The Get PTO Request API endpoint provides information about a single time off request for an employee within a company. It requires two path parameters: 'cid', which is the company identifier, and 'rid', which is the time off request id. The response includes details about the employee, the time off request, and additional PTO details such as request state, requested time, and approval information. The response is returned in JSON format with a status of 200 OK.
Input Fields: Input Fields
Output Fields: Output Fields

Get PTO Request Notes

ID: get_pto_request_notes
Operation: read
Entities: pto request, note, company
Summary: The Get PTO Request Notes API retrieves all notes associated with a time off request for a specified company. The request requires a path parameter 'cid' to identify the company and a query parameter 'note_thread_id' to specify the note thread. The response includes an array of notes, each containing an ID, text, creation timestamp, and creator details. The API returns a 200 OK response on success or a 400 Bad Request if invalid query parameters are provided.
Input Fields: Input Fields
Output Fields: Output Fields

Get Questionnaire

ID: get_questionnaire
Operation: read
Entities: questionnaire, benefit enrollment, job requisition
Summary: The Get Questionnaire API endpoint is used to fetch questionnaires related to Job Requisition, Benefit Enrollment, Recruitment Evaluation, or Peer Feedback for a specific company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of questionnaire items, each with an 'id', 'display_name', and 'description'. The API returns a 200 OK status on success, and may return 404 Not Found if the questionnaire object is not found, 403 Forbidden for security errors, or 400 Bad Request for validation errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Rate Schedules

ID: get_rate_schedules
Operation: read
Entities: rate schedule, rate table, company
Summary: The Get Rate Schedules API retrieves all rate schedules data of a specified rate table for a company. It requires two path parameters: 'cid' (the company identifier, which can be a company id, unique id, or short name) and 'tid' (the rate table id). The API returns a detailed list of rate schedules, including information such as rate table details, rate items, usage, and various records related to time entry, payroll, and counters. The response includes a comprehensive schema detailing each rate schedule's properties, such as id, line, type, description, and associated records. The API handles various response codes, including 200 for success, 404 if the rate table is not found, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Rate Table

ID: get_rate_table
Operation: read
Entities: rate table, owner, company
Summary: The Get Rate Table API endpoint is used to fetch details of a rate table by its ID. This API requires the 'Rates' functionality to be enabled for the company. The request must include the company ID (cid) and the rate table ID (tid) as path parameters. The response includes detailed information about the rate table, such as its name, description, currency, owner details, and links for further actions. The API returns various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Rate Tables

ID: get_rate_tables
Operation: read
Entities: currency, rate table, company
Summary: The Get Rate Tables API retrieves all rate tables, both company and personal, configured within a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of rate tables with details such as id, name, description, currency, and links for actions like edit, reapply rates, and download. The response also includes metadata about the total count of rate tables and links for self and create actions. The API returns various HTTP status codes including 200 for success, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Reason Codes

ID: get_reason_codes
Operation: read
Entities: timesheet, reason code, company
Summary: The Get Reason Codes API retrieves a list of defined reason codes for a specified company. The request requires the company ID as a path parameter, and the date, owner ID, and type as query parameters. The response returns a list of reason codes, each with an ID and display name.
Input Fields: Input Fields
Output Fields: Output Fields

Get Recent Punches

ID: get_recent_punches
Operation: read
Entities: punch, employee, company
Summary: The Get Recent Punches API retrieves a list of the last N punches for a specified employee within a company. The API requires two path parameters: 'cid' for the company identifier and 'aid' for the account identifier. The response includes an array of punch objects, each containing a timestamp, type, and optionally cost centers. The punch type can be one of several predefined values such as PUNCH_IN, PUNCH_OUT, CHANGE_CCS, etc. The API returns a 200 OK response on success, with potential error responses including 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Referrals

ID: get_referrals
Operation: read
Entities: resource, referral, company
Summary: The Get Referrals API endpoint is used to fetch a list of supported referrals for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of referral items, each containing an 'id', 'code', and 'name'. The API returns a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Refresh Token

ID: get_refresh_token
Operation: read
Entities: token, employee, authentication
Summary: The Get Refresh Token API allows clients to obtain a newly generated token by sending a GET request to the specified endpoint. A valid authentication token must be included in the request headers under 'Authorization'. The response will include a new token, its time to live (ttl), and the units for the ttl. If the authentication token is invalid, a login error will be returned. Possible responses include 200 OK for successful login, 401 Unauthorized if authentication is required, and 403 Forbidden if the refresh token is forbidden due to reasons such as the employee being locked, terminated, or deleted.
Input Fields: Input Fields
Output Fields: Output Fields

Get Attendance

ID: get_regularized_attendance
Operation: read
Entities: attendance
Summary: The Get Attendance API retrieves attendance data for a specific employee. It requires two path parameters: 'cid' for the company ID and 'aid' for the account ID. The response includes the employee's attendance status, the last start time, the last punch action type, and associated cost centers. The API returns a 200 OK response on success, with possible error responses including 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Reports

ID: get_reports
Operation: read
Entities: report, user, company
Summary: The Get Reports API retrieves a list of available reports. The response format is determined by the 'Accept' header, which is required. Query parameters can be used to specify a client company by providing 'company', 'company:shortname', 'company:id', or 'company:external_id'. If no query parameters are provided, the service returns reports for the current user. The response includes a list of report IDs. Possible responses include 200 OK, 400 Bad Request for invalid or missing parameters, and 500 Internal Server Error for server issues.
Input Fields: Input Fields
Output Fields: Output Fields

Get Retirement Plan Profiles

ID: get_retirement_plan_profiles
Operation: read
Entities: retirement plan profile, company
Summary: The Get Retirement Plan Profiles API returns a list of retirement plan profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable errors under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Role Profiles

ID: get_role_profiles
Operation: read
Entities: role profile, company
Summary: The Get Role Profiles API returns a list of role profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of role profiles, each with an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Schedule

ID: get_schedule
Operation: read
Entities: schedule, time zone, company
Summary: The Get Schedule API retrieves a schedule by its ID. It requires the Advanced Scheduler (SCHEDULE) Subsystem to be enabled in the company setup. The API endpoint requires two path parameters: 'cid', which is the company identifier, and 'schedule_id', which is the schedule identifier. The response includes detailed information about the schedule, such as its ID, settings ID, name, start and end dates, status, time zone, and associated cost centers. The response also includes links for further actions like self, delete, and unpost. The API returns various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Schedule Settings

ID: get_schedule_settings
Operation: read
Entities: time zone, schedule setting, company
Summary: The Get Schedule Settings API retrieves the list of schedule settings required to create a schedule in the system. It requires the Advanced Scheduler (SCHEDULE) Subsystem to be enabled in the company setup. The API takes a path parameter 'cid', which is the company identifier. The response includes a list of settings, each with details such as id, name, cycle length, time zone, scheduled cost centers, and cost centers trees. The response may also include user messages and errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Scheduled Deductions

ID: get_scheduled_deductions
Operation: read
Entities: deduction, account, company
Summary: The Get Scheduled Deductions API retrieves all account deductions available within a specified company. The API requires a path parameter 'cid', which is the company identifier. The response includes a list of account deductions with details such as deduction type, account information, currency, active dates, calculation methods, payroll frequency, and settings for child support and garnishments. The API returns a 200 OK response on success, and may return 401 Unauthorized, 400 Bad Request, or 403 Forbidden for errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Scheduled Earnings

ID: get_scheduled_earnings
Operation: read
Entities: employee, earning, company
Summary: The Get Scheduled Earnings API returns a list of scheduled earnings filtered by the specified company ID. The company ID is a required path parameter and can be referenced via company ID, unique ID, or short name. The API responds with a list of earnings, each containing details such as earning ID, name, code, sequence, active dates, amount, frequency, currency, and employee information. The response includes a detailed schema of the earnings with properties like calculation method, frequency type, and employee details. The API supports standard HTTP response codes including 200 for success, 401 for unauthorized access, 400 for bad requests, and 403 for forbidden access due to insufficient rights.
Input Fields: Input Fields
Output Fields: Output Fields

Get Scheduler

ID: get_scheduler
Operation: read
Entities: cost center, schedule, company
Summary: The Get Scheduler API retrieves a list of schedules for a specified company. The company is identified by a path parameter 'cid', which is required. The API also requires two query parameters, 'from' and 'to', which define the date range for the schedules. The response includes a list of schedules with details such as schedule ID, settings ID, name, start and end dates, status, time zone, and associated cost centers. The response also includes links for further actions on the schedules. The API requires the Advanced Scheduler subsystem to be enabled in the company setup.
Input Fields: Input Fields
Output Fields: Output Fields

Get Scheduler Profiles

ID: get_scheduler_profiles
Operation: read
Entities: scheduler profile, company
Summary: The Get Scheduler Profiles API returns a list of scheduler profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of scheduler profiles, each with an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Schedules

ID: get_schedules
Operation: read
Entities: schedule, employee, company
Summary: The Get Schedules API fetches schedule items for a single user within a specified date range, which must not exceed 31 days. The company ID is specified as a path parameter, and the employee can be identified using various query parameters such as system ID, external ID, or username. The API returns a detailed schedule for the specified user, including shift details, cost centers, job information, and working status. The response includes a list of schedules with attributes like date, shift number, type name, start and end times, total hours, and more. The API supports only companies with TLM functionality and returns various HTTP status codes based on the request's validity and server status.
Input Fields: Input Fields
Output Fields: Output Fields

Get Security Profiles

ID: get_security_profiles
Operation: read
Entities: security profile, company
Summary: The Get Security Profiles API returns a list of security profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of security profiles, each with an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Service Account

ID: get_service_account
Operation: read
Entities: service account, security profile, company
Summary: The Get Service Account API endpoint is used to fetch a service account by its ID. It requires two path parameters: 'cid', which is the company identifier and can be a company id, unique id, or short name, and 'id', which is the service account id. The API returns a JSON object containing details about the service account, including username, external id, locked status, security profile, service type, login permissions, company group ids, edit permissions, and account group ids. The possible responses include 200 OK for a successful request, 401 Unauthorized if the user is not authorized, 403 Forbidden if the user has no access, 404 Not Found if the resource does not exist, and 503 Service Unavailable if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Get Service Accounts

ID: get_service_accounts
Operation: read
Entities: service account, security profile, company
Summary: The Get Service Accounts API retrieves all service accounts available within a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of service accounts, each with details such as account ID, username, external ID, lock status, security profile, service type, login permissions, company group IDs, edit permissions, and account group IDs. The API returns a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Shift

ID: get_shift
Operation: read
Entities: shift, schedule, company
Summary: The Get Shift API retrieves a specific shift by its ID. It requires the Advanced Scheduler (SCHEDULE) Subsystem to be enabled in the company setup. The API endpoint requires three path parameters: 'cid' (the company identifier), 'schedule_id' (the schedule identifier), and 'shift_id' (the shift identifier). The response includes detailed information about the shift, such as its type, start and end times, associated cost centers, skills, day type, shift premium, and more. The API returns various HTTP status codes, including 200 for a successful request, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Shifts

ID: get_shifts
Operation: read
Entities: shift, schedule, company
Summary: The Get Shifts API retrieves a list of shifts within a specified schedule for a company. The Advanced Scheduler (SCHEDULE) Subsystem must be enabled in the company setup. The API requires two path parameters: 'cid', which is the company identifier, and 'schedule_id', which is the schedule identifier. The response includes detailed information about each shift, such as shift ID, account details, date, type, shift start and end times, cost centers, skills, shift premiums, and more. The API returns a 200 OK response on success, with potential error responses including 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Skills

ID: get_skills
Operation: read
Entities: skill, company
Summary: The Get Skills API endpoint is used to fetch a list of defined skills within a company. It requires a path parameter 'cid', which is the company identifier. The response includes an array of skill objects, each containing an 'id', 'name', 'category', and 'schedulable' status. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Snapshots

ID: get_snapshots
Operation: read
Entities: snapshot, pay period, company
Summary: The Get Snapshots API allows the caller to retrieve the list of available snapshots for a specified pay period. The snapshots can be used in the Export Payroll API to define the data that should be included in the resulting Payroll interface file. The API requires two path parameters: 'cid', which is the company identifier, and 'pay_period_id', which is the identifier for the pay period. The response includes a list of snapshots, each containing an 'id', 'created_by' information with 'account_id' and 'display_name', and 'created_at' timestamp. The API returns a 200 OK response on success, 403 Forbidden in case of security errors, and 503 Service Unavailable if the service is unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Succession Profiles

ID: get_succession_profiles
Operation: read
Entities: succession profile, company
Summary: The Get Succession Profiles API returns a list of succession profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get System Account

ID: get_system_account
Operation: read
Entities: profile, account, company
Summary: The Get System Account API retrieves the core system account record containing detailed information about the account. It requires the 'REST API RESOURCES' security profile items in combination with 'manager permissions'. The API endpoint requires two path parameters: 'cid' (company id or unique id or short name) and 'aid' (account id or external id). The response includes detailed account information such as username, name, email, phone numbers, address, and profiles. The API returns various HTTP status codes including 200 (OK), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), and 503 (Service Unavailable).
Input Fields: Input Fields
Output Fields: Output Fields

Get System Accounts

ID: get_system_accounts
Operation: read
Entities: system account, user, company
Summary: The Get System Accounts API returns basic information about the system accounts a user has permissions to view. It requires a path parameter 'cid' which is the company identifier. The response includes an array of system accounts with details such as id, username, first name, and last name. The API considers only the 'REST API RESOURCES' security profile items. Possible responses include 200 OK, 404 Not Found, 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get System Forms for a Company

ID: get_system_forms_for_a_company
Operation: read
Entities: system, form, company
Summary: The 'Get System Forms for a Company' API endpoint retrieves a list of system forms associated with a specified company for a given period. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of forms, each with details such as form ID, name, type, creation date, creator information, and a download link. The API handles various response codes, including 200 for success, 400 for invalid requests, 403 for security violations, 404 for not found errors, 401 for unauthorized access, and 503 for service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Tax Codes

ID: get_tax_codes
Operation: read
Entities: tax code, response, company
Summary: The Get Tax Codes API endpoint is used to fetch a list of supported tax codes for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of tax codes, each with details such as id, code, name, abbreviation, and external id. The API returns a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Tax Information

ID: get_tax_information
Operation: read
Entities: employee, tax information, company
Summary: The Get Tax Information API retrieves the tax information of an employee for a specified company. It requires the company ID (cid) and account ID (aid) as path parameters. The API checks for access rights based on the security profile in the company settings. The response includes details such as employee tax type, pension box type, FEIN, DBA company name, and third-party sick pay reporting. The API returns various HTTP status codes to indicate success or specific errors, such as 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Tax Information for Employee

ID: get_taxes_for_employee
Operation: read
Entities: taxes
Summary: The Get Tax Information for Employee API retrieves the tax information of an employee for a specified company. It requires the company ID (cid) and account ID (aid) as path parameters. The API checks for access rights based on the security profile in the company settings. The response includes details such as employee tax type, pension box type, FEIN, DBA company name, and third-party sick pay reporting. The API returns various HTTP status codes to indicate success or specific errors, such as 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Termination Reason

ID: get_termination_reason
Operation: read
Entities: termination reason, company
Summary: The 'Get Termination Reason' API endpoint is used to fetch a list of termination reasons within a company. It requires a path parameter 'cid', which is the company identifier and must be provided in the request. The API returns a list of termination reasons, each with an id, display name, code, description, and a boolean indicating if the reason is rehireable. The response is a JSON object containing an array of termination reason objects. Possible response codes include 200 for a successful request, 401 if the user is unauthorized, 403 if access is forbidden, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Time Entries

ID: get_time_entries
Operation: read
Entities: time entry, employee, company
Summary: The 'Get Time Entries' API allows users to fetch existing time entries for a specified company within a given date range, with a maximum range of 31 days. The API requires a path parameter 'cid' which is the company identifier. The response includes detailed time entry data, even if some data is not displayed on the UI due to settings. The response schema includes information about employees, time entries, and various attributes such as start and end times, total time, approval status, and more. The API returns a 200 OK response on success, with other possible responses including 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Get Time Entry Notes

ID: get_time_entry_notes
Operation: read
Entities: time entry, note, company
Summary: The 'Get Time Entry Notes' API endpoint allows users to retrieve notes associated with specific time entries for a given company. The request requires a path parameter 'cid' which is the company identifier, and a query parameter 'time_entry_ids' which is a comma-separated list of time entry IDs. The response includes an array of time entry notes, each containing an 'id', 'text', and 'time_entry_id'. The API returns a 200 OK status on success, a 403 Forbidden status if the user lacks access, and a 503 Service Unavailable status if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Get Time Off Planning Profiles

ID: get_time_off_planning_profiles
Operation: read
Entities: time off planning profile, company
Summary: The 'Get Time Off Planning Profiles' API retrieves a list of Time Off Planning Profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API returns a 200 OK status on success, while 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable are possible error responses.
Input Fields: Input Fields
Output Fields: Output Fields

Get Timesheet Profiles

ID: get_timesheet_profiles
Operation: read
Entities: timesheet profile, company
Summary: The Get Timesheet Profiles API retrieves a list of timesheet profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of timesheet profiles, each with an 'id', 'display_name', and 'description'. The API returns a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Timesheets for a Given Employee

ID: get_timesheets
Operation: read
Entities: timesheets
Summary: The Get Timesheets API endpoint allows users to search for timesheets for a single employee. To access personal timesheets, the user must have the 'Access Personal Timesheets' permission. The API requires the company ID (cid) and account ID (aid) as path parameters. Additionally, one of the query parameters (date, current, previous, next) is mandatory to fulfill the request. The response includes a list of timesheets with details such as the timesheet ID, employee account ID, start and end dates, state, and editability. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Timesheets

ID: get_timesheets_for_given_employee
Operation: read
Entities: timesheet, employee, company
Summary: The Get Timesheets API endpoint allows users to search for timesheets for a single employee. To access personal timesheets, the user must have the 'Access Personal Timesheets' permission. The API requires the company ID (cid) and account ID (aid) as path parameters. Additionally, one of the query parameters (date, current, previous, next) is mandatory to fulfill the request. The response includes a list of timesheets with details such as the timesheet ID, employee account ID, start and end dates, state, and editability. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Timezones

ID: get_timezones
Operation: read
Entities: timezone, company
Summary: The Get Timezones API endpoint is used to fetch a list of defined timezones for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of timezones, each with details such as id, name, display name, java name, joda time zone, offset, and daylight saving time (dst) status. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get To-Do Items

ID: get_to_do_items
Operation: read
Entities: employee, to-do item, company
Summary: The 'Get To-Do Items' API endpoint returns a list of to-do items for a specific employee within a company. The to-do items are sorted by date in descending order. The API requires two path parameters: 'cid' (company identifier) and 'aid' (account identifier), both of which are required. The response includes an array of items, each with details such as 'id', 'type', 'created_at', 'linked_account', and 'props'. The API can return various HTTP status codes, including 200 (OK), 401 (Unauthorized), 403 (Forbidden), and 503 (Service Unavailable).
Input Fields: Input Fields
Output Fields: Output Fields

Get Total Compensation

ID: get_total_compensation
Operation: read
Entities: employee, compensation, company
Summary: The Get Total Compensation API retrieves the total compensation details for a specific employee identified by the account ID (aid) within a company identified by the company ID (cid). The compensation amount represents the total compensation per hour. The API requires two path parameters: 'cid' for the company and 'aid' for the employee account. The response includes an array of total compensations, each with details such as account ID, amount, currency, and the effective date. The API returns various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Training And Certifications

ID: get_training_and_certifications
Operation: read
Entities: training, certification, employee
Summary: The 'Get Training And Certifications' API retrieves the training and certifications information for a specific employee within a company. It requires the company ID (cid) and account ID (aid) as path parameters. The API checks for access rights based on the security profile in the company settings. The response includes an array of training courses with details such as course name, description, schedulability, completion date, expiration date, and expiration status. The API returns various HTTP status codes including 200 for success, 401 for unauthorized access, 403 for forbidden access, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Training Profiles

ID: get_training_profiles
Operation: read
Entities: profile, training profile, company
Summary: The Get Training Profiles API retrieves a list of training profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of training profiles, each with an 'id', 'display_name', and 'description'. The API returns a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable in case of errors.
Input Fields: Input Fields
Output Fields: Output Fields

Get Ts Auto Population Profiles

ID: get_ts_auto_population_profiles
Operation: read
Entities: profile, company
Summary: The 'Get Ts Auto Population Profiles' API returns a list of TS Auto Population Profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API can return various HTTP status codes, including 200 for success, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Unions

ID: get_unions
Operation: read
Entities: union, company
Summary: The Get Unions API allows retrieval of active unions associated with a specific company. The company is identified by the 'cid' path parameter, which is required and can be a company id, unique id, or short name. The API returns a list of unions in the response body, each with an id, name, and optional description. The response can include status codes such as 200 (Ok), 401 (Unauthorized), 403 (Forbidden), and 503 (Service Unavailable).
Input Fields: Input Fields
Output Fields: Output Fields

Get Vca Report Dialogs Settings

ID: get_vca_report_dialogs_settings
Operation: read
Entities: employee, dialog setting, company
Summary: The Get Vca Report Dialogs Settings API returns the employee VCA configuration for report dialog in notifications. This API requires the 'Report Dialogs In Notifications' functionality to be enabled in the company. It uses the GET method and requires two path parameters: 'cid' (company id or unique id or short name) and 'aid' (account id or external id). The response includes a JSON object with 'enabled' (boolean), 'text' (string), 'phone' (string), and 'email' (string) fields. Possible response codes include 200 (OK), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), and 503 (Service Unavailable).
Input Fields: Input Fields
Output Fields: Output Fields

Get Vehicle Assignment

ID: get_vehicle_assignment
Operation: read
Entities: employee, vehicle assignment, vehicle
Summary: The Get Vehicle Assignment API endpoint is used to fetch a specific vehicle assignment by its ID. It requires two path parameters: 'cid', which is the company identifier, and 'id', which is the vehicle assignment ID. The response includes detailed information about the vehicle assignment, such as the employee details, vehicle details, and various dates related to the assignment. The response also includes links for self, edit, delete, notes, add_note, documents, and add_document. The API returns different status codes such as 200 for success, 404 if the vehicle assignment is not found, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Vehicle Assignments

ID: get_vehicle_assignments
Operation: read
Entities: vehicle, assignment, company
Summary: The Get Vehicle Assignments API endpoint returns a list of all vehicle assignments for a specified company. The request requires a path parameter 'cid', which is the company ID or unique identifier. The response includes a list of vehicle assignments with details such as assignment ID, issue date, scheduled return date, status, and vehicle information. The response also includes links for self, edit, delete, notes, add_note, documents, and add_document. The API returns various HTTP status codes including 200 for success, 401 for unauthorized access, 403 for forbidden access, and 503 for service unavailable due to call limit exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Get Vehicles

ID: get_vehicles
Operation: read
Entities: vehicle, company
Summary: The Get Vehicles API endpoint is used to fetch a list of all vehicles within a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of vehicles with details such as vehicle ID, name, license state, license plate, and status. The status can be one of several values including 'IN_SERVICE', 'LOST', 'DAMAGED', etc. The response also includes a total count of vehicles. Possible response codes include 200 for success, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Get Vendors

ID: get_vendors
Operation: read
Entities: vendor, company
Summary: The Get Vendors API endpoint is used to fetch a list of active vendors for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of vendor items, each with an 'id' and 'name'. The API returns a 200 OK status on success, and may return 401 Unauthorized if the user is not authorized, 403 Forbidden if the user has no access to the resource, or 503 Service Unavailable if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Get Work Schedule Profiles

ID: get_work_schedule_profiles
Operation: read
Entities: profile, work schedule, company
Summary: The Get Work Schedule Profiles API returns a list of work schedule profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable errors under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Workday Breakdown Profiles

ID: get_workday_breakdown_profiles
Operation: read
Entities: workday breakdown profile, company
Summary: The 'Get Workday Breakdown Profiles' API retrieves a list of Workday Breakdown Profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API returns a 200 OK status on success, while 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable are possible error responses.
Input Fields: Input Fields
Output Fields: Output Fields

Get Worker Types

ID: get_worker_types
Operation: read
Entities: subsystem, worker type, company
Summary: The Get Worker Types API endpoint is used to fetch a list of worker types for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of worker types, each with an 'id', 'external_id', 'name', and 'type'. The 'type' can be one of several predefined values such as 'NONE', 'CONTINGENT_WORKER', 'CONTRACT_WORKER', 'EMPLOYEE', 'CONTRACTOR', or 'TEMPORARY_WORKER'. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Workers Comp Codes

ID: get_workers_comp_codes
Operation: read
Entities: worker comp code, company
Summary: The 'Get Workers Comp Codes' API endpoint is used to fetch a list of active workers compensation codes for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes a list of items, each containing details such as name, external_id, code, id, state, description, and country. The API returns a 200 OK response on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Get Working Time Regulation

ID: get_working_time_regulation
Operation: read
Entities: working time regulation profile, company
Summary: The 'Get Working Time Regulation' API returns a list of Working Time Regulation Profiles for a specified company. The request requires a path parameter 'cid', which is the company identifier. The response includes an array of profile objects, each containing an 'id', 'display_name', and 'description'. The API responds with a 200 OK status on success, and may return 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable under certain conditions.
Input Fields: Input Fields
Output Fields: Output Fields

Post Access Policy Profiles

ID: post_access_policy_profiles
Operation: write
Entities: access policy profile, company
Summary: The Post Access Policy Profiles API allows the creation of a new access policy profile for a specified company. The user must have permission to add access policies. The API requires the company ID as a path parameter and a JSON body containing the access profile details, including ID, name, description, active status, mobile access allowance, and a list of access options with their respective details. The API responds with a 201 status code upon successful creation, or appropriate error codes such as 400 for validation errors, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Account Groups

ID: post_account_groups
Operation: write
Entities: manager, account group, company
Summary: The Post Account Groups API allows the creation of a new regular account group for a specified company. The API requires the company ID as a path parameter. The request body must include the name of the account group, a description, a list of members with their account IDs, and a list of managers with their account IDs, active periods, and permissions. The API responds with a 201 Created status if successful, or error statuses such as 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable if there are issues with authorization, access, or call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Accrual Balances Update

ID: post_accrual_balances_update
Operation: write
Entities: accrual balance, employee, company
Summary: The Post Accrual Balances Update API allows updating employee accrual balances for a specified company. The API requires a path parameter 'cid' which is the company identifier. The request body must include an array of accrual balances with details such as company short name, employee username, time off type, as of date, updated to date, hours, and external accrued, taken, and carry over hours. The response indicates the success or failure of the operation with a status code such as 201 Created for success, or error codes like 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable for various failure scenarios.
Input Fields: Input Fields
Output Fields: Output Fields

Post Actions on Schedule

ID: post_actions_on_schedule
Operation: write
Entities: schedule, action, company
Summary: The Post Actions on Schedule API executes an action on a given schedule. It requires the Advanced Scheduler (SCHEDULE) Subsystem to be enabled in the company setup. The API takes path parameters including 'cid' (company identifier), 'schedule_id' (schedule identifier), and 'action_id' (action to perform, such as 'post' or 'unpost'). The response can be a 204 No Content if the action is performed successfully, or various error codes such as 403 Forbidden, 404 Not Found, 406 Not Acceptable, and 500 Internal Server Error depending on the situation.
Input Fields: Input Fields
Output Fields: Output Fields

Post Additional Compensation

ID: post_additional_compensation
Operation: write
Entities: employee, compensation, company
Summary: The Post Additional Compensation API creates an additional compensation record for an employee. It requires the company ID (cid) and account ID (aid) as path parameters. The request body must include details such as the compensation ID, account ID, type ID, currency, effective date, change date, period, active status, value, and a self-link. The API responds with a 201 Created status if successful, or error statuses such as 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable if there are issues with authorization, access, or call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post All Data Export

ID: post_all_data_export
Operation: write
Entities: user, data export, company
Summary: The 'Post All Data Export' API endpoint allows users to create a data export for a specified company. The request requires a path parameter 'cid' to identify the company. The request headers must include 'Accept' with a value of 'application/json'. The request body must include details such as 'name', 'format', 'type_id', 'data_records', and 'file_name_pattern'. The response will indicate success with a 201 status code if the data export is created successfully, or provide error codes such as 404 for company not found, 400 for request validation errors, and 500 for internal server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Post Applicants

ID: post_applicants
Operation: write
Entities: education, applicant, company
Summary: The Post Applicants API allows for the creation of a new applicant within a specified company. The API requires a path parameter 'cid' which is the company identifier. The request body includes detailed information about the applicant such as account details, address, phone numbers, demographics, salary requirements, education, skills, work experiences, professional references, job categories, and custom fields. The API responds with various status codes indicating the result of the operation, including 201 for successful creation, 401 for unauthorized access, 403 for forbidden access, and 503 for service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Asset Assignments

ID: post_asset_assignments
Operation: write
Entities: employee, asset assignment, company
Summary: The Post Asset Assignments API endpoint is used to create a new asset assignment for a company. It requires the company to be referenced via a company ID, unique ID, or short name. The request body must include details about whether the asset is personal, the asset type ID, and the employee's account ID. The API returns a 201 status code if the asset assignment is successfully created. If the user is unauthorized, a 401 status code is returned. A 403 status code is returned if the user has no access to the resource. If the call limit is exceeded, a 503 status code is returned, and the X-CallLimit-TimeToWait header specifies the duration to wait before making subsequent calls.
Input Fields: Input Fields
Output Fields: Output Fields

Post Batch Upload

ID: post_batch_upload
Operation: write
Entities: job setting, cost center, contact
Summary: The Post Batch Upload API allows the creation of new cost centers within an existing cost center tree. The parent node of a cost center can be specified using various fields of the parent_cc reference object, such as tree_index, id, and external_id. If only tree_index is specified, the new cost center will be created under the root node. If both id and external_id are specified, external_id will be ignored, and the search will be done with id. The API requires the TLM, HR, Scheduler subsystem to be enabled in the company setup, and the user must have Cost Center Definitions add permission. The API takes a path parameter 'cid' to identify the company and a request body containing the details of the cost centers to be created. The response includes the status of each item in the payload, with possible errors detailed in the response schema.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Closing

ID: post_cancel_closing
Operation: write
Entities: payroll, job, company
Summary: The 'Post Cancel Closing' API cancels the closing of specified payrolls for a company. It requires the company ID as a path parameter and a list of payroll IDs in the request body. The response includes job details and user messages indicating the status and any issues encountered during the process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Delete Sync Time

ID: post_cancel_delete_sync_time
Operation: write
Entities: payroll, job, company
Summary: The 'Post Cancel Delete Sync Time' API cancels the delete sync time action on specified payrolls for a given company. The API requires the company ID as a path parameter and a list of payroll IDs in the request body. The response includes job details and user messages indicating the status and any issues encountered during processing.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Finalize Payroll

ID: post_cancel_finalize_payroll
Operation: write
Entities: payroll, job, company
Summary: The Post Cancel Finalize Payroll API allows users to cancel the finalize action on specified payrolls for a given company. The request requires a path parameter 'cid' which is the company identifier. The request body must include an array of payroll IDs under the 'ids' key. The response includes a list of jobs with their statuses and any user messages indicating the result of the operation.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Initiate

ID: post_cancel_initiate
Operation: write
Entities: payroll, job, company
Summary: The Post Cancel Initiate API allows users to cancel the initiation of specified payrolls for a company. The API requires the company ID as a path parameter and a list of payroll IDs in the request body to specify which payrolls to cancel. The response includes job details with their status and any user messages indicating the result of the cancellation process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Recalculate

ID: post_cancel_recalculate
Operation: write
Entities: payroll, job, company
Summary: The Post Cancel Recalculate API cancels the recalculation of payrolls for a specified company. The API requires the company ID as a path parameter and a list of payroll IDs in the request body to identify which payroll recalculations to cancel. The response includes the status of the cancellation jobs and any user messages indicating the success or failure of the operation.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Reopen Payroll

ID: post_cancel_reopen_payroll
Operation: write
Entities: payroll, company
Summary: The Post Cancel Reopen Payroll API cancels the reopen action on specified payrolls for a given company. It requires the company ID as a path parameter and a list of payroll IDs in the request body. The response includes job details and user messages indicating the status and any issues encountered during processing.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Rollback Payroll

ID: post_cancel_rollback_payroll
Operation: write
Entities: payroll, job, company
Summary: The Post Cancel Rollback Payroll API cancels the rollback action on specified payrolls for a given company. The API requires the company ID as a path parameter and a list of payroll IDs in the request body. It returns a response containing job details and user messages indicating the status and any issues encountered during the process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cancel Sync Time

ID: post_cancel_sync_time
Operation: write
Entities: payroll, job, company
Summary: The Post Cancel Sync Time API allows users to cancel the sync time on specified payrolls for a given company. The request requires a path parameter 'cid' which is the company identifier, and a request body containing 'ids', an array of payroll IDs to cancel. The response includes a list of jobs with their statuses and any user messages indicating the result of the operation.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cases for Leave of Absence

ID: post_cases_for_leave_of_absence
Operation: write
Entities: leave of absence case, employee, company
Summary: This API endpoint is used to create a new leave of absence case for a company. The company must have leave of absence functionality enabled. The API requires a path parameter 'cid' to specify the company. The request body includes details about the employee, reason for leave, start and estimated end dates, case number, status, categories, leave time, entries, time off categories, and time off entries. The response will indicate whether the case was created successfully or if there were any authorization or access issues.
Input Fields: Input Fields
Output Fields: Output Fields

Post Clear Error Messages

ID: post_clear_error_messages
Operation: write
Entities: message, payroll, company
Summary: The 'Post Clear Error Messages' API is used to clear error messages for specified payrolls within a company. The API requires the company ID as a path parameter and a request body containing the list of payroll IDs, a boolean indicating whether to synchronize time action, and the status range from which to clear messages. Upon successful execution, it returns a message indicating that the clear messages action was successfully finished. If there is a validation error, a 400 Bad Request response is returned.
Input Fields: Input Fields
Output Fields: Output Fields

Post Close Payrolls

ID: post_close_payrolls
Operation: write
Entities: payroll, job, company
Summary: The Post Close Payrolls API performs the closing process on specified payrolls for a company. It requires the company ID as a path parameter and a list of payroll IDs in the request body. The response includes job details and user messages indicating the status and any issues encountered during the process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Collection

ID: post_collection
Operation: write
Entities: shift, schedule, company
Summary: The Post Collection API is used to perform a bulk operation to create multiple shifts within a specified schedule for a company. The API requires the Advanced Scheduler (SCHEDULE) Subsystem to be enabled in the company setup. It accepts path parameters 'cid' for the company identifier and 'schedule_id' for the schedule identifier. The request body includes details of the shifts to be created, such as shift ID, account information, date, type, start and end times, cost centers, skills, shift premiums, and average rates. The API returns a 200 Ok response if all shifts are successfully created, with other status codes indicating various errors such as insufficient permissions, schedule not found, unsupported media type, payload size too large, or internal server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Post Contacts

ID: post_contacts
Operation: write
Entities: contact, employee, company
Summary: The Post Contacts API endpoint is used to create employee contacts for a specified company. The endpoint requires a path parameter 'cid' to identify the company. The request body includes detailed information about the contact, such as personal details, phone numbers, email, national identification numbers, and other attributes. The API supports backward compatibility with fields like 'bsn', 'social_insurance', 'social_security', and 'national_insurance', but prefers the use of 'national_id_numbers'. The response indicates the success or failure of the contact creation, with status codes 201 for success, 401 for unauthorized access, 403 for forbidden access, and 503 for service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Contracts

ID: post_contracts
Operation: write
Entities: employee, contract, company
Summary: The Post Contracts API endpoint is used to create employee contracts for a specified company. The endpoint requires a path parameter 'cid' which is the company identifier. The request body must include an array of contract objects, each containing details such as employee account ID, working hours, working days, start and end dates, and other contract-specific information. The API validates the input, ensuring constraints like days per week not exceeding 7, and returns a response indicating the success or failure of each contract creation. The response includes an array of items, each with an index, status, and optionally an ID or error details.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cost Center Jobs

ID: post_cost_center_jobs
Operation: write
Entities: employee, cost center job, company
Summary: The Post Cost Center Jobs API endpoint allows users to create a new Cost Center Job within a specified company. The user must have the necessary permissions and at least one of the HR subsystems to use this endpoint. The API requires a path parameter 'cid' to identify the company. The request body must include detailed information about the job, such as job category, name, description, and various other attributes related to the job's classification, compensation, and skills. The API responds with a 201 status code if the job is created successfully, or with error codes 401, 403, or 503 in case of authorization issues or service unavailability.
Input Fields: Input Fields
Output Fields: Output Fields

Post Cost Center Lists

ID: post_cost_center_lists
Operation: write
Entities: cost center, list, company
Summary: The Post Cost Center Lists API endpoint allows the creation of a list that includes all cost centers in the list for a specified company. The request requires a path parameter 'cid' to specify the company, and a request body containing 'name', 'tree_index', and an array of 'cost_centers' with their respective 'id'. The response will indicate success with a 201 status code or provide error messages for unauthorized access (401), forbidden access (403), or service unavailability (503) due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Counter Adjustment Notes

ID: post_counter_adjustment_notes
Operation: write
Entities: counter adjustment note, counter adjustment, company
Summary: The 'Post Counter Adjustment Notes' API allows users to post notes related to counter adjustments for a specific company identified by the 'cid' path parameter. The request body must include an array of 'counter_adjustment_notes', each containing a 'counter_adjustment_id' and 'text'. The API responds with a list of notes indicating the status of each note posting, including an 'index', 'status', and 'note_id'. Possible response statuses include 200 OK, 201 Created, 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Post Counter Adjustments

ID: post_counter_adjustments
Operation: write
Entities: employee, counter adjustment, company
Summary: The Post Counter Adjustments API allows the creation of a counter adjustment for a specific employee within a company. It requires the company ID (cid) and account ID (aid) as path parameters. The request body must include the record date, counter ID, cost centers, value, reset flag, and reason code. The response returns the details of the created counter adjustment, including its ID, record date, counter details, cost centers, value, reset status, and reason code. Possible responses include 200 OK for success, 400 Bad Request for validation errors, 403 Forbidden for security issues, and 500 Internal Server Error for server issues.
Input Fields: Input Fields
Output Fields: Output Fields

Post Create Intuit W2 File

ID: post_create_intuit_w2_file
Operation: write
Entities: tax filing, file, company
Summary: The 'Post Create Intuit W2 File' API is used to create a file of W2 information to send to Intuit. It requires the PR subsystem. The API endpoint is 'https://HOSTNAME/ta/rest/v2/companies/{cid}/taxes/years/{year}/actions/create-intuit-file' and it uses the POST method. The path parameters include 'cid', which is a required string representing the company ID or unique identifier, and 'year', which is a required integer representing the four-digit year. Upon successful request, the API returns a '202 Accepted' response indicating that the action was accepted and a job was started.
Input Fields: Input Fields
Output Fields: Output Fields

Post Delete Multiple Documents

ID: post_delete_multiple_documents
Operation: write
Entities: document, module, company
Summary: The 'Post Delete Multiple Documents' API endpoint allows for the deletion of one or more documents associated with a company. The endpoint requires a list of document IDs to be provided in the request body. The company is identified by a path parameter 'cid', which can be the company ID, unique ID, or short name. The API is intended for companies with the 'Integrated Document Storage' marketplace product. If documents are linked to a module, the user must have access to that module to delete the documents. The response includes the status of each document deletion attempt, with possible statuses being 'OK' or 'FAILURE'. The response also includes user messages indicating the success or failure of each deletion attempt. The API returns various HTTP status codes, including 200 for success, 400 for bad requests, 404 if the resource is not found, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Delete Sync Time

ID: post_delete_sync_time
Operation: write
Entities: time, payroll, company
Summary: The 'Post Delete Sync Time' API is used to delete sync time on specified payrolls for a company. The API requires a path parameter 'cid' which is the company identifier. The request body should include 'payroll_ids' and 'pay_period_ids', both arrays of numbers. The response includes a list of jobs with their statuses and user messages indicating the result of the operation.
Input Fields: Input Fields
Output Fields: Output Fields

Post Deliver

ID: post_deliver
Operation: write
Entities: payroll, job, company
Summary: The Post Deliver API performs the delivery process on specified payrolls if they are closed. It requires a path parameter 'cid' which is the company identifier and a request body containing 'ids', an array of payroll IDs to be delivered. The response includes a list of jobs with their statuses and user messages indicating the processing actions for each payroll.
Input Fields: Input Fields
Output Fields: Output Fields

Post Direct Deposits

ID: post_direct_deposits
Operation: write
Entities: calculation method, direct deposit account, company
Summary: This API endpoint is used to create a new direct deposit account for a company. The endpoint is deprecated as of April 13, 2023, but will continue to function according to the deprecation policy. The request requires a path parameter 'cid' to specify the company. The request body must include details such as the account name, description, type, active dates, employee account ID, and bank account details. Depending on the calculation method, either 'amount' or 'percentage' may be required. The response will indicate success with a 201 Created status or provide error statuses such as 401 Unauthorized, 403 Forbidden, or 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Post Document Storage

ID: post_document_storage
Operation: write
Entities: document, metadata, company
Summary: The Post Document Storage API is used to create metadata for a document as part of a two-phase document upload process. This endpoint handles the metadata creation phase, providing a link to the document resource upon success. It is available for companies with the 'Integrated Document Storage' marketplace product. The API requires a company ID as a path parameter and accepts a JSON body with details about the document, including type, file name, display name, document type, description, and optional attributes. The response indicates the success or failure of the metadata creation, with appropriate HTTP status codes.
Input Fields: Input Fields
Output Fields: Output Fields

Post Employees

ID: post_employees
Operation: write
Entities: manager, employee, company
Summary: The Post Employees API allows the creation of a new employee record. It requires a company ID as a path parameter and accepts a detailed JSON body containing employee information such as name, address, phone numbers, and other personal details. The API does not consider certain fields like 'Id', 'Status', 'Terminated', and 'Links' in the request body. It performs validation only on system fields like 'Firstname'. The response includes various status codes indicating the result of the operation, such as 201 for successful creation, 400 for validation errors, and 403 for security issues.
Input Fields: Input Fields
Output Fields: Output Fields

Post Execute Accrual Balances

ID: post_execute_accrual_balances
Operation: write
Entities: payroll, pay period, company
Summary: The Post Execute Accrual Balances API performs the execute accrual balances process on specified payrolls, payroll, or pay period. It requires a path parameter 'cid' to specify the company and a request body containing 'ids', which is a list of payroll IDs to execute accrual balances on. The response includes a 'task_id' indicating the task created for the execution and 'user_messages' providing information about the process with severity levels.
Input Fields: Input Fields
Output Fields: Output Fields

Post Execute Accruals

ID: post_execute_accruals
Operation: write
Entities: payroll, accrual, company
Summary: The Post Execute Accruals API performs the execute accruals process on specified payrolls for a given company. The request requires a path parameter 'cid' which is the company identifier and a request body containing 'ids', an array of payroll IDs to execute accruals on. Upon successful execution, the API returns a message indicating the successful creation of the execute accruals job.
Input Fields: Input Fields
Output Fields: Output Fields

Post Export Payroll

ID: post_export_payroll
Operation: write
Entities: payroll, pay period, company
Summary: The Post Export Payroll API allows the caller to trigger the generation of the payroll interface file. This process is asynchronous, and a successful call returns a job ID that can be used to retrieve the status. The API requires path parameters 'cid' (company ID) and 'pay_period_id' (pay period ID). The request body can include details of the snapshot to export, export format ID, type of records to export, a flag indicating if only payroll employees should be exported, and user prompts. The response includes a job ID if the export job is successfully created.
Input Fields: Input Fields
Output Fields: Output Fields

Post External Pay Statements

ID: post_external_pay_statements
Operation: write
Entities: document metadata, pay statement, company
Summary: The Post External Pay Statements API allows users to upload their pay statements. This is a two-phase process where users first create the pay statement and document metadata, and then get a link to upload the pay statement content. The API is available for companies with the 'Import External Pay History' functionality enabled. The request requires a path parameter 'cid' to specify the company, and a request body containing details such as employee account ID, file name, pay date, total gross pay, and other pay-related information. The API responds with various status codes indicating the result of the operation, such as 201 for successful creation, 400 for bad requests, 401 for unauthorized access, 403 for forbidden access, and 503 for service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Finalize And Deliver

ID: post_finalize_and_deliver
Operation: write
Entities: payroll, job, company
Summary: The Post Finalize And Deliver API performs the finalize and delivery process on specified payrolls if they are closed. It requires a path parameter 'cid' which is the company identifier. The request body must include an array of payroll IDs under 'ids'. The response includes a list of jobs with their statuses and user messages indicating the result of the operation, including any errors or warnings.
Input Fields: Input Fields
Output Fields: Output Fields

Post Finalize Payrolls

ID: post_finalize_payrolls
Operation: write
Entities: payroll, job, company
Summary: The Post Finalize Payrolls API performs the finalize process on specified payrolls if they are closed. It requires a path parameter 'cid' which is the company identifier. The request body must include an array of payroll IDs to finalize. The response includes job details and user messages indicating the status and any issues encountered during the process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Forward Mailbox Items

ID: post_forward_mailbox_items
Operation: write
Entities: mailbox item, notification, company
Summary: The Post Forward Mailbox Items API endpoint forwards specified mailbox items for a given company. The request requires a path parameter 'cid' which is the company identifier. The request body must include an array of 'ids' representing the mailbox item IDs to be forwarded. The response returns a list of processing results for each item, indicating success ('OK') or failure ('FAILURE') with error details if applicable. Possible response codes include 200 (OK), 403 (Forbidden), and 503 (Service Unavailable).
Input Fields: Input Fields
Output Fields: Output Fields

Post Hcm Application Details Widget

ID: post_hcm_application_details_widget
Operation: write
Entities: widget, hcm application detail, company
Summary: The Post Hcm Application Details Widget API enables the HCM Application Details Widget for a specified company. It requires the company ID as a path parameter. The request body must include the HCM application details configuration, such as enabling decimal rounding, allowing special characters, and other settings. The API responds with a status indicating the success or failure of the operation, including messages for successful configuration, unauthorized access, or service unavailability.
Input Fields: Input Fields
Output Fields: Output Fields

Post Hcm System Details Widget

ID: post_hcm_system_details_widget
Operation: write
Entities: configuration, system, widget
Summary: The Post Hcm System Details Widget API enables the Dimensions HCM System Details Widget for a specified company. It requires a company ID as a path parameter and a system configuration object in the request body, which includes server URL, API key, tenant ID, username, password, client ID, client secret, and a flag for Dimensions HCM mode. The API returns a response indicating the success or failure of the operation, with possible HTTP status codes including 200 (OK), 201 (Created), 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), and 503 (Service Unavailable).
Input Fields: Input Fields
Output Fields: Output Fields

Post History

ID: post_history
Operation: write
Entities: employee, compensation, company
Summary: The Post History API endpoint is used to create Employee Base Compensation for a specified company. The request requires a path parameter 'cid' which is the company identifier. The request body includes details such as employee account ID, effective date, compensation amount, currency, amount period, time, time period, number of pay periods in a year, and auto pay details. The response indicates the success or failure of the request with status codes such as 201 for successful creation, 401 for unauthorized access, 403 for forbidden access, and 503 for service unavailability due to exceeded call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Initiate Payrolls

ID: post_initiate_payrolls
Operation: write
Entities: payroll, job, company
Summary: The Post Initiate Payrolls API is used to initiate one or more payrolls for a specified company. The request requires a path parameter 'cid' which is the company identifier. The request body includes parameters such as 'ids' for payroll identifiers, 'pay_statement_types' for specifying types of pay statements, 'process' to define the payroll process, 'block_base_comp' as a boolean to block base compensation, 'reconcile' for reconciliation type, and 'pay_stub_note' for any notes. The response returns a list of jobs with their statuses and user messages indicating the processing status.
Input Fields: Input Fields
Output Fields: Output Fields

Post Inventory Items

ID: post_inventory_items
Operation: write
Entities: inventory profile, employee, inventory item
Summary: The Post Inventory Items API endpoint is used to create a new employee inventory item. It requires the company ID and inventory profile ID as path parameters. The request body must include the employee's account ID. The API responds with a 201 status code if the item is successfully created. If the user is unauthorized, a 401 status code is returned. A 403 status code is returned if the user lacks access to the resource. If the call limit is exceeded, a 503 status code is returned, indicating the service is unavailable for a specified duration.
Input Fields: Input Fields
Output Fields: Output Fields

Post Job Applications

ID: post_job_applications
Operation: write
Entities: job application, job requisition, company
Summary: The Post Job Applications API endpoint allows for the creation of a new job application for a specified company. The request requires a path parameter 'cid' which is the company identifier. The request body must include details such as account ID, applicant comment, application date, company comment, hiring stage ID, job application status ID, job requisition ID, and rank. The API responds with a 201 status code if the job application is successfully created. It may also return 401 if the user is unauthorized, 403 if access is forbidden, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Submit Leave of Absence Request

ID: post_leave_of_absence_request
Operation: write
Entities: leave of absence, employee, company
Summary: This API endpoint allows the submission of a new leave of absence request for a specified company. The request requires a path parameter 'cid' to identify the company. The request body must include details about the employee, reason for leave, start and estimated end dates, leave time specifics, any custom fields, and an optional comment. The API responds with a 201 status code if the request is successfully created, or with error codes 401, 403, or 503 for unauthorized access, forbidden access, or service unavailability, respectively.
Input Fields: Input Fields
Output Fields: Output Fields

Post Lock Pay Period

ID: post_lock_pay_period
Operation: write
Entities: account, pay period, company
Summary: The Post Lock Pay Period API allows the caller to lock a specific pay period for a company. The endpoint requires two path parameters: 'cid', which is the company identifier, and 'pay_period_id', which is the identifier for the pay period to be locked. Upon successful execution, the API returns a 200 OK status indicating that the pay period and all associated employee accounts are locked. If there are validation errors, a 400 Bad Request is returned. Security errors result in a 403 Forbidden response, and if the service is unavailable, a 503 Service Unavailable is returned.
Input Fields: Input Fields
Output Fields: Output Fields

Post Login

ID: post_login
Operation: write
Entities: token, login, authentication
Summary: The Post Login API is used to authenticate users and obtain a bearer token for accessing protected resources. The request requires an 'Api-Key' header, which is unique to each company, and a JSON body containing the user's 'username', 'password', and 'company' short name. A successful login returns a token with a 200 status code, valid for 1 hour. If the user must change their password, a temporary token is issued with a 403 status code, valid for 5 minutes, and can only be used with the /employee/password endpoint.
Input Fields: Input Fields
Output Fields: Output Fields

Post Mailbox Items

ID: post_mailbox_items
Operation: write
Entities: employee, notification, company
Summary: The Post Mailbox Items API endpoint allows the creation of a new mailbox item for a specified employee within a company. It requires the company ID (cid) and account ID (aid) as path parameters. The request body must include the subject and body of the mailbox item, as well as any associated documents. Upon successful creation, a 201 status code is returned. If the user is unauthorized, a 401 status code is returned. A 403 status code is returned if the user lacks access to the resource, and a 503 status code is returned if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Post Managed Cost Centers

ID: post_managed_cost_centers
Operation: write
Entities: managed cost center, employee, company
Summary: The 'Post Managed Cost Centers' API endpoint allows users to create a managed cost center for a specified company and employee. The user must have the appropriate permissions to add a managed cost center. The API requires two path parameters: 'cid' for the company ID and 'aid' for the account ID. The request body includes details about the cost center and the permissions associated with it. The response indicates the status of the request, such as '201 Created' for a successful creation, '401 Unauthorized' if the user is not authorized, '403 Forbidden' if the user lacks access, and '503 Service Unavailable' if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Post Managers

ID: post_managers
Operation: write
Entities: manager, account group, company
Summary: The Post Managers API allows the creation of a new regular account group manager. It requires the company ID (cid) and account group ID (gid) as path parameters. The request body includes details about the employee, such as account ID, username, active period, and permissions related to employee information, time, and pay statements. The API responds with a 201 Created status if successful, or error statuses like 401 Unauthorized, 403 Forbidden, and 503 Service Unavailable for various failure scenarios.
Input Fields: Input Fields
Output Fields: Output Fields

Post Members

ID: post_members
Operation: write
Entities: account group, member, company
Summary: The Post Members API allows the creation of a new regular account group member. It requires the company ID (cid) and account group ID (gid) as path parameters. The request body must include the account ID and username of the member to be added. The API returns a 201 Created response on success. If the user is unauthorized, a 401 Unauthorized response is returned. A 403 Forbidden response is returned if the user lacks access to the resource. If the call limit is exceeded, a 503 Service Unavailable response is returned, and the application will be unavailable for subsequent calls for the duration specified by the X-CallLimit-TimeToWait header.
Input Fields: Input Fields
Output Fields: Output Fields

Post Notes

ID: post_notes
Operation: write
Entities: note, company
Summary: The Post Notes API endpoint allows for the creation of notes associated with a specific company. The request requires a company identifier (cid) as a path parameter and a token as a query parameter to resolve user permissions. The request body must include the text of the note to be created. Successful creation of a note returns a 201 status code. If the user is unauthorized or lacks access, 401 and 403 status codes are returned, respectively. A 503 status code is returned if the call limit is exceeded, with the X-CallLimit-TimeToWait header indicating the wait time before subsequent calls.
Input Fields: Input Fields
Output Fields: Output Fields

Post Notes for Leave of Absence Case

ID: post_notes_for_leave_of_absence_case
Operation: write
Entities: leave of absence, note, case
Summary: This API endpoint is used to create notes for a leave of absence case. It requires the company ID (cid) and the case ID (id) as path parameters. The request body must include the text of the note to be created. Upon successful creation, a 201 status code is returned. If the user is unauthorized, a 401 status code is returned. If the user lacks access to the resource, a 403 status code is returned. If the call limit is exceeded, a 503 status code is returned, and the X-CallLimit-TimeToWait header specifies the duration to wait before making subsequent calls.
Input Fields: Input Fields
Output Fields: Output Fields

Post Oauth Applications

ID: post_oauth_applications
Operation: write
Entities: oauth application, company
Summary: The Post Oauth Applications API allows the creation of a new OAuth application for a specified company. The API requires a path parameter 'cid' to identify the company. The request body must include the 'name' and 'application_type' of the application. Depending on the 'application_type', additional fields may be required: 'secret', 'security_profile', and 'account_group_ids' for 'Machine to Machine' type, and 'redirect_url_whitelist' for 'Interactive' type. The response indicates the success or failure of the operation, with various HTTP status codes representing different outcomes.
Input Fields: Input Fields
Output Fields: Output Fields

Post Order Status

ID: post_order_status
Operation: write
Entities: background screening, order status, company
Summary: The Post Order Status API endpoint is used to receive background screening order statuses. It requires a company ID as a path parameter and a request body containing details such as request ID, vendor order identifier, order status details, and optional notes. The order status details include the current status, result, completion date, and status of individual products in the order. The API responds with various HTTP status codes indicating the success or failure of the request, including 200 for success, 400 for bad request, 401 for unauthorized access, 403 for forbidden access, 500 for internal server errors, and 503 for service unavailability.
Input Fields: Input Fields
Output Fields: Output Fields

Post Overtime Requests

ID: post_overtime_requests
Operation: write
Entities: overtime request, employee, company
Summary: The Post Overtime Requests API allows users to create overtime requests for themselves or on behalf of employees. The user must have the appropriate permissions to request or approve overtime. The API requires the 'TLM' subsystem. The request includes a path parameter 'cid' for the company ID, and a body with details such as employee account ID, agreement status, reason ID, type of overtime, start and end times, and an optional comment. The response indicates success with a 201 status or provides error messages for unauthorized access, forbidden actions, or service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Pay Statement Mass Delete

ID: post_pay_statement_mass_delete
Operation: write
Entities: payroll, pay statement, company
Summary: The Post Pay Statement Mass Delete API allows for the deletion of multiple pay statements using either a key_set_ref or a list of pay statement ids. The API requires the company id (cid) and payroll id (id) as path parameters. The request body can include an array of pay statement ids and/or a key_set_ref for deletion. The API responds with a 200 status code if the deletion is successful, a 404 status code if the company, payroll, or pay statement ids are not found, and a 500 status code if an individual pay statement is not found or access is forbidden.
Input Fields: Input Fields
Output Fields: Output Fields

Post Pay Statements

ID: post_pay_statements
Operation: write
Entities: pay statement, payroll, employee
Summary: The Post Pay Statements API endpoint allows for the creation of new pay statements for a given employee within a specified payroll. It supports various pre-defined pay statement types such as Regular, 3rd Party Sick, Bonus, Void, and Historical. The API requires path parameters including the company ID (cid) and payroll ID (id). The request body includes details about the employee, pay statement type, earnings, and deductions. The response indicates the success or failure of the operation, with possible status codes including 201 Created, 400 Bad Request, 403 Forbidden, and 500 Internal Server Error.
Input Fields: Input Fields
Output Fields: Output Fields

Post Payrolls

ID: post_payrolls
Operation: write
Entities: type, payroll, company
Summary: The Post Payrolls API endpoint is used to create a new payroll that has not been scheduled. It supports various payroll types such as Historical, Regular, and Void, depending on the company settings. The API requires a path parameter 'cid' to specify the company, and a request body containing the payroll name, pay date, and type. The response indicates whether the payroll was successfully saved or if there were any errors during the process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Process Records

ID: post_process_records
Operation: write
Entities: record, pay period, company
Summary: The Post Process Records API allows the caller to execute the 'Process Records' business step in the Pay Prep process asynchronously. It requires the company ID (cid) and pay period ID (pay_period_id) as path parameters. The request body must include the 'process_type', such as 'ALL_ACTUAL'. Upon successful initiation, it returns a job ID that can be used to query the status of the process. The API responds with a 202 Accepted status if the job is started, 400 Bad Request for validation errors, 403 Forbidden for security errors, and 503 Service Unavailable if the service is down.
Input Fields: Input Fields
Output Fields: Output Fields

Post Project Management

ID: post_project_management
Operation: write
Entities: project, cost center, company
Summary: The Post Project Management API endpoint is used to create a new project within a specified company. The company is identified by the 'cid' path parameter, which is required. The request body must include details about the project such as its name, business purpose, percentage of completion, description, start and end dates, cost center list ID, budget amount, status, associated employees and managers, and EIN details. The API responds with a 201 status code if the project is created successfully. Other possible responses include 404 if the resource does not exist, 401 if the user is not authorized, 403 if the functionality is not enabled, and 503 if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Post PTO Request

ID: post_pto_request
Operation: write
Entities: manager, employee, time off request
Summary: The Post PTO Request API allows for creating a new time off request for an employee. This can be done by the employee themselves or by a manager on behalf of the employee. The API requires a valid time off type, which can be FullDay, Partial, PartialBlk, Multiple, or Dynamic. Depending on the type, different fields are required, such as from_date, from_time, to_time, total_time, and dynamic_duration. The request body must include the employee's username, the time off name, and the type of request. The API returns a success code on successful processing, and may also return various message types such as info, confirm, critical, error, or warning. The response includes a success flag, the requested time, and a list of results with message details.
Input Fields: Input Fields
Output Fields: Output Fields

Post Rate Schedules

ID: post_rate_schedules
Operation: write
Entities: rate schedule, rate table, company
Summary: The Post Rate Schedules API allows the creation of a rate schedule for a specified company and rate table. It requires the company ID (cid) and rate table ID (tid) as path parameters. The request body includes details such as line number, type, description, rate items, rate reason code, usage, time entry record, and counter record. Upon successful creation, the API returns a 201 Created response.
Input Fields: Input Fields
Output Fields: Output Fields

Post Rate Tables

ID: post_rate_tables
Operation: write
Entities: cost center, rate table, company
Summary: The Post Rate Tables API allows users to create a new rate table for a specified company. The API requires the company ID as a path parameter. The request body must include details such as the name, description, currency, and external table ID. It also supports specifying alternative tables with operations. The API responds with a 201 status code if the rate table is successfully created. If the user is unauthorized, a 401 status code is returned. A 403 status code indicates no access to the resource, and a 503 status code is returned if the call limit is exceeded, with the X-CallLimit-TimeToWait header indicating the wait time for subsequent calls.
Input Fields: Input Fields
Output Fields: Output Fields

Post Read Mailbox Items

ID: post_read_mailbox_items
Operation: write
Entities: mailbox item, notification, company
Summary: The Post Read Mailbox Items API marks specified mailbox items as read for a given company. The request requires a path parameter 'cid' which is the company identifier. The request body must include an array of 'ids' representing the mailbox item IDs to be marked as read. The response returns a list of items with their processing status. A status of 'OK' indicates successful processing, while 'FAILURE' indicates an error, with details provided in the 'errors' array. Possible response codes include 200 for success, 403 for forbidden access, and 503 if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Post Ready Learning

ID: post_ready_learning
Operation: write
Entities: learning item, assignment, company
Summary: The 'Post Ready Learning' API allows for the creation and updating of ready learning item assignments for a specified company. The API requires a path parameter 'cid' which is the company identifier. The request body can include the company's short name, academy ID, and a list of learning statuses, each containing details such as account ID, item ID, enrollment date, status, name, description, last updated date, item URL, image URL, due date, completion date, and item type. The API responds with various status codes indicating the result of the operation, such as 200 for success, 404 for incorrect endpoint, 401 for unauthorized access, 403 for forbidden access, 201 for creation, and 503 for service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Recalculate

ID: post_recalculate
Operation: write
Entities: payroll, company
Summary: The 'Post Recalculate' API recalculates pay statements on the specified payrolls for a given company. It requires the company ID as a path parameter and a list of payroll IDs in the request body. The response includes job details such as job ID, status, and processing statistics, along with user messages indicating the success or failure of the recalculation process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Recalculate Company Taxes

ID: post_recalculate_company_taxes
Operation: write
Entities: job, tax, company
Summary: The 'Post Recalculate Company Taxes' API recalculates the W2, 1099, and pay statement information for a specified tax year for a company. It requires the 'PR' subsystem. The API is accessed via a POST request to the endpoint with the company ID and tax year as path parameters. Upon successful initiation, it returns a 202 Accepted response, indicating that a job has been started. The 'Location' header in the response provides a URL to check the status of the job.
Input Fields: Input Fields
Output Fields: Output Fields

Post Reopen Payrolls

ID: post_reopen_payrolls
Operation: write
Entities: payroll, job, company
Summary: The Post Reopen Payrolls API performs the reopening process on specified payrolls for a company identified by the 'cid' path parameter. The request body must include a list of payroll IDs to be reopened, and optional flags to open pay statements and clear auto check numbers. The response includes job details and user messages indicating the status and any issues encountered during the process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Rollback

ID: post_rollback
Operation: write
Entities: payroll, job, company
Summary: The Post Rollback API performs the rollback process on specified payrolls if they are finalized. It requires the company ID as a path parameter and a list of payroll IDs in the request body. The response includes job details and user messages indicating the status and any issues encountered during the rollback process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Scheduled Deduction Mass Add, Edit, Or Delete

ID: post_scheduled_deduction_mass_add_edit_or_delete
Operation: write
Entities: scheduled deduction, vendor, company
Summary: The 'Post Scheduled Deduction Mass Add, Edit, Or Delete' API endpoint allows users to create one or more scheduled deductions for a specified company. The API requires the company ID as a path parameter. The request body must include an array of scheduled deductions, each with detailed information such as account ID, deduction ID, sequence, vendor details, memo, active dates, annual maximums, and various calculation methods. The response will indicate the success or failure of the operation, with a 201 status code indicating successful creation. Other possible responses include 401 Unauthorized, 400 Bad Request, 403 Forbidden, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Post Scheduled Earning Mass Add, Edit, Or Delete

ID: post_scheduled_earning_mass_add_edit_or_delete
Operation: write
Entities: employee, scheduled earning, company
Summary: The 'Post Scheduled Earning Mass Add, Edit, Or Delete' API endpoint allows users to create one or more scheduled earnings for a specified company. The API requires the company ID as a path parameter. The request body must include details of the scheduled earnings, such as employee account ID, earning ID, active dates, amounts, frequency, and cost centers. The API responds with a status indicating the success or failure of the operation, including specific error messages for bad requests, unauthorized access, insufficient rights, or service unavailability.
Input Fields: Input Fields
Output Fields: Output Fields

Post Scheduler

ID: post_scheduler
Operation: write
Entities: scheduler, company
Summary: The Post Scheduler API creates a new schedule for a company. The Advanced Scheduler (SCHEDULE) subsystem must be enabled in the company setup. The API requires a path parameter 'cid' to specify the company, and a request body containing 'settings_id', 'schedule_start', 'time_zone_id', and 'template'. The response includes status codes 201 for successful creation, 401 for unauthorized access, 403 for forbidden access, and 503 if the service is unavailable due to exceeded call limits. The 'X-CallLimit-TimeToWait' header indicates the wait time before subsequent calls if the limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Post Service Accounts

ID: post_service_accounts
Operation: write
Entities: service account, security profile, company
Summary: The Post Service Accounts API allows for the creation of a new service account within a specified company. The API requires a path parameter 'cid' to identify the company. The request body must include details such as 'username', 'password', 'external_id', 'locked' status, 'security_profile', 'service_type', 'login_as_account', 'login_as_sa', 'company_group_ids', 'allow_edit', and 'account_group_ids'. The API responds with various status codes indicating the result of the operation, including 201 for successful creation, 400 for validation errors, 500 for server errors, 401 for unauthorized access, 403 for forbidden access, and 503 for service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Snapshot

ID: post_snapshot
Operation: write
Entities: snapshot, pay period, company
Summary: The Post Snapshot API allows the caller to create a snapshot for a specified pay period. It requires two path parameters: 'cid', which is the company identifier and can be a company id, unique id, or short name, and 'pay_period_id', which is the identifier for the pay period. The API responds with a 201 status code if the snapshot is successfully created. If there are validation errors, it returns a 400 status code. A 403 status code is returned in case of security errors, and a 503 status code is returned if the service is unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Post Submit Payrolls

ID: post_submit_payrolls
Operation: write
Entities: payroll, job, company
Summary: The Post Submit Payrolls API performs the submit process on specified payrolls if they are closed. It requires a path parameter 'cid' to identify the company and a request body containing 'ids', which is a list of payroll IDs to be submitted. The response includes a list of jobs with their statuses and user messages indicating the success or failure of the submission process.
Input Fields: Input Fields
Output Fields: Output Fields

Post Sync Time

ID: post_sync_time
Operation: write
Entities: payroll, job, company
Summary: The Post Sync Time API is used to sync time on specified payrolls for a company. The API requires a path parameter 'cid' which is the company identifier. The request body should include 'payroll_ids' and 'pay_period_ids', both of which are arrays of numbers. The response includes a list of jobs with their statuses and user messages indicating the result of the sync operation.
Input Fields: Input Fields
Output Fields: Output Fields

Post System Accounts

ID: post_system_accounts
Operation: write
Entities: profile, system account, company
Summary: The Post System Accounts API allows the creation of a new system account record. It requires a company identifier as a path parameter. The request body can include various fields such as username, first name, last name, email addresses, phone numbers, and profiles. The API responds with different status codes indicating the result of the operation, such as 201 for successful creation, 400 for validation errors, and 403 for security issues.
Input Fields: Input Fields
Output Fields: Output Fields

Post Time Entry Notes

ID: post_time_entry_notes
Operation: write
Entities: time entry, note, company
Summary: The 'Post Time Entry Notes' API allows users to post notes for time entries for a specified company. The API requires a path parameter 'cid' which is the company identifier. The request body must include an array of 'time_entry_notes', each containing a 'time_entry_id' and 'text'. The response returns a list of items indicating the status of each note processed, with possible statuses being 'OK' or 'FAILURE'. In case of failure, error details are provided. The API responds with various HTTP status codes such as 200 for success, 403 for forbidden access, 503 for service unavailable, 401 for unauthorized access, and 413 if the request entity is too large.
Input Fields: Input Fields
Output Fields: Output Fields

Post Time Punches

ID: post_time_punches
Operation: write
Entities: cost center, time punch, company
Summary: The Post Time Punches API allows for the import of time punches for employees within a specified company. The API requires a path parameter 'cid' which is the company identifier. The request body must include an array of 'punches', each containing details such as 'employee' account ID, 'raw_type' of punch, 'timestamp', 'ip', and optional fields like 'latitude', 'longitude', 'cost_centers', 'terminal_id', and 'device_id'. The response will indicate the success or failure of each punch with an 'items' array, where each item contains an 'index', 'id', 'status', and any 'errors' if applicable. The API handles various response codes including 200 for success, 401 for unauthorized access, 403 for forbidden access, 413 for payload too large, and 503 for service unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Token

ID: post_token
Operation: write
Entities: authorization, token, company
Summary: The Post Token API implements the OAuth 2.0 Authorization Framework Authorization Endpoint as per RFC 6749 section-4.4. It is used to obtain an access token for a company identified by the 'cid' path parameter. The request must include the 'Content-Type' header set to 'application/x-www-form-urlencoded'. The response includes an 'access_token', 'token_type', 'expires_in', and optionally a 'refresh_token'. The API returns various HTTP status codes to indicate success or specific errors, such as 200 for success, 400 for bad request, 401 for unauthorized access, 404 for not found, 405 for method not allowed, 406 for not acceptable, and 415 for unsupported media type.
Input Fields: Input Fields
Output Fields: Output Fields

Post Unread

ID: post_unread
Operation: write
Entities: mailbox item, notification, company
Summary: The 'Post Unread' API endpoint is used to mark mailbox items as unread for a specified company. The request requires a path parameter 'cid' which is the company identifier. The request body must include an array of 'ids', which are the mailbox item IDs to be marked as unread. The response will return a list of items with their processing status. A status of 'OK' indicates successful processing, while 'FAILURE' indicates an error, with details provided in the 'errors' array. Possible response codes include 200 for success, 403 for forbidden access, and 503 if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Post Vehicle Assignments

ID: post_vehicle_assignments
Operation: write
Entities: vehicle, assignment, company
Summary: The Post Vehicle Assignments API endpoint allows the creation of a new vehicle assignment for a company. The request requires a path parameter 'cid' to specify the company, and a request body containing 'employee' with 'account_id', 'vehicle' with 'id', and 'is_personal' to indicate if the vehicle is personal. The API responds with a 201 status code if the assignment is successfully created, or error codes 401, 403, or 503 for unauthorized access, forbidden access, or service unavailability respectively.
Input Fields: Input Fields
Output Fields: Output Fields

Post Vehicle Insurances

ID: post_vehicle_insurances
Operation: write
Entities: vehicle, vehicle insurance, company
Summary: The Post Vehicle Insurances API endpoint allows the creation of a new vehicle insurance for a specified company. The request requires a path parameter 'cid' to identify the company. The request body must include 'effective_from' and 'effective_to' dates, 'insurance_carrier' name, 'policy_num', and vehicle details including 'id' and 'display_name'. The API responds with a 201 status code if the insurance is successfully created. It may also return 401 if the user is unauthorized, 403 if access is forbidden, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Post Vehicle Maintenances

ID: post_vehicle_maintenances
Operation: write
Entities: maintenance, vehicle, company
Summary: The Post Vehicle Maintenances API endpoint allows for the creation of a new vehicle maintenance record. It requires a path parameter 'cid' which is the company identifier. The request body must include details such as 'odometer_reading', 'performed_at', 'performed_on', 'type', and 'vehicle' information including 'id' and 'display_name'. Upon successful creation, a 201 status code is returned. If the user is unauthorized, a 401 status code is returned. A 403 status code is returned if the user lacks access to the resource, and a 503 status code is returned if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Post Web Clock

ID: post_web_clock
Operation: write
Entities: coordinate, cost center, web clock
Summary: The Post Web Clock API is used for clocking in and out, changing cost centers, and collecting extra pay. The API requires an action type, which can be one of punch, punch_in, punch_out, change_ccs, or collect_ep. If the action is change_ccs, cost center details must be provided. If the action is collect_ep, extra pay details must be included. Optional parameters include latitude and longitude coordinates, custom punch button ID, and NFC tag ID. The API returns a status indicating success or failure, along with details of the punch action performed. Possible response codes include 200 for success, 503 for service unavailable, 400 for bad request, 406 for not acceptable, 413 for request entity too large, 415 for unsupported media type, and 500 for internal server error.
Input Fields: Input Fields
Output Fields: Output Fields

Post Workload Manager

ID: post_workload_manager
Operation: write
Entities: workload manager, schedule, company
Summary: The Post Workload Manager API allows users to send volume data to the Scheduler, creating workload coverage and open shifts based on the provided data. The API requires the Advanced Scheduler (SCHEDULE) Subsystem and Workload Manager functionality to be enabled in the company setup. The request must include the company ID as a path parameter and a JSON body containing the schedule ID, staffing matrix name, and an array of volume data entries. The response provides details on the number of processed, skipped, and added volume data entries, along with any user messages or errors encountered during processing.
Input Fields: Input Fields
Output Fields: Output Fields

Put Access Policy Profile

ID: put_access_policy_profile
Operation: write
Entities: access policy profile, access option, company
Summary: The Put Access Policy Profile API allows an existing access policy profile to be updated by its ID. The user must have permission to edit access policies. The API requires the company ID (cid) and access policy profile ID (aid) as path parameters. The request body includes details such as the profile ID, name, description, active status, mobile access allowance, and access options with IP ranges. The API returns various HTTP status codes indicating the result of the operation, including 204 for success, 400 for validation errors, 401 for unauthorized access, 403 for forbidden access, 404 for resource not found, and 503 for service unavailability due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Put Account Group

ID: put_account_group
Operation: write
Entities: manager, account group, company
Summary: The Put Account Group API allows an existing regular account group to be replaced. It requires the company ID (cid) and account group ID (gid) as path parameters. The request body must include the name, description, members, and managers of the account group. The API returns a 204 No Content response if the account group is successfully replaced. If the user is not authorized, a 401 Unauthorized response is returned. A 403 Forbidden response is returned if the user has no access to the resource. If the resource does not exist, a 404 Not Found response is returned. A 503 Service Unavailable response is returned if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Put Accrual Balances

ID: put_accrual_balances
Operation: write
Entities: accrual balance, employee, company
Summary: The Put Accrual Balances API endpoint allows for the modification of an employee's accrual balance. The API requires the company ID (cid) and account ID (aid) as path parameters. The request body must include the accrual category ID, modification date, hours (in milliseconds), action (such as ADD, SET, or DEDUCT), a comment, and an optional ignore_warnings flag. If warnings are generated, they will be sent to the client, and the operation will not be committed unless ignore_warnings is set to true. The API returns various HTTP status codes, including 204 for successful operations with no content, and error codes such as 400, 401, 403, 404, 500, and 503 for different failure scenarios.
Input Fields: Input Fields
Output Fields: Output Fields

Put Accrual Balances Update

ID: put_accrual_balances_update
Operation: write
Entities: accrual balance, employee, company
Summary: The Put Accrual Balances Update API allows updating employee accrual balances for a specified company. The API requires a path parameter 'cid' which is the company identifier. The request body includes an array of 'accrual_balances' objects, each containing details such as company short name, employee username, time off type, as of date, updated to date, hours, and external accrual details. The 'updated_to_date' can be set to a specific date or to the end of the accrual year. The hours and external fields are in HH:MM or HH.DD format. The API does not specify any response details.
Input Fields: Input Fields
Output Fields: Output Fields

Put Additional Compensation

ID: put_additional_compensation
Operation: write
Entities: employee, compensation, company
Summary: The 'Put Additional Compensation' API updates an employee's additional compensation record. It requires the company ID ('cid') and the additional compensation record ID ('acid') as path parameters. The request body must include details such as the compensation ID, account ID, type ID, currency, effective date, change date, period, active status, value, and related links. The API returns a 204 No Content response upon successful update. Possible error responses include 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Put Announcement Statistics

ID: put_announcement_statistics
Operation: write
Entities: employee, announcement, company
Summary: The Put Announcement Statistics API allows updating the statistics of announcement popups for a specific employee within a company. The request requires path parameters 'cid' for the company identifier and 'aid' for the account identifier. The request body must include a list of statistics, each containing an 'announcement_id' and 'total_times' indicating how many times the announcement was shown. A successful update returns a 204 No Content response.
Input Fields: Input Fields
Output Fields: Output Fields

Put Applicant

ID: put_applicant
Operation: write
Entities: account, applicant, company
Summary: The Put Applicant API allows updating an existing applicant by their account ID. It requires the company ID (cid) and account ID as path parameters. The request body includes detailed applicant information such as account details, address, phones, demographics, salary requirements, education, skills, work experiences, references, job categories, and custom fields. The API responds with a 204 No Content status on success, and various error codes like 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable for different failure scenarios.
Input Fields: Input Fields
Output Fields: Output Fields

Put Asset Assignment

ID: put_asset_assignment
Operation: write
Entities: asset, employee, asset assignment
Summary: The Put Asset Assignment API endpoint is used to replace an existing asset assignment identified by its ID with a new one provided in the request payload. It requires the company ID and asset assignment ID as path parameters. The request body must include details about the employee and the asset, including various properties such as brand, model, and purchase details. The API returns a 204 No Content response on successful execution, indicating that the asset assignment has been updated. Other possible responses include 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Put Asset Assignment Action

ID: put_asset_assignment_action
Operation: write
Entities: asset assignment, action, company
Summary: The 'Put Asset Assignment Action' API allows performing actions such as marking an asset assignment as returned or lost/destroyed. It requires the company ID, asset assignment ID, and the action name as path parameters. The request body can include optional fields like comments, date, and status change. The API returns a 204 No Content response on success, with possible error responses including 403 Forbidden, 404 Not Found, and 503 Service Unavailable. The 'X-CallLimit-TimeToWait' header indicates the wait time if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Put Badges

ID: put_badges
Operation: write
Entities: badge, employee, company
Summary: The Put Badges API is used to update the badge information of an employee. It requires the company ID (cid) and account ID (aid) as path parameters. The request body should contain an array of badge objects, each with properties such as badge_type, badge_number, and optionally pin, short_id, effective_from, and effective_to. The API responds with a 204 status code if the update is successful. It may also return 401 if the user is unauthorized, 403 if access is forbidden, 404 if the resource is not found, and 503 if the service is unavailable due to call limits.
Input Fields: Input Fields
Output Fields: Output Fields

Put Batch Update

ID: put_batch_update
Operation: write
Entities: time entry, employee, company
Summary: The Put Batch Update API allows users to replace all existing time entries for a given employee and date range, with a maximum date range of 31 days. The API supports two types of entries: EXTRA_PAY and TIME. EXTRA_PAY supports only date, amount, from, and to fields, while TIME supports all fields except amount, from, and to. The total is ignored when start_time or end_time are specified. Default values for Cost Centers, Shift Premium, and Custom Fields are always overridden. To use this API, users must have DELETE and EDIT permissions and access to at least one of the following subsystems: TLM or TLM (Small Business Edition: PR/HR Version). The API requires a path parameter 'cid' to specify the company, and the request body must include time entry sets with employee account IDs, start and end dates, and time entries. The response includes the updated time entry sets. Possible responses include 200 OK for success, 401 Unauthorized for unauthorized users, 403 Forbidden for users without access, 413 Request Entity Too Large for payloads exceeding limits, and 503 Service Unavailable when the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Put Cancel Pre Note

ID: put_cancel_pre_note
Operation: write
Entities: pre note, direct deposit, company
Summary: This API endpoint is used to cancel pre-notes for selected direct deposits for a specified company. The endpoint has been deprecated as of April 13, 2023, but will continue to function according to the deprecation policy. The request requires a path parameter 'cid' which is the company identifier, and a request body containing 'direct_deposit_ids', an array of integers representing the IDs of the direct deposits to cancel pre-notes for. A successful request returns a 204 No Content response, indicating that the cancel pre-note operation was successful. If the request fails, a 400 Bad Request response is returned.
Input Fields: Input Fields
Output Fields: Output Fields

Put Collection

ID: put_collection
Operation: write
Entities: rate schedule, rate table, company
Summary: The Put Collection API is used to update rate schedules collection for a specific company and rate table. It requires the company ID (cid) and rate table ID (tid) as path parameters. The request body contains an array of rate schedules, each with details such as line number, type, description, rate items, rate reason code, usage, and various records (time entry, counter, global, payroll). The API returns a 204 No Content response on successful update, indicating that the rate schedules were successfully updated. If there is a validation error, a 400 Bad Request response is returned.
Input Fields: Input Fields
Output Fields: Output Fields

Put Collection for Bulk Shift Creation

ID: put_collection_for_bulk_shift_creation
Operation: write
Entities: shift, schedule, company
Summary: The Put Collection API allows for bulk creation of multiple shifts within a specified schedule for a company. The API requires the Advanced Scheduler (SCHEDULE) Subsystem to be enabled in the company setup. It takes path parameters 'cid' for the company identifier and 'schedule_id' for the schedule identifier. The request body includes an array of shifts with details such as shift ID, account information, date, type, start and end times, cost centers, skills, shift premiums, and average rates. The API returns a status message indicating the success or failure of the operation, with possible responses including 200 Ok, 403 Forbidden, 404 Not Found, 406 Not Acceptable, 413 Request Entity Too Large, and 500 Internal Server Error.
Input Fields: Input Fields
Output Fields: Output Fields

Put Company Tax Quarter Status

ID: put_company_tax_quarter_status
Operation: write
Entities: quarter, tax, company
Summary: The 'Put Company Tax Quarter Status' API updates the status of a specified tax quarter for a company. It requires the company ID (cid), the year, and the quarter number (q) as path parameters. The request body must include the new status for the tax quarter. Upon successful update, the API returns a 204 No Content response, indicating that the status was successfully updated.
Input Fields: Input Fields
Output Fields: Output Fields

Put Company Tax Year Status

ID: put_company_tax_year_status
Operation: write
Entities: tax year, status, company
Summary: The 'Put Company Tax Year Status' API updates the status of a company's tax year. It requires the company ID ('cid') and the year as path parameters. The request body must include the 'status' field to specify the new status of the tax year. Upon successful update, the API returns a 204 No Content response, indicating that the status was successfully updated.
Input Fields: Input Fields
Output Fields: Output Fields

Put Contact

ID: put_contact
Operation: write
Entities: contact, employee, company
Summary: The Put Contact API is used to update an existing employee's contact information. It requires the company ID (cid) and the employee contact ID (id) as path parameters. The request body includes various fields such as employee account ID, contact details (name, phone numbers, email), national identification numbers, and personal attributes (birthdate, gender, ethnicity, etc.). The API supports backward compatibility with fields like 'bsn', 'social_insurance', 'social_security', and 'national_insurance', but prefers the 'national_id_numbers' field for new patterns. The response can be a 204 No Content if successful, or various error codes like 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Put Contracts

ID: put_contracts
Operation: write
Entities: employee, contract, company
Summary: The Put Contracts API is used to update existing employee contracts for a specified company. The API requires the company ID as a path parameter. The request body must include contract details such as contract ID, company short name, employee account ID, hours and days worked, start and end dates, and other contract-specific information. The API supports updating multiple contracts in a single request. The response will indicate the success or failure of each contract update, with detailed error messages if applicable. The API returns various HTTP status codes to indicate the result of the request, including 200 for success, 400 for bad requests, and 500 for server errors.
Input Fields: Input Fields
Output Fields: Output Fields

Put Cost Center

ID: put_cost_center
Operation: write
Entities: job strain, cost center, company
Summary: The Put Cost Center API allows updating an existing cost center by its ID. The endpoint requires the company ID (cid) and cost center ID (ccid) as path parameters. The request body includes various fields such as external_id, abbreviation, name, payroll_code, description, and more, which are used to fully replace the existing cost center resource. The API requires specific subsystems to be enabled and appropriate permissions for editing cost center definitions. The response can be a 204 No Content for successful updates, or error codes like 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable for various failure scenarios.
Input Fields: Input Fields
Output Fields: Output Fields

Put Cost Center Action

ID: put_cost_center_action
Operation: write
Entities: cost center, action, company
Summary: The Put Cost Center Action API allows users to perform actions on a cost center, such as moving it to a new parent cost center. The API requires the company ID (cid), cost center ID (ccid), and the action name (action_name) as path parameters. The request body must include the new parent cost center ID. The user must have the necessary permissions and the required subsystems must be enabled. A successful request returns a 204 No Content response. Possible error responses include 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable.
Input Fields: Input Fields
Output Fields: Output Fields

Put Cost Center Job

ID: put_cost_center_job
Operation: write
Entities: employee, cost center job, company
Summary: The 'Put Cost Center Job' API endpoint allows users to update a specific Cost Center Job within a company. The user must have the necessary permissions to edit a Cost Center Job and must be part of one of the required subsystems (HR or HR Small Business Edition). The API requires two path parameters: 'cid' (the company identifier) and 'id' (the cost center job identifier). The request body contains detailed information about the job, including its category, name, description, and various attributes related to payroll, visibility, and employee type. The API returns a 204 No Content response upon successful update, or error responses such as 401 Unauthorized, 403 Forbidden, 404 Not Found, and 503 Service Unavailable in case of issues.
Input Fields: Input Fields
Output Fields: Output Fields

Put Counter Adjustment

ID: put_counter_adjustment
Operation: write
Entities: employee, counter adjustment, company
Summary: The Put Counter Adjustment API updates a counter adjustment for a specific employee within a company. It requires path parameters including the company ID (cid), account ID (aid), and counter adjustment ID (counter_adjustment_id). The request body must include the record date, counter ID, cost centers, value, reset flag, and reason code. The response returns the updated counter adjustment details, including the ID, record date, counter information, cost centers, value, reset status, and reason code. Possible responses include 200 OK for success, 400 Bad Request for validation errors, 403 Forbidden for security issues, 404 Not Found if the counter adjustment ID is not found, 500 Internal Server Error for server issues, 204 No Content, 401 Unauthorized for unauthorized access, and 503 Service Unavailable if the call limit is exceeded.
Input Fields: Input Fields
Output Fields: Output Fields

Put Counters for Leave of Absence

ID: put_counters_for_leave_of_absence
Operation: write
Entities: leave of absence, employee, company
Summary: This API endpoint is used to update the leave of absence counters for an employee in a company. The request requires the company ID (cid) and account ID (aid) as path parameters. The body of the request contains an array of items, each representing a leave of absence counter with details such as entitlement, entitlement type, id, taken amount, taken as of date, taken type, and an optional comment. The API returns a 204 No Content response upon successful update, indicating that the leave of absence was successfully updated. The user must have the necessary permissions to edit leave of absence cases and modify leave of absence balances.
Input Fields: Input Fields
Output Fields: Output Fields