Wiresk

Wiresk

Standard HTTP – Connection

Estimated reading time: 4 min
Standard HTTP Banner Standard HTTP - Connection

The Standard HTTP Connection allows you to connect Wiresk to any HTTP or REST API, even if no native app integration exists.
It provides multiple authentication options to match different API security requirements — from simple key-based access to OAuth or custom-signed authentication.

Once configured, the connection can be reused in any Flow to send or receive data through HTTP Methods.

Summary Table:

Authentication TypeStatusDescriptionTypical Use
Self-signed JWTComing SoonSigned JWT for secure APIsInternal enterprise systems
No AuthenticationAvailableSend requests without credentialsPublic or internal endpoints
Bearer (API Key or Token)AvailableAuthenticate using a tokenSlack, Notion, OpenAI
OAuth (Code)Coming SoonUser login and consent-based OAuthGoogle, HubSpot
Basic AuthenticationAvailableUsername/password accessLegacy or private APIs
OAuth (Client Credentials)Coming SoonMachine-to-machine authenticationMicrosoft Graph, Salesforce
Custom RequestComing SoonFully manual configuration with certificatesGovernment or banking APIs

Used to authenticate with APIs that require a self-signed JSON Web Token (JWT).
Instead of using static credentials, Wiresk generates a signed JWT with your defined claims and secret.

FieldDescription
Username / PasswordOptional credentials used by some APIs in combination with JWT payload claims.
Client ID / Client SecretIdentifies your application to the external API. Required for most JWT-based services.
JSON Configuration (advanced)Area to define the token payload in JSON format, including claims like issuer and audience.
DurationToken validity period in seconds (e.g., 3600).
Issuer (iss)Identifies who issued the token (e.g., your company domain).
Audience (aud)The target API’s base URL or audience identifier.
Subject (sub)Represents the entity (user or system) the token belongs to.
JWT ID (jti)Unique identifier for the token to prevent reuse.
URL (optional)Used for testing the generated token before saving the connection.
Add (JSON Data Type Selector)Adds elements like text, boolean, or key-value pairs to the payload JSON.

A company API expects a signed JWT with the following data:

{
  "iss": "mycompany.com",
  "sub": "integration_user",
  "aud": "https://api.partnerapp.com",
  "exp": 1698547200
}

After generating the JWT, Wiresk will include it in the Authorization header:

Authorization: Bearer eyJhbGciOi...
  • Internal enterprise APIs requiring token signing.
  • Financial, HR, or security systems enforcing strict JWT verification.

Used for APIs or endpoints that do not require any credentials. Wiresk sends requests without authorization headers.

Example:

GET https://api.publicapis.org/entries

Wiresk sends the request directly without authentication.

  • Open or public APIs.
  • Test or demo endpoints.
  • Internal URLs restricted by IP or network-level security.

Used for APIs that require a token or API key in the HTTP header.

FieldDescription
API Key or TokenEnter your access token or API key. Wiresk automatically includes it in the Authorization header.
URL (Optional)Used for testing the token with a sample endpoint.
Test ButtonSends a test request using your provided URL and token to confirm it works.
Create ButtonSaves the connection for reuse in Flows.

Connecting to Notion API

  • API Key or Token: secret_abcd123xyz
  • Test URL: https://api.notion.com/v1/users/me

Wiresk sends:

GET https://api.notion.com/v1/users/me
Authorization: Bearer secret_abcd123xyz
  • Notion, OpenAI, Slack, Airtable, SendGrid, or Telegram.
  • Any API using static tokens for authentication.
Keep tokens secure and update them if the API key rotates.

Implements OAuth 2.0 Authorization Code Flow where the user logs in and grants permission for Wiresk to access their data.
Used for APIs that require interactive authorization.

FieldDescription
Client IDApp identifier from your developer account.
Client SecretConfidential key paired with the Client ID.
Authorize URLURL where users are redirected to log in and approve access.
Token URLAPI endpoint that exchanges the authorization code for an access token.
ScopesList of permissions your integration requests (add multiple with the “Add” button).
Request Token PathOptional path to extract the token if the API returns it in a nested JSON structure.

Connecting to Google Calendar API

  • Client ID: 123456.apps.googleusercontent.com
  • Client Secret: GOCSPX-xyzABC123
  • Authorize URL: https://accounts.google.com/o/oauth2/auth
  • Token URL: https://oauth2.googleapis.com/token
  • Scopes: https://www.googleapis.com/auth/calendar.readonly
  • Google Workspace APIs (Drive, Calendar, Gmail).
  • HubSpot, Microsoft, or LinkedIn apps requiring user login.
  • Marketing platforms with user-level authorization.

Authenticates using a username and password encoded in Base64 and included in the Authorization header.

FieldDescription
UsernameThe account name or API user credential.
PasswordThe password or API token associated with the user.
URL (Optional)Used for testing the credentials before saving.
Test ButtonSends a test request to confirm authentication works.
Create ButtonSaves the connection configuration.

Private CRM API

  • Username: api_user
  • Password: securePass123
  • Test URL: https://crm.example.com/api/v1/contacts

Wiresk sends:

GET https://crm.example.com/api/v1/contacts
Authorization: Basic YXBpX3VzZXI6c2VjdXJlUGFzczEyMw==
  • Legacy REST APIs.
  • On-premise ERP systems.
  • Internal systems with basic HTTP access.
Use HTTPS to protect transmitted credentials.

Implements OAuth 2.0 Client Credentials Flow for system-level authentication.
Used for background or server-to-server access where no user consent is needed.

FieldDescription
Client IDApp identifier registered with the API provider.
Client SecretSecret key used to verify your app.
Token URLEndpoint where Wiresk requests the access token.
ScopesDefine access levels or resources (add multiple as needed).
Request Token PathOptional custom path to extract the returned token from a nested response.

Microsoft Graph API

  • Client ID: 7d59b5b7-8eab-4c89-83d2-0e2c6c8c59e5
  • Client Secret: V3V1b~XyQexampleSecret!
  • Token URL: https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token
  • Scopes: https://graph.microsoft.com/.default
  • Microsoft Graph, Salesforce, or SAP BTP service accounts.
  • System integrations without user login.
  • Automated reporting or sync tasks.

Provides complete flexibility to create a custom authentication request.
Ideal for APIs that use certificates, signatures, or proprietary login mechanisms.

FieldDescription
Auth URLEndpoint used to authenticate or retrieve tokens.
Username / PasswordOptional credentials for hybrid or multi-step authentication.
Client ID / Client SecretOptional credentials used in complex authentication payloads.
CertificateUpload client certificate (.pem, .pfx, .crt) for mTLS authentication.
JSON Configuration (advanced)Define custom request payloads for authentication.
MethodHTTP method (e.g., POST, GET, PUT).
Content TypeFormat of the request body (JSON, x-www-form-urlencoded).
Add ButtonsAdd key-value pairs or nested data to the JSON structure.
Request Token PathPath where Wiresk extracts the token from the API response.

Custom Certificate-Based API

  • Auth URL: https://secureapi.company.com/auth
  • Certificate: client_certificate.pem
  • Method: POST
  • Content Type: json
  • JSON Configuration: { "login": "apiuser", "password": "examplepass" }
  • Request Token Path: auth.token
  • Government, finance, or regulated systems with mTLS authentication.
  • Proprietary or legacy APIs with signed payloads.
  • Private corporate endpoints requiring certificates.

Each authentication type includes a Test button for instant verification:

  • Confirms endpoint accessibility.
  • Validates authentication success.
  • Displays test response (when applicable).

Once verified, click Create to save and reuse the connection in Flows.