Tempo

Tempo provides time tracking, planning, and budgeting apps for Jira, used for resource and project management. The Tempo REST API exposes worklogs, timesheet approvals, and approval periods so teams can automate reporting and keep time-tracking data in sync with other systems.

Power end-to-end data operations for your Tempo API with Nexla. Our bi-directional Tempo connector is purpose-built for Tempo, 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 Tempo or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Tempo 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 Tempo credential, you need a Tempo API integration token generated from your Jira Cloud instance. Tempo authenticates API requests using a bearer token that you create in the Tempo settings, and each token can be scoped to specific access levels.

To generate a Tempo API integration token, follow these steps:

1. Sign in to your Jira Cloud instance with an account that has access to Tempo.

2. Open the Tempo settings menu, and select API Integration.

3. Click New Token (or Generate) to create a new token.

4. Set an optional name and expiration for the token. By default, an access token is valid for 30 days.

5. Define the access scope for the token. You can grant full access to all APIs, or define custom access. View access permits GET requests within the scope, while Manage access permits GET, POST, PUT, and DELETE requests.

6. Click Generate, then copy the token immediately. The token is shown only once when it is first created. If you lose it, you must regenerate the token, which invalidates the previous one.

7. Store the token securely. You will provide it when configuring your Nexla credential.

The Nexla credential accepts either a username and API key or a username and password, depending on how your Tempo API access is provisioned. For most Tempo Cloud setups, the generated API integration token is the value you provide. For detailed information about token generation, scopes, and available endpoints, refer to the Tempo REST API documentation and the Using REST API integrations guide.

Authenticate

Credentials required

A standard authentication method that requires sending encoded username and password credentials

Field	Required	Secret	Description
Username Or API Key	Yes	No	Your username or personal API Key
Password	Yes	Yes	Your password

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 username or personal API key in the Username Or API Key field. For most Tempo Cloud setups, this is the account associated with your Tempo API integration token.

4. Enter your password or Tempo API integration token in the Password field. This value is stored securely and is used to authenticate all API requests to Tempo.

   Tempo API integration tokens can expire. If your token expires or is compromised, regenerate it in the Tempo API Integration settings and update this credential with the new value.

   For detailed information about Tempo authentication, token scopes, and available endpoints, see the Tempo REST API documentation and Using REST API integrations.

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 Tempo connector tile, then select the credential that will be used to connect to the Tempo instance, and click Next; or, create a new Tempo 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 Tempo 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 approval period

This endpoint template retrieves an approval period from Tempo. Use this template when you need to access the details of a timesheet approval period for analysis, reporting, or integration purposes.

For detailed information about approval periods, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Get secondary approval period

This endpoint template retrieves a secondary approval period from Tempo. Use this template when you need to access secondary approval period details for timesheet review workflows.

For detailed information about approval periods, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Get timesheet approval for reviewer

This endpoint template retrieves a timesheet approval for a reviewer. Use this template when you need to access approvals assigned to a specific reviewer for analysis or reporting.

For detailed information about timesheet approvals, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Get all approvals for a team in a period

This endpoint template retrieves all approvals that the user is allowed to see for a team in a given period. Use this template when you need a team-level view of timesheet approvals within a specific time frame.

For detailed information about team approval logs, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Get timesheet approval for specific user

This endpoint template retrieves a timesheet approval for a specific user. Use this template when you need approval details scoped to an individual user.

For detailed information about timesheet approvals, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Get approval statuses for a user over multiple periods

This endpoint template retrieves approval statuses for a specific user over multiple periods. Use this template when you need to track a user's timesheet approval history across several time periods.

For detailed information about approval statuses, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Get approval log for a specific user within a time frame

This endpoint template retrieves the approval log for a specific user within a time frame. Use this template when you need an audit trail of a user's approval activity over a defined range.

For detailed information about approval logs, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Create worklogs

This endpoint template creates worklogs in Tempo and returns the created records. Use this template when you need to record time entries and capture the resulting worklog data.

For detailed information about worklogs, request bodies, and response structures, see the Tempo REST API documentation.

[Rest API] Get worklog

This endpoint template retrieves a worklog from Tempo. Use this template when you need to access the details of a specific time entry for analysis, reporting, or integration purposes.

For detailed information about worklogs, request parameters, and response structures, see the Tempo REST API documentation.

[Rest API] Find existing worklogs

This endpoint template finds existing worklogs in Tempo based on your search criteria. Use this template when you need to retrieve a set of time entries matching specific filters for reporting or downstream processing.

For detailed information about searching worklogs, request parameters, and response structures, see the Tempo REST API documentation.

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

Tempo data sources can also be manually configured to ingest data from any valid Tempo 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 Tempo 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 Tempo destination, and select the Send to Destination option from the menu. Select the Tempo connector from the list of available destination connectors, then select the credential that will be used to connect to the Tempo instance, and click Next; or, create a new Tempo 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 Tempo 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] Post approvals

This endpoint template posts approvals to Tempo using records from a Nexset. Use this template when you need to submit timesheet approvals based on data from your Nexla flows.

Each record from your Nexset is sent as a request to the Tempo API. The request body must match the format expected by Tempo. For detailed information about posting approvals, request bodies, and required fields, see the Tempo REST API documentation.

[Rest API] Update existing worklog

This endpoint template updates an existing worklog in Tempo using records from a Nexset. Use this template when you need to modify previously recorded time entries based on data from your Nexla flows.

Each record from your Nexset is sent as a request to the Tempo API, and must include the identifier of the worklog to update. The request body must match the format expected by Tempo. For detailed information about updating worklogs, request bodies, and required fields, see the Tempo REST API documentation.

[Rest API] Delete worklog

This endpoint template deletes a worklog in Tempo using records from a Nexset. Use this template when you need to remove time entries based on data from your Nexla flows.

Each record from your Nexset must include the identifier of the worklog to delete. Deletions are permanent. For detailed information about deleting worklogs and required fields, see the Tempo REST API documentation.

Manual configuration

Tempo destinations can also be manually configured to send data to any valid Tempo 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.

Tempo APIs typically expect JSON format for most operations. For update or delete operations, include the identifier of the object to be modified in the request as required by the Tempo API.

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 Tempo endpoint, open the destination resource menu, and select Activate.

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