Page Comparison

...

The full technical API specification is available here.

Scenarios and uses

This section describes various scenarios of how the Web Services can be used.

Authentication

Before you can call any other InTime Web Service method you must first call the authenticatethe authenticate() method. Providing valid credentials to this method will return an authentication token that must be provided with all other Web Service calls.

Modified Items

getModifiedItems() and getModifiedItemsWithRefCodeand getModifiedItemsWithRefCode() functions return a list of items that have been updated since a specific date and time. This is useful where you wish to maintain a copy of various entities in an external system.

...

Once you have a current copy you can then periodically check for any items that have been modified since the last update and just update the details of those modified items. This is much more efficient than attempting to update all entities every the time. 

Data Retrieval (Read operations)

There are a number of methods that enable you to read back the full details of an entity. The required entity can be identified by a number of different fields. Examples are:

getWorkerByRefCode() returns the worker entity that has the specified RefCode.

getClientById() returns the Client entity with the specified Id.

getPlacementByExternalId() returns the Placement entity with the specified External Id.

getUsersByExternalId() returns a list of User entities that have the specified External Id. For this method a list of items rather than a single items is returned as is it possible, although not advisable, to have multiple users with the same external Id.

getTimesheetById() returns the Timesheet with the specified Id.

These methods return a complex data structure that represents the InTime entity. Some of these also contain other data types that constain information about related entities. For example the Timesheet object Timesheet object that is returned from getTimesheetByIdfrom getTimesheetById() can also contain a number of InvoiceInfo objects that hold information about the invoices that the Timesheet is associated with. It also contains a number of Shift objects that detail the worked time that has been entered on the Timesheet.

There are also a number of Search type methods that retrieve multiple results. This enables you to retrieve a set of entities that are filtered according to some criteria. Examples are:

getTimesheetIdsWithStatusAndDatesForWorker() This returns a list of Timesheet Ids for a specific Worker that have a specific status within a certain date range.

getInvoicesForClient() This  This returns a list of all invoices relating to a specific Client.  

Data Creation (Write Operations)

With version 2.0 it is now possible to create data in InTime via the Web Services. This includes the following entities: Worker, Client, Manager, Consultant, Provider, Placement and Timesheet. These mostly take the form of createOrUpdateXXX as this allows the same method to be used to create the entity if it doesn't exist or update it if it does. Examples are: createOrUpdateWorker createOrUpdateWorker(), createorUpdatePlacement() and createOrUpdateProvider()

Timesheets

updateTimesheet() method will create a new Timesheet or update an existing one if it exists in Draft status. The Timesheet will be saved with Draft status. The Timesheet object you supply to this method must contain all the necessary data which includes a valid Placement reference, the Period End date and one or more Shifts. Each Shift must reference a valid Rate from the Placement, the Time worker or a Decimal value and the Date on which it was worked. It will normally be necessary to retrieve the details of the Placement the Timesheet relates to in order to correctly complete all the required fields.

submitTimesheet() would then be called to submit the Timesheet for approval once it has all the necessary time (Shifts) added to it. 

rejectTimesheet() or approveTimesheet() are then used to process the approval.

revertTimesheet() can also be used to revert a Submitted or Approved status Timesheet if required. This has exactly the same result as reverting a Timesheet though the InTime UI.

Single Sign On

getSingleSignOnToken() can be used to log in to InTime using an existing InTime User account. This method returns a token that you can then append to any valid InTime URL and it will allow you to retrieve the page as if you were logged into the system directly. This means you can embed InTime pages within another web site or retrieve other data.

Other methods

The interface also provides various other methods. Some examples:

getMissingTimesheetsForPlacement() identifes any periods within the specified range that do not contain an approved timesheet. The reponse will include a status that indicates if it is Missing, Draft or Submitted.

getAllPayElements() returns a list of all Pay Elements present in the system.

getURLForContractorsPayslip() retrieves the URL to viewing a workers Payslips. *InPay Linked systems only

Getting started

The InTime Web Service uses the Simple Object Access Protocol (SOAP) interface as opposed to REST. This is a stricter protocol than REST which means you can only call the defined methods available and the return types will be in a fixed format. Normally you would start by building "stub" code against the WSDL file that defines the interface.

...

From the command line run:

/axis2-1.6.2/bin/wsdl2java.sh -or -uri "https://demo.in-time.co.uk/services/IntimeServiceV2_0?wsdl"

This will produce the following files:

/src/uk/co/in_time/IntimeServiceV2_0Stub.java

/src/uk/co/in_time/IntimeServiceV2_0CallbackHandler.java

/src/uk/co/in_time/IntimeServiceV2_0IntimeWebServiceException.java

Include and reference these files in your application and you will be able to make calls to the Web Services. Some examples are given below.

Java Code Examples

Authenticate

Create or update a Worker

- createOrUpdatePlacement

...