Skip to main content

Authentication

Standard non-authenticated HTTP requests​

You can use HTTP requests without authentication, if the service provider or web server receiving the request does not require authentication.

Authenticated HTTP requests to existing service providers​

HTTP Actions can be used with most of Blink's connection types to send authenticated requests to existing service providers in Blink. For example, to send an authenticated request to GitHub's API, use a GitHub connection.

Thumbnail

Authenticated HTTP requests to unsupported service providers​

Blink adds support for additional service providers on a weekly basis. To use Actions with a service provider that is not currently supported, there are two options:

  1. Contact the Blink team to request integration with a new service provider. Contact us.
  2. Use generic HTTP Actions to communicate with unsupported service providers, as explained below.

Using generic HTTP actions to communicate with unsupported service providers​

HTTP Actions can be used with one of the three HTTP connection types to send authenticated requests to service providers that aren't currently supported by Blink:

  1. HTTP Basic Authentication
  2. HTTP Bearer Authentication
  3. HTTP Custom Authentication

For example, to communicate with a service provider called X that isn't supported by Blink and requires Basic Authentication:

  1. Create an HTTP Basic Authentication connection with the required credentials.
Thumbnail
  1. Use the connection to perform the Action, and the outgoing HTTP request will be sent with the appropriate authentication headers.
Thumbnail