HTTP Requests

The HTTP connector lets your workflows make HTTP requests to any API endpoint. It supports all standard HTTP methods with optional authentication and custom headers.

A connection is optional. You can use this connector without a connection for public APIs, or configure a connection to set a base URL and authentication for reuse across requests.

Connection setup (optional)

If you make multiple requests to the same API, configure a connection to avoid repeating the base URL and auth details:

Base URL: Common prefix for all requests (e.g., https://api.example.com)
Auth Method: None, Bearer token, API key, Basic auth, or OAuth 2.0
Token / API Key: For bearer or API key auth
Username / Password: For basic auth
OAuth 2.0 app: For APIs that authorize with an access token from your own OAuth app (see below)

The connection’s auth is sent as a default header on every request: Authorization: Bearer <token> for bearer and OAuth 2.0, X-API-Key: <key> for API key, and Authorization: Basic <credentials> for basic. A headers value on a tool call overrides the default.

OAuth 2.0 (bring your own app)

Choose OAuth 2.0 as the auth method when the API expects an access token issued by an OAuth 2.0 provider (GitHub, Google, Microsoft, HubSpot, and most SaaS APIs). You register an OAuth app with the provider and give Spojit its details; Spojit runs the authorization, stores the tokens securely and refreshes the access token before it expires.

Add this callback URL to your provider’s OAuth app:

https://miraxa.spojit.com/api/connectors/oauth/callback

Fill in the OAuth fields

On the connection’s Configure dialog choose OAuth 2.0 and enter the Authorization URL, Token URL, Client ID, Client Secret and Scopes. Under Advanced you can toggle PKCE and switch client authentication between POST body and Basic header. The Base URL works as usual.

Save & connect

Click Save & connect. Spojit redirects you to the provider to consent, then stores the tokens and marks the connection Connected. Every request through this connection carries Authorization: Bearer <access token>.

Editing the base URL later does not ask you to consent again. Changing the OAuth app details (URLs, client ID or secret, scopes) does, and Reconnect on the connection re-runs the flow at any time, for example after the provider revokes a token.

Switching the auth method from OAuth 2.0 back to a token method retires the OAuth app: the stored client secret and tokens are removed and the new token takes over. The same bring-your-own-app flow is used for custom MCP servers.

Tools

http-get: GET request

string

required

URL or path (if base URL is configured).

object

Custom HTTP headers.

number

Request timeout in milliseconds.

Example request:

{
  "url": "https://api.example.com/users/42",
  "headers": {
    "Accept": "application/json"
  }
}

Example response:

{
  "status": 200,
  "statusText": "OK",
  "headers": {
    "content-type": "application/json; charset=utf-8",
    "x-request-id": "req_abc123"
  },
  "data": {
    "id": 42,
    "name": "Alice Johnson",
    "email": "alice@example.com"
  }
}

http-post: POST request

string

required

URL or path.

any

Request body. If you keep the default JSON editor, the body is JSON-serialized with Content-Type: application/json auto-set. If you switch the editor to Text (via the ⋮ menu), the body is sent as the raw string; set your own Content-Type header to match (text/plain, application/xml, application/x-www-form-urlencoded, etc.).

object

Custom HTTP headers.

number

Request timeout in milliseconds.

Example request:

{
  "url": "https://api.example.com/orders",
  "body": {
    "customerId": "cust_8f3a",
    "items": [
      { "sku": "WIDGET-01", "quantity": 3 },
      { "sku": "GADGET-05", "quantity": 1 }
    ]
  },
  "headers": {
    "X-Idempotency-Key": "ord_20240315_001"
  }
}

Example response:

{
  "status": 201,
  "statusText": "Created",
  "headers": {
    "content-type": "application/json",
    "location": "/orders/ord_9k2m"
  },
  "data": {
    "id": "ord_9k2m",
    "customerId": "cust_8f3a",
    "total": 149.97,
    "status": "pending"
  }
}

http-put: PUT request

string

required

URL or path.

any

object

Custom HTTP headers.

number

Request timeout in milliseconds.

Example request:

{
  "url": "https://api.example.com/users/42",
  "body": {
    "name": "Alice Johnson",
    "email": "alice.johnson@example.com",
    "role": "admin"
  }
}

Example response:

{
  "status": 200,
  "statusText": "OK",
  "headers": {
    "content-type": "application/json"
  },
  "data": {
    "id": 42,
    "name": "Alice Johnson",
    "email": "alice.johnson@example.com",
    "role": "admin",
    "updatedAt": "2025-03-15T10:30:00Z"
  }
}

http-patch: PATCH request

string

required

URL or path.

any

object

Custom HTTP headers.

number

Request timeout in milliseconds.

Example request:

{
  "url": "https://api.example.com/users/42",
  "body": {
    "role": "editor"
  }
}

Example response:

{
  "status": 200,
  "statusText": "OK",
  "headers": {
    "content-type": "application/json"
  },
  "data": {
    "id": 42,
    "name": "Alice Johnson",
    "role": "editor",
    "updatedAt": "2025-03-15T11:45:00Z"
  }
}

http-delete: DELETE request

string

required

URL or path.

object

Custom HTTP headers.

number

Request timeout in milliseconds.

Example request:

{
  "url": "https://api.example.com/users/42"
}

Example response:

{
  "status": 204,
  "statusText": "No Content",
  "headers": {
    "x-request-id": "req_del_xyz789"
  },
  "data": ""
}

http-head: HEAD request

Returns response headers only (no body).

string

required

URL or path.

object

Custom HTTP headers.

number

Request timeout in milliseconds.

Example request:

{
  "url": "https://cdn.example.com/assets/logo.png"
}

Example response:

{
  "status": 200,
  "statusText": "OK",
  "headers": {
    "content-type": "image/png",
    "content-length": "24580",
    "cache-control": "public, max-age=86400",
    "etag": "\"abc123def456\""
  }
}

http-request: Generic HTTP request

Make a request with any HTTP method.

string

required

HTTP method: GET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS.

string

required

URL or path.

any

object

Custom HTTP headers.

number

Request timeout in milliseconds.

Example request:

{
  "method": "OPTIONS",
  "url": "https://api.example.com/uploads",
  "headers": {
    "Origin": "https://app.example.com"
  }
}

Example response:

{
  "status": 204,
  "statusText": "No Content",
  "headers": {
    "access-control-allow-origin": "https://app.example.com",
    "access-control-allow-methods": "GET, POST, PUT, DELETE",
    "access-control-allow-headers": "Content-Type, Authorization"
  },
  "data": ""
}

Overview

Integrations

Remote MCP Servers

Databases

Data Processing

Text and Strings

Numbers and Dates

Files and Media

Encoding and Validation

Developer Tools

Connection setup (optional)

OAuth 2.0 (bring your own app)

Tools

​Connection setup (optional)

​OAuth 2.0 (bring your own app)

​Tools

Connection setup (optional)

OAuth 2.0 (bring your own app)

Tools