TickTick

TickTick is a cross-platform task management and to-do application for organizing tasks, lists, and projects. The TickTick Open API lets applications read and manage a user's projects and tasks programmatically over REST, using an OAuth 2.0 access token for authentication.

Power end-to-end data operations for your TickTick API with Nexla. Our bi-directional TickTick connector is purpose-built for TickTick, 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 TickTick or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your TickTick 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 TickTick credential, you need a TickTick Open API access token. TickTick uses the OAuth 2.0 protocol to issue access tokens, and every API request is authenticated with the token sent in the Authorization header as a Bearer token.

To register an application and obtain an access token, follow these steps:

1. Sign in to the TickTick Developer Center using your normal TickTick account credentials.

2. Click Manage Apps in the top-right corner to open the app management page.

3. Click the +App Name button to register a new application. Enter a name for the app (for example, "Nexla Integration") and save it.

4. Open the newly created app to view its generated Client ID and Client Secret. These identify your application during the OAuth flow.

5. Set an OAuth Redirect URL for the app. This is the URL the user is redirected to after granting access; a local URL such as http://localhost is acceptable for most purposes.

6. Complete the OAuth 2.0 authorization flow to obtain an access token for the target user:

   • Direct the user to the TickTick authorization endpoint at https://ticktick.com/oauth/authorize, requesting the tasks:read and tasks:write scopes, which grant read and write access to tasks and projects.

   • After the user grants access, TickTick redirects to your redirect URL with an authorization code.

   • Exchange the authorization code for an access token by calling the TickTick token endpoint at https://ticktick.com/oauth/token with your Client ID and Client Secret.

7. Copy the resulting access token. This token is the value you will enter as the API Key when creating your Nexla credential.

The access token is sensitive and grants access to the associated TickTick account's projects and tasks. Store it securely and treat it as confidential. For complete details about registration, the OAuth flow, scopes, and available endpoints, see the TickTick Open API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	TickTick Open API access token (Bearer token).

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 TickTick Open API access token in the API Key field. This is the OAuth 2.0 access token you obtained in Prerequisites. Nexla sends this token in the Authorization header as a Bearer token on every API request.

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

List Projects

Retrieve all projects (lists) for the authenticated user.

• This endpoint returns every project accessible to the credential's access token. Use it to ingest the full set of the user's projects, or as the starting point for flows that then fetch details or tasks for each project.

Get Project

Retrieve a single project by project ID.

• This template first lists the user's projects and then fetches the details of a single project. Provide the Project ID in the endpoint configuration; the value can be chained from the project list returned by the first step.

List Project Tasks

Retrieve all tasks (and columns) within a project.

• This template first lists the user's projects and then fetches the tasks contained in a single project. Provide the Project ID in the endpoint configuration; the value can be chained from the project list returned by the first step.

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

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

Create Task

Create a new task.

• This endpoint sends each record from your Nexset as JSON in the request body to create a new task in TickTick. Ensure the record fields match the task structure expected by the TickTick Open API.

Update Task

Update an existing task by task ID.

• Provide the Task ID of the task to update in the endpoint configuration. Each record from your Nexset is sent as JSON in the request body with the updated task fields.

Delete Task

Delete a task by project ID and task ID.

• Provide the Project ID of the project the task belongs to and the Task ID of the task to delete in the endpoint configuration.

Complete Task

Mark a task as completed by project ID and task ID.

• Provide the Project ID of the project the task belongs to and the Task ID of the task to mark complete in the endpoint configuration.

Create Project

Create a new project.

• This endpoint sends each record from your Nexset as JSON in the request body to create a new project in TickTick. Ensure the record fields match the project structure expected by the TickTick Open API.

Update Project

Update an existing project by project ID.

• Provide the Project ID of the project to update in the endpoint configuration. Each record from your Nexset is sent as JSON in the request body with the updated project fields.

Delete Project

Delete an existing project by project ID.

• Provide the Project ID of the project to delete in the endpoint configuration.

Manual configuration

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

TickTick APIs expect JSON format for these operations. For update operations, include the ID of the object to be updated in the endpoint configuration.

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

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