Eric Allam
6d9dfbc75d
And move the ApiClient configuration away from AsyncLocalStorage and use our globals system instead
47 lines
1.4 KiB
Plaintext
47 lines
1.4 KiB
Plaintext
---
|
|
title: "API keys"
|
|
description: "How to authenticate with Trigger.dev so you can trigger tasks."
|
|
---
|
|
|
|
### Authentication and your secret keys
|
|
|
|
When you [trigger a task](/v3/triggering) from your backend code, you need to set the `TRIGGER_SECRET_KEY` environment variable.
|
|
|
|
Each environment has its own secret key. You can find the value on the API keys page in the Trigger.dev dashboard:
|
|
|
|
|
|
|
|
### Automatically Configuring the SDK
|
|
|
|
To automatically configure the SDK with your secret key, you can set the `TRIGGER_SECRET_KEY` environment variable. The SDK will automatically use this value when calling API methods (like `trigger`).
|
|
|
|
```bash
|
|
export TRIGGER_SECRET_KEY=tr_dev_…
|
|
```
|
|
|
|
You can do the same if you are self-hosting and need to change the default URL by using `TRIGGER_API_URL`.
|
|
|
|
```bash
|
|
export TRIGGER_API_URL=https://trigger.example.com
|
|
```
|
|
|
|
The default URL is `https://api.trigger.dev`.
|
|
|
|
### Manually Configuring the SDK
|
|
|
|
If you prefer to manually configure the SDK, you can call the `configure` method:
|
|
|
|
```ts
|
|
import { configure } from "@trigger.dev/sdk/v3";
|
|
import { myTask } from "./trigger/myTasks";
|
|
|
|
configure({
|
|
secretKey: "tr_dev_1234", // WARNING: Never actually hardcode your secret key like this
|
|
baseURL: "https://mytrigger.example.com", // Optional
|
|
});
|
|
|
|
async function triggerTask() {
|
|
await myTask.trigger({ userId: "1234" }); // This will use the secret key and base URL you configured
|
|
}
|
|
```
|