Appearance
imgix
undefined
| Detail | Value |
|---|---|
| Category | Media |
| Base URL | https://api.imgix.com/api/v1 |
| Authentication | Bearer Token |
| Endpoints | 5 |
| Connector key | imgix |
Using imgix in a workflow
- Go to Connections and click New Connection.
- Pick imgix from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Sources |
GET | Assets |
GET | Upload |
GET | Purge Cache |
GET | Bandwidth Reports |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Sources
| Detail | Value |
|---|---|
| Operation ID | sources_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your imgix connection from the Connection dropdown.
- In the Operation dropdown, select
sources_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream imgix API reference.
GET
Assets
| Detail | Value |
|---|---|
| Operation ID | assets_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your imgix connection from the Connection dropdown.
- In the Operation dropdown, select
assets_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream imgix API reference.
GET
Upload
| Detail | Value |
|---|---|
| Operation ID | upload_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your imgix connection from the Connection dropdown.
- In the Operation dropdown, select
upload_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream imgix API reference.
GET
Purge Cache
| Detail | Value |
|---|---|
| Operation ID | purge_cache_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your imgix connection from the Connection dropdown.
- In the Operation dropdown, select
purge_cache_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream imgix API reference.
GET
Bandwidth Reports
| Detail | Value |
|---|---|
| Operation ID | bandwidth_reports_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your imgix connection from the Connection dropdown.
- In the Operation dropdown, select
bandwidth_reports_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream imgix API reference.