httpbin

HTTP request/response testing service. Perfect for debugging and testing API integrations.

Detail	Value
Category	Testing
Base URL	https://httpbin.org
Authentication	None
Endpoints	8
Connector key	httpbin

Using httpbin in a workflow

1. Go to Connections and click New Connection.
2. Pick httpbin from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET /get	Returns GET data
POST /post	Returns POST data
PUT /put	Returns PUT data
DELETE /delete	Returns DELETE data
GET /status/{codes}	Return status code
GET /headers	Returns request headers
GET /ip	Returns origin IP
GET /user-agent	Returns user-agent string

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /get

Returns GET data

Detail	Value
Operation ID	test.get
Method	GET
Path	/get

Parameters

Name	Location	Type	Required
foo	query	string	No

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.get.
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 httpbin API reference.

POST /post

Returns POST data

Detail	Value
Operation ID	test.post
Method	POST
Path	/post

Parameters

No parameters.

Request Body

Field	Type
data	string

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.post.
4. 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 httpbin API reference.

PUT /put

Returns PUT data

Detail	Value
Operation ID	test.put
Method	PUT
Path	/put

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.put.
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 httpbin API reference.

DELETE /delete

Returns DELETE data

Detail	Value
Operation ID	test.delete
Method	DELETE
Path	/delete

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.delete.
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 httpbin API reference.

GET /status/{codes}

Return status code

Detail	Value
Operation ID	test.status
Method	GET
Path	/status/{codes}

Parameters

Name	Location	Type	Required
codes	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.status.
4. 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 httpbin API reference.

GET /headers

Returns request headers

Detail	Value
Operation ID	test.headers
Method	GET
Path	/headers

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.headers.
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 httpbin API reference.

GET /ip

Returns origin IP

Detail	Value
Operation ID	test.ip
Method	GET
Path	/ip

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.ip.
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 httpbin API reference.

GET /user-agent

Returns user-agent string

Detail	Value
Operation ID	test.userAgent
Method	GET
Path	/user-agent

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your httpbin connection from the Connection dropdown.
3. In the Operation dropdown, select test.userAgent.
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 httpbin API reference.