Skip to content

CRE: HTTP Trigger link revert #3597

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dev-dist merged 1 commit into from
Mar 25, 2026
Merged

CRE: HTTP Trigger link revert #3597

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/content/cre/guides/workflow/using-triggers/http-trigger/local-testing-tool.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ Create a `.env` file in the package root:

```bash
PRIVATE_KEY=0xYourPrivateKeyHere
GATEWAY_URL=https://01.gateway.zone-a.app.chain.link
GATEWAY_URL=https://01.gateway.zone-a.cre.chain.link
```

Replace `0xYourPrivateKeyHere` with your EVM private key.
Expand Down Expand Up @@ -160,7 +160,7 @@ When the server processes your request, you'll see logs in the terminal where th

Response: Response (297 bytes) {
ok: true,
url: "https://01.gateway.zone-a.app.chain.link/",
url: "https://01.gateway.zone-a.cre.chain.link/",
status: 200,
statusText: "OK",
...
Expand Down
2 changes: 1 addition & 1 deletion src/content/cre/guides/workflow/using-triggers/http-trigger/overview-go.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ This section provides everything you need to work with HTTP triggers:
| ------------------ | ------------------------------- | -------------------------------------------------------- |
| **Authorization** | Optional (can use empty config) | Required (`authorizedKeys` must be configured) |
| **Trigger method** | CLI with `--input` flag | HTTP POST to gateway endpoint with JWT |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.app.chain.link`) |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.cre.chain.link`) |
| **Use case** | Development, testing, debugging | Live integrations, webhooks, production APIs |

## Key concepts
Expand Down
2 changes: 1 addition & 1 deletion src/content/cre/guides/workflow/using-triggers/http-trigger/overview-ts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ This section provides everything you need to work with HTTP triggers:
| ------------------ | ------------------------------- | -------------------------------------------------------- |
| **Authorization** | Optional (can use empty config) | Required (`authorizedKeys` must be configured) |
| **Trigger method** | CLI with `--input` flag | HTTP POST to gateway endpoint with JWT |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.app.chain.link`) |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.cre.chain.link`) |
| **Use case** | Development, testing, debugging | Live integrations, webhooks, production APIs |

## Key concepts
Expand Down
4 changes: 2 additions & 2 deletions ...e/guides/workflow/using-triggers/http-trigger/triggering-deployed-workflows.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Details:
All workflow executions use JSON-RPC 2.0 format:

```http
POST https://01.gateway.zone-a.app.chain.link
POST https://01.gateway.zone-a.cre.chain.link
Content-Type: application/json
Authorization: Bearer <JWT_TOKEN>

Expand Down Expand Up @@ -233,7 +233,7 @@ If you're testing deployed workflows during development, use the [Local Testing
Here's what a complete curl request looks like:

```bash
curl -X POST https://01.gateway.zone-a.app.chain.link \
curl -X POST https://01.gateway.zone-a.cre.chain.link \
-H "Content-Type: application/json" \
-H "Authorization: Bearer eyJhbGciOiJFVEgiLCJ0eXAiOiJKV1QifQ.eyJkaWdlc3QiOiIweDRhMWYyYjNjNGQ1ZTZmN2E4YjljMGQxZTJmM2E0YjVjNmQ3ZThmOWEwYjFjMmQzZTRmNWE2YjdjOGQ5ZTBmMWEiLCJpc3MiOiIweGIwOEUwMDRiZDJiNWFGZjFGNUY5NTBkMTQxZjQ0OUIxYzA1ODAwZWIiLCJpYXQiOjE3MzM4MzIwMDAsImV4cCI6MTczMzgzMjMwMCwianRpIjoiNTUwZTg0MDAtZTI5Yi00MWQ0LWE3MTYtNDQ2NjU1NDQwMDAwIn0.r7s8v9recoveryId..." \
-d '{
Expand Down
10 changes: 5 additions & 5 deletions src/content/cre/llms-full-go.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1637,7 +1637,7 @@ Details:
All workflow executions use JSON-RPC 2.0 format:

```http
POST https://01.gateway.zone-a.app.chain.link
POST https://01.gateway.zone-a.cre.chain.link
Content-Type: application/json
Authorization: Bearer <JWT_TOKEN>

Expand Down Expand Up @@ -1801,7 +1801,7 @@ If you're testing deployed workflows during development, use the [Local Testing
Here's what a complete curl request looks like:

```bash
curl -X POST https://01.gateway.zone-a.app.chain.link \
curl -X POST https://01.gateway.zone-a.cre.chain.link \
-H "Content-Type: application/json" \
-H "Authorization: Bearer eyJhbGciOiJFVEgiLCJ0eXAiOiJKV1QifQ.eyJkaWdlc3QiOiIweDRhMWYyYjNjNGQ1ZTZmN2E4YjljMGQxZTJmM2E0YjVjNmQ3ZThmOWEwYjFjMmQzZTRmNWE2YjdjOGQ5ZTBmMWEiLCJpc3MiOiIweGIwOEUwMDRiZDJiNWFGZjFGNUY5NTBkMTQxZjQ0OUIxYzA1ODAwZWIiLCJpYXQiOjE3MzM4MzIwMDAsImV4cCI6MTczMzgzMjMwMCwianRpIjoiNTUwZTg0MDAtZTI5Yi00MWQ0LWE3MTYtNDQ2NjU1NDQwMDAwIn0.r7s8v9recoveryId..." \
-d '{
Expand Down Expand Up @@ -1984,7 +1984,7 @@ Create a `.env` file in the package root:

```bash
PRIVATE_KEY=0xYourPrivateKeyHere
GATEWAY_URL=https://01.gateway.zone-a.app.chain.link
GATEWAY_URL=https://01.gateway.zone-a.cre.chain.link
```

Replace `0xYourPrivateKeyHere` with your EVM private key.
Expand Down Expand Up @@ -2077,7 +2077,7 @@ When the server processes your request, you'll see logs in the terminal where th

Response: Response (297 bytes) {
ok: true,
url: "https://01.gateway.zone-a.app.chain.link/",
url: "https://01.gateway.zone-a.cre.chain.link/",
status: 200,
statusText: "OK",
...
Expand Down Expand Up @@ -15247,7 +15247,7 @@ This section provides everything you need to work with HTTP triggers:
| ------------------ | ------------------------------- | -------------------------------------------------------- |
| **Authorization** | Optional (can use empty config) | Required (`authorizedKeys` must be configured) |
| **Trigger method** | CLI with `--input` flag | HTTP POST to gateway endpoint with JWT |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.app.chain.link`) |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.cre.chain.link`) |
| **Use case** | Development, testing, debugging | Live integrations, webhooks, production APIs |

## Key concepts
Expand Down
10 changes: 5 additions & 5 deletions src/content/cre/llms-full-ts.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1623,7 +1623,7 @@ Details:
All workflow executions use JSON-RPC 2.0 format:

```http
POST https://01.gateway.zone-a.app.chain.link
POST https://01.gateway.zone-a.cre.chain.link
Content-Type: application/json
Authorization: Bearer <JWT_TOKEN>

Expand Down Expand Up @@ -1787,7 +1787,7 @@ If you're testing deployed workflows during development, use the [Local Testing
Here's what a complete curl request looks like:

```bash
curl -X POST https://01.gateway.zone-a.app.chain.link \
curl -X POST https://01.gateway.zone-a.cre.chain.link \
-H "Content-Type: application/json" \
-H "Authorization: Bearer eyJhbGciOiJFVEgiLCJ0eXAiOiJKV1QifQ.eyJkaWdlc3QiOiIweDRhMWYyYjNjNGQ1ZTZmN2E4YjljMGQxZTJmM2E0YjVjNmQ3ZThmOWEwYjFjMmQzZTRmNWE2YjdjOGQ5ZTBmMWEiLCJpc3MiOiIweGIwOEUwMDRiZDJiNWFGZjFGNUY5NTBkMTQxZjQ0OUIxYzA1ODAwZWIiLCJpYXQiOjE3MzM4MzIwMDAsImV4cCI6MTczMzgzMjMwMCwianRpIjoiNTUwZTg0MDAtZTI5Yi00MWQ0LWE3MTYtNDQ2NjU1NDQwMDAwIn0.r7s8v9recoveryId..." \
-d '{
Expand Down Expand Up @@ -1970,7 +1970,7 @@ Create a `.env` file in the package root:

```bash
PRIVATE_KEY=0xYourPrivateKeyHere
GATEWAY_URL=https://01.gateway.zone-a.app.chain.link
GATEWAY_URL=https://01.gateway.zone-a.cre.chain.link
```

Replace `0xYourPrivateKeyHere` with your EVM private key.
Expand Down Expand Up @@ -2063,7 +2063,7 @@ When the server processes your request, you'll see logs in the terminal where th

Response: Response (297 bytes) {
ok: true,
url: "https://01.gateway.zone-a.app.chain.link/",
url: "https://01.gateway.zone-a.cre.chain.link/",
status: 200,
statusText: "OK",
...
Expand Down Expand Up @@ -14767,7 +14767,7 @@ This section provides everything you need to work with HTTP triggers:
| ------------------ | ------------------------------- | -------------------------------------------------------- |
| **Authorization** | Optional (can use empty config) | Required (`authorizedKeys` must be configured) |
| **Trigger method** | CLI with `--input` flag | HTTP POST to gateway endpoint with JWT |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.app.chain.link`) |
| **Endpoint** | Local simulator | CRE gateway (`https://01.gateway.zone-a.cre.chain.link`) |
| **Use case** | Development, testing, debugging | Live integrations, webhooks, production APIs |

## Key concepts
Expand Down
Loading