Creating a connection with the HTTP connector is more complex than configuring a connection with a pre-built connector because it requires more customization. Base URI is a component of configuring an HTTP connection. As we continue to configure HTTP connectors, exports, and imports you will be asked to identify the relative URI.
Base URI: The starting point for any call made to the API endpoint, which is why it is configured on the connection.
Relative URI: This is more specific and used to make the call to retrieve or import the data needed in your flow. You will be asked to configure the relative URI in a variety of places on universal connectors including “How to Test a Connection?”, Exports, Lookups and Imports.
Authentication Types
When you are setting up a HTTP connector, authenticating the connection will be a bit complex with this type of connection because you are building everything from scratch. When you set up authentication on the HTTP connector, you will have the following options:
- Override HTTP status code for auth errors
- Path to auth error field in HTTP response body
- Auth error values
These fields allow you to let integrator.io specify whether or not the endpoint sends error messages for the authentication response that are not typical, and what those atypical responses mean.
Basic: Basic allows you to create a Base64-encoded username and password.
Cookie: Cookie is a session-based method that typically includes a unique cookie in the HTTP request header. For this authentication type, you will need to specify the HTTP method, what the absolute URL will be, which is where the cookie can be obtained, and finally an override HTTP status for success, for when the endpoints status code for success is not within the 200 range.
Custom: For a custom type, integrator.io will not perform any special authentication. You must configure the HTTP request fields of the import and export models to include placeholders for any required values. You can store these values in the encrypted and unencrypted fields in this connection.
Digest: With the digest authentication method, integrator.io sends the first request to the API, and the server responds with details that include a single-use number: a real value and a 401 unauthorized response. An encrypted array of data, including the username and password combined with the data received from the server in the first request, is sent back. The server uses the passed data to generate an encrypted string and compares it against what is sent in the previous step to authenticate requests.
OAuth 2.0: The OAuth 2.0 authentication type enables integrator.io to obtain limited access to an HTTP service on behalf of an account. The scope is a mechanism in OAuth 2.0 to limit an application’s access to an account.
Token: Token requires that there be a token within the request to validate that it is a successful call. With this type, you will need to specify where integrator.io should send the token by selecting an option from the “send token via” field.
WSSE: WSSE is an authentication type available for HTTP connectors that use SOAP. This authentication must be used where the connecting application expects crypto hash generated out of the username and password. This value is sent over as part of the header.