Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

API features

This page describes the different actions that can be performed with the Tailer API.

For the table-to-table configurations, don't forget to add at the end of the configuration_id the environnement (DEV, PROD, etc.) before querying it throw the APIs. __Example : the table-to-table configuration_id "000099_iowa_liquor_prepare_pda" in your json file in DEV environnement is referenced as the "000099_iowa_liquor_prepare_pda_DEV" in the payload below.

🔑 Get a JWT token

You will need to provide a JWT token for your API call. You can use different methods to get a JWT token based on your credentials.

You can use thetailer auth get-token function to get a few tokens, including a JWT token associated with the credentials you use with your tailer-sdk. You can get this token only using TAILER_API_JWT=tailer auth get-token | sed '7q;d' | sed 's/User token : //g'

🚀 Launching a job's execution

Tables to Tables or Tables to Storage data operations can be launched through the Tailer API.

You need to provide the full identity of the job as input (the execution_date parameter is optional):

TAILER_API_JWT=`tailer auth get-token | awk '/User token :/ {print $4}'` \
&& curl --request POST \
--http2 \
--header "content-type:application/json" \
--header "Authorization: Bearer ${TAILER_API_JWT}" \
--data '{ "action": "launch_job",
          "account": "000099",
          "environment": "DEV",
          "configuration_type": "table-to-table",
          "configuration_id": "000099_iowa_liquor_prepare_pda_DEV"}' \
"https://tailer-api-nqonovswsq-ew.a.run.app/v1/dag/launch"

As a result, the job is launched and you get a unique run ID in the following format:

🏃‍♂️ Checking a run's status

Once you have a run ID, you can check its current status to see how the processing is going.

You need to provide the full identity of the job and the run ID as input:

As a result, you get a json payload with information about the run in the following format:

⌛ Getting the last status of a job/data operation

You can check the current status for the latest run of a job/data operation.

You need to provide the full identity of the job/data operation as input. If needed, you can specify some parameters for the job/data operation in order to target a specific one:

Example with a job

As a result, you get a json payload with information about the last runs of this job in the following format:

Example with a data operation (configuration level)

As a result, you get a json payload with information about the last runs of this configuration in the following format:

Example with a data operation (configuration) with specific parameters

As a result, you get a json payload with information about the last 2 runs ins success, with a start date the 2020/12/09 of this configuration in the following format:

Getting job/data operations by status

You can list job/data operations using a specific status.

You need to provide at least the account, the environment and the configuration type:

Example with TTT

You can filter using a specific status:

You can filter further using a specific date

⚙️ Setting a run's status

Once you have a run ID, you can modify the status of any run.

You need to provide the full identity and run ID as input:

Note that only the following statuses are supported: SUCCESS, FAILED, RUNNING, NO_MATCH, CHECKED

0️⃣ Resetting a workflow

The Tailer API allows you to reset a Workflow data operation. The reset feature deletes all the triggered jobs so the workflow can start from scratch, as when the it was just deployed. (This feature is also available in Tailer Studio.)

Example of a case requiring a workflow reset

We have three jobs, named JA, JB, and JC which trigger a job named JT when they are all successfully executed.

If a situation happens where JA and JB are OK, but JC is not, JT is not triggered. You fix and relaunch JC, which becomes OK, and JT is triggered. The next morning, you launch JC again to make sure it works: you get JA(0), JB(0) and JC(1). When JA and JB are automatically started a few hours later, JC is already considered as OK, which creates an unbalanced situation. A reset is necessary.

You need to provide the full identity of the Workflow data operation as input:

As a result, you get a response (OK, or KO) in the following format:

⏹️ Disabling a data operation

You can disable a data operation (configuration) using the API. (This feature is also available in Tailer Studio.)

You need to provide the full identity of the data operation as input:

As a result, you get a response (OK, or KO) in the following format:

▶️ Enabling a data operation

You can enable a data operation that had been disabled using the API. (This feature is also available in Tailer Studio.)

You need to provide the full identity of the data operation as input:

As a result, you get a response (OK, or KO) in the following format:

▶️ Archive a data operation

You can archive a data operation using the API. (This feature is also available in Tailer Studio.)

You need to provide the full identity of the data operation as input:

As a result, you get a response (OK, or KO) in the following format:

PreviousGetting startedNextTailer Beta Releases

Last updated