OpenParable
Skip to content
← Back to skills

HTTP Request Skill

Apps & Automation
http-request-skill

HTTP Request Skill is an Agent Skill for apps & automation published in the zeenie-ai/OpenCompany repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Make HTTP requests to external APIs and web services. Supports GET, POST, PUT, DELETE, PATCH methods with headers and JSON body.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/zeenie-ai/OpenCompany/blob/HEAD/server/skills/web_agent/http-request-skill/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/http-request-skill, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

HTTP Request Tool

Make HTTP requests to external APIs and web services.

How It Works

This skill provides instructions for the HTTP Request tool node. Connect the HTTP Request node to Zeenie's input-tools handle to enable API calls.

http_request Tool

Make an HTTP request to any URL.

Schema Fields

FieldTypeRequiredDescription
urlstringYesFull URL to request (e.g., https://api.example.com/data)
methodstringNoHTTP method: GET, POST, PUT, DELETE, PATCH (default: GET)
bodyobjectNoRequest body as JSON object (for POST/PUT/PATCH)
useProxybooleanNoRoute through proxy (default: false). The proxy service handles provider selection, geo-targeting, and session type automatically.

Node Parameters

Additional options can be configured on the node:

ParameterDescription
headersCustom headers as JSON (e.g., {"Authorization": "Bearer token"})
base_urlBase URL prepended to the url parameter

Response Format

{
  "status": 200,
  "data": { "key": "value" },
  "url": "https://api.example.com/data",
  "method": "GET",
  "proxied": false
}

Examples

GET request (fetch data):

{
  "url": "https://api.example.com/users/123",
  "method": "GET"
}

POST request (create resource):

{
  "url": "https://api.example.com/users",
  "method": "POST",
  "body": {
    "name": "John Doe",
    "email": "[email protected]"
  }
}

PUT request (update resource):

{
  "url": "https://api.example.com/users/123",
  "method": "PUT",
  "body": {
    "name": "John Updated"
  }
}

DELETE request:

{
  "url": "https://api.example.com/users/123",
  "method": "DELETE"
}

PATCH request (partial update):

{
  "url": "https://api.example.com/users/123",
  "method": "PATCH",
  "body": {
    "status": "active"
  }
}

Real-World Examples

Get Bitcoin price:

{
  "url": "https://api.coindesk.com/v1/bpi/currentprice.json",
  "method": "GET"
}

Get weather:

{
  "url": "https://api.openweathermap.org/data/2.5/weather?q=London&appid=YOUR_KEY",
  "method": "GET"
}

Post to webhook:

{
  "url": "https://hooks.slack.com/services/xxx",
  "method": "POST",
  "body": {
    "text": "Hello from OpenCompany!"
  }
}

Check website status:

{
  "url": "https://example.com",
  "method": "GET"
}

Error Responses

Timeout:

{
  "error": "Request timed out"
}

Connection failed:

{
  "error": "Connection failed: Unable to reach host"
}

HTTP error:

{
  "status": 404,
  "data": "Not Found",
  "url": "https://api.example.com/missing",
  "method": "GET"
}

HTTP Status Codes

StatusMeaningAction
200-299SuccessProcess the response data
400Bad RequestCheck request parameters
401UnauthorizedCheck API key/authentication
403ForbiddenInsufficient permissions
404Not FoundCheck URL path
429Too Many RequestsRate limited, wait and retry
500-599Server ErrorExternal service issue

Use Cases

Use CaseMethodDescription
Fetch dataGETRetrieve resources
Create resourcePOSTAdd new data
Update resourcePUT/PATCHModify existing data
Delete resourceDELETERemove data
Health checkGETVerify service availability
Webhook triggerPOSTSend events to services

Proxy Usage

To route a request through a residential proxy, just set useProxy: true. The proxy service automatically selects the best provider, geo-target, and session type from its configuration. A proxy provider must be configured first via the proxy_config tool (see proxy-config-skill).

Proxied request:

{
  "url": "https://example.com/data",
  "method": "GET",
  "useProxy": true
}

If no proxy providers are configured or the proxy lookup fails, the request proceeds directly without a proxy and "proxied": false appears in the response.

Guidelines

  1. URLs: Must be fully qualified with protocol (https://)
  2. Authentication: Use node headers for API keys/tokens
  3. Timeout: Default 30 seconds
  4. JSON body: Automatically serialized for POST/PUT/PATCH
  5. Response: JSON responses are automatically parsed
  6. Proxy: Set useProxy: true to route through proxy -- the proxy service handles all routing details

Security Notes

  1. Never expose API keys in responses to users
  2. Validate URLs before making requests
  3. Avoid internal/private network addresses (localhost, 192.168.x.x)
  4. Respect rate limits of external services
  5. Don't store sensitive data from API responses

Setup Requirements

  1. Connect the HTTP Request node to Zeenie's input-tools handle
  2. Configure authentication headers on the node if needed
  3. Ensure network access to target APIs
  4. For proxy usage: configure a proxy provider via the proxy-config-skill first