Workline API OAS3

Introduction

Workline is a unique SaaS HRMS that is built from the ground-up based on your specific requirements. As applicable to retail as it is to factories and tech companies, Workline’s comprehensive HR modules, enterprise-grade security and powerful analytics make it a potent tool for business transformation.

Workline API provides a simple RESTful interface with lightweight JSON-formatted responses to use many of its features. Our API uses HTTPS verbs and is built using REST principles, which ensures predictable URLs that makes writing applications easy. REST API provides a powerful, convenient, and simple Web services API for interface. Its advantages include ease of design, integration and development.

Our current suite of APIs include:

  • Attendance Data Bulk Upload
  • Get Active Workforce Info
  • Get Inactive Workforce Info
  • Get NewJoinee Info
  • Get Workforce Career Info
  • Get Workforce Leave Balance
  • Get Workforce Leave Entitlement

With this guide we explain and provide examples for many common integration use cases and show you how to take advantage of Workline's capabilities.

HTTP Methods & Errors

  • GET - Reads a resource. Returns HTTP 200 on success.
  • POST - Creates a new resource. Returns HTTP 200 on success.
  • PUT - Updates a resource. Returns HTTP 200 on success.
  • DELETE - Deletes a resource. Returns HTTP 200 on success.

Workline uses conventional HTTP response codes to indicate the success or failure of an API request.

HTTP status code summary
200 - OK Everything worked as expected.
400 - Bad Request The request was unacceptable, often due to missing a required parameter.
401 - Unauthorized Invalid API Key / Invalid User Credentials.
402 - Request Failed The parameters were valid but the request failed.
403 - Forbidden The API key doesn't have permissions to perform the request.
404 - Not Found The requested resource doesn't exist.
429 - Too Many Requests Too many requests hit the API too quickly. We recommend an exponential backoff of your requests.
500, 502, 503, 504 - Server Errors Something went wrong at Workline end. Please try again after sometime. These are rare and usually resolved in few minutes.

Getting started

To use our API, you must satisfy the following prerequisites :

  • Client code
  • Authorization Credentials

Based on request, they will be provided to you through secured communication channels.

Access to External vendors

If your organization has external vendors who will be involved in interfacing applications, Workline will provide access to them with special credentials.For more information, please contact your Workline administrator and they will guide you through the process.

Authentication

Authentication to the API is performed via HTTP Basic Auth. Provide your user credentials as the basic auth username and password value. If you need to authenticate via bearer auth , use Bearer authentication tokens. Authentication tokens will be generated and provided to you over secure communication channels.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Never share your secret keys. Keep them guarded and secure.

API Keys

Workline uses API keys to authenticate requests. If you would like to create a new API key, please contact your Workline administrator.

Your API keys carry many privileges, so be sure to secure them! Do not share your secret API keys with any one.

Domains and IP Addresses

Based on your organization policy, domain & IP restrictions may have been implemented. To know more about this, please contact your Workline administrator.

API Call Limit

API calls are limited to provide better quality of service and availability to all the users.

Terms & Conditions