Jibble API

Jibble is a time-tracking and workforce-attendance platform. Its REST API exposes members, locations, schedules, activities, projects, time and hour entries, timesheets, approvals, reports, and time-off data. Most read endpoints support OData query options (such as $filter, $expand, $select, and $orderby) so you can retrieve exactly the data you need in a single request.

Power end-to-end data operations for your Jibble API API with Nexla. Our bi-directional Jibble API connector is purpose-built for Jibble API, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Jibble API or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Jibble API workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Jibble credential, you need a Client ID and Client Secret from your Jibble organization. The Jibble API uses OAuth2 with the client credentials grant: Nexla exchanges your Client ID and Client Secret for a bearer access token at Jibble's identity service (https://identity.prod.jibble.io/connect/token) and uses that token to authorize API requests. API credentials can only be created by an organization owner.

To obtain your Jibble API credentials:

1. Sign in to Jibble as an organization owner.

2. Open your Organization Settings and select the API Credentials tab.

3. Click Create New Secret to generate a new API credential.

4. Copy the generated API Key ID (Client ID) and API Key Secret (Client Secret). The secret is shown only once, so store it securely before leaving the page.

For details on authentication and the available endpoints, see the Jibble API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	No	The Client ID from the API Credentials tab in Jibble Organization Settings
Client Secret	Yes	Yes	The Client Secret from the API Credentials tab in Jibble Organization Settings

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Jibble Client ID in the Client ID field.

4. Enter your Jibble Client Secret in the Client Secret field. This value is treated as a secret and must be kept confidential.

   If your Client Secret is compromised, revoke it in your Jibble Organization Settings under the API Credentials tab and create a new secret.

   For detailed information about authentication and available endpoints, see the Jibble API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Jibble API connector tile, then select the credential that will be used to connect to Jibble, and click Next; or, create a new Jibble API credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Jibble endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] Get Organization Info

Retrieve all the organizations available for the authenticated access token.

[Rest API] Get Members

Retrieves people associated with the organization. OData query parameters (such as $filter and $expand) are available to enable more precise data retrieval.

[Rest API] Create Member

Creates a new member and optionally sends an invitation email. The IPersonSetting/SendInviteEmail parameter is optional; when set to true, an email invitation is sent to the specified member.

[Rest API] List Available Roles

List the roles available to be set for members.

[Rest API] Get Locations

Retrieves the list of locations from the workspace, excluding those with a status of 'Archived'. The response includes the ID, name, code, address, and geofence.

[Rest API] Add Location

Create a new Location object.

[Rest API] Get Schedules

Get the schedules of an organization.

[Rest API] Get Activities

Retrieve all Activity objects from the organization.

[Rest API] Check Projects

Get all projects from the organization.

[Rest API] List of raw Time Entries

List of time entries. OData $filter query options let you retrieve exactly the data you need in a single request rather than performing several.

[Rest API] List of raw Hour Entries

List of hour entries. OData $filter query options let you retrieve exactly the data you need in a single request rather than performing several.

[Rest API] Get Total Count of People by time entry type

Returns a real-time count of people currently clocked in, out, or on a break, filtered by the provided scope and optional identifiers.

[Rest API] Get the Latest Time Entry

Get the latest time entry for a person.

[Rest API] People Clocked In

Retrieves people associated with the organization who are currently active. OData query parameters (such as $filter and $select) are available to enable more precise data retrieval.

[Rest API] Get Approval configurations

Lists all available approval (pay period) configurations, including the displayed name of the pay period definition and its cycle type.

[Rest API] Summary

Get a summary of approval periods for members, including the pay period identifier, end date, and totals.

[Rest API] Details

Gets detailed information for an approval with a breakdown per day, including the pay period identifier, start date, end date, person, totals, and status.

[Rest API] Timesheets

Get timesheets for a given date and period.

[Rest API] Timesheets daily summary

Gets a daily timesheets summary for a given date range and set of persons. Omit the personIds parameters to return data for all members of the organization.

[Rest API] Tracked Time Report

Generic endpoint for retrieving time tracking reports. Use the groupBy and subGroupBy parameters to group the data; subGroupBy can be set to None to return the data with a single level of grouping.

[Rest API] Get Time Off policies

Get all organization time off policies. OData query parameters are supported.

[Rest API] Get Time Offs

Get time offs for the organization. OData query parameters are supported; see the request examples for parameter usage.

[Rest API] Create Time Off request

Create a new time off request for a person against a specific Time Off Policy, with a start date, end date, and optional note.

[Rest API] Leave Balance

Get leave balances for a person, filtered by policy status and assignment.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Jibble API data sources can also be manually configured to ingest data from any valid Jibble API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Jibble API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Jibble destination, and select the Send to Destination option from the menu. Select the Jibble API connector from the list of available destination connectors, then select the credential that will be used to connect to Jibble, and click Next; or, create a new Jibble API credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Jibble endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Add Project

Add a new project to the organization using records from a Nexset.

[Rest API] Clock In

Clock a person in by creating a time entry from records in a Nexset.

[Rest API] Clock In with LocationID

Clock a person in at a specific location by creating a time entry that includes a location identifier.

[Rest API] Clock Out

Clock a person out by creating a time entry from records in a Nexset.

[Rest API] Change status

Change the status of an approval pay period.

[Rest API] Approve/reject/cancel Time Off request

Approve, reject, or cancel an existing time off request.

Manual configuration

Jibble API destinations can also be manually configured to send data to any valid Jibble API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Jibble APIs expect JSON format for write operations. For update operations, include the identifier of the object to be updated in the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Jibble endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Jibble endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.