Appearance
JSONPlaceholder
Free fake REST API for testing and prototyping. Returns realistic JSON data.
| Detail | Value |
|---|---|
| Category | Testing |
| Base URL | https://jsonplaceholder.typicode.com |
| Authentication | None |
| Endpoints | 7 |
| Connector key | jsonplaceholder |
Using JSONPlaceholder in a workflow
- Go to Connections and click New Connection.
- Pick JSONPlaceholder 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 /posts | Get all posts |
GET /posts/{id} | Get a post by ID |
POST /posts | Create a post |
PUT /posts/{id} | Update a post |
DELETE /posts/{id} | Delete a post |
GET /users | Get all users |
GET /comments | Get all comments |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /posts
Get all posts
| Detail | Value |
|---|---|
| Operation ID | test.listPosts |
| Method | GET |
| Path | /posts |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your JSONPlaceholder connection from the Connection dropdown.
- In the Operation dropdown, select
test.listPosts. - 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 JSONPlaceholder API reference.
GET /posts/{id}
Get a post by ID
| Detail | Value |
|---|---|
| Operation ID | test.getPost |
| Method | GET |
| Path | /posts/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your JSONPlaceholder connection from the Connection dropdown.
- In the Operation dropdown, select
test.getPost. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 JSONPlaceholder API reference.
POST /posts
Create a post
| Detail | Value |
|---|---|
| Operation ID | test.createPost |
| Method | POST |
| Path | /posts |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
title | string |
body | string |
userId | integer |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your JSONPlaceholder connection from the Connection dropdown.
- In the Operation dropdown, select
test.createPost. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 JSONPlaceholder API reference.
PUT /posts/{id}
Update a post
| Detail | Value |
|---|---|
| Operation ID | test.updatePost |
| Method | PUT |
| Path | /posts/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | integer | Yes |
Request Body
| Field | Type |
|---|---|
title | string |
body | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your JSONPlaceholder connection from the Connection dropdown.
- In the Operation dropdown, select
test.updatePost. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 JSONPlaceholder API reference.
DELETE /posts/{id}
Delete a post
| Detail | Value |
|---|---|
| Operation ID | test.deletePost |
| Method | DELETE |
| Path | /posts/{id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
id | path | integer | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your JSONPlaceholder connection from the Connection dropdown.
- In the Operation dropdown, select
test.deletePost. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
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 JSONPlaceholder API reference.
GET /users
Get all users
| Detail | Value |
|---|---|
| Operation ID | test.listUsers |
| Method | GET |
| Path | /users |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your JSONPlaceholder connection from the Connection dropdown.
- In the Operation dropdown, select
test.listUsers. - 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 JSONPlaceholder API reference.
GET /comments
Get all comments
| Detail | Value |
|---|---|
| Operation ID | test.listComments |
| Method | GET |
| Path | /comments |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
postId | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your JSONPlaceholder connection from the Connection dropdown.
- In the Operation dropdown, select
test.listComments. - 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 JSONPlaceholder API reference.