HTTP Authentication

Requisitos previos

To create a connection using the HTTP connector, you must provide the details needed for the selected authentication type. See the following sections for information on the details required for each authentication type. For information on how to retrieve these details, refer to the documentation of the API provider.

UiPath User Access Token

Establish a connection through supported UiPath services. No configuration required.

Código de autorización OAuth 2.0

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
• Client secret - The confidential secret key for your application as provided by your OAuth provider.
• Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g. https://login.example.com/oauth2/authorize).
• Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g. https://login.example.com/oauth2/token).
• Scope - The required OAuth scopes based on your API provider or integration needs.

Additional configuration:

• Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g. https://example.com/docs/oauth/refresh)
• Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (https://example.com/docs/oauth/revoke).
• Refresh interval - Time in seconds between OAuth token refresh attempts.
• OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.

Código de autorización OAuth 2.0 con PKCE

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
• Client secret - The confidential secret key for your application as provided by your OAuth provider.
• Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g. https://login.example.com/oauth2/authorize).
• Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g. https://login.example.com/oauth2/token).
• Scope - The required OAuth scopes based on your API provider or integration needs.

Additional configuration:

• Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g. https://example.com/docs/oauth/refresh)
• Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (https://example.com/docs/oauth/revoke).
• Refresh interval - Time in seconds between OAuth token refresh attempts.
• OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.

Credenciales de cliente OAuth 2.0

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
• Client secret - The confidential secret key for your application as provided by your OAuth provider.
• Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g. https://login.example.com/oauth2/token).
• Scope - The required OAuth scopes based on your API provider or integration needs.

Additional configuration:

• Refresh interval - Time in seconds between OAuth token refresh attempts.
• OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.

Contraseña OAuth 2.0

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Username - The end-user's username credential for authentication.
• Password - The end-user's password credential for authentication.
• Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
• Client secret - The confidential secret key for your application as provided by your OAuth provider.
• Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g. https://login.example.com/oauth2/authorize).
• Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g. https://login.example.com/oauth2/token).
• Scope - The required OAuth scopes based on your API provider or integration needs.

Additional configuration:

• Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g. https://example.com/docs/oauth/refresh).
• Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (https://example.com/docs/oauth/revoke).
• Refresh interval - Time in seconds between OAuth token refresh attempts.
• OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.

Autenticación básica

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Username - The username credential for your API account.
• Password - The password credential for your API account.

Additional configuration:

• Authentication validation API - Enter the relative path that will be used to verify your authentication credentials (e.g. /api/v1/me, /user/profile, /auth/validate). This API route should return a successful response when your credentials are valid.

Clave API

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Parameter name - The exact name of the API key parameter as required by your API (e.g. X-API-Key, api_key, Authorization). This will be used as either a header name or query parameter name based on your selection.
• Value - Your complete API key value as provided by your API provider. This will be securely stored and used for authentication.

Additional configuration:

• Add to - Select whether to add the API key in the request header or as a query parameter. Header is recommended for better security.
• Authentication validation API - Enter the relative path that will be used to verify your authentication credentials (e.g. /api/v1/me, /user/profile, /auth/validate). This API route should return a successful response when your credentials are valid.

OAuth 2.0 JWT Bearer

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Client ID - The unique identifier for your application as provided by your OAuth provider during app registration.
• Client secret - The confidential secret key for your application as provided by your OAuth provider.
• JWT base64 encoded key - Your Base64-encoded private key. Ensure you follow your API provider's instructions for key generation and encoding.
• Authorization URL - The full authorization endpoint URL as provided by your OAuth provider (e.g. https://login.example.com/oauth2/authorize).
• Token URL - The token endpoint URL where authorization codes or credentials are exchanged for access tokens as provided by your OAuth provider (e.g. https://login.example.com/oauth2/token).
• Scope - The required OAuth scopes based on your API provider or integration needs.

Additional configuration:

• Refresh token URL - The refresh token endpoint URL as provided by your OAuth provider (e.g. https://example.com/docs/oauth/refresh).
• Token revoke URL - The token revocation endpoint URL as provided by your OAuth provider (https://example.com/docs/oauth/revoke).
• Refresh interval - Time in seconds between OAuth token refresh attempts.
• OAuth basic header - Enable to send Client ID and Secret as a basic authentication header during OAuth token exchange. Most providers need this enabled.

Token de acceso personal

Introduzca los siguientes datos:

• Connection name - A descriptive name to help you identify this connection.
• Base URL - The base URL of your API (e.g. https://api.example.com).
• Token prefix - The token prefix (e.g. Bearer, Token, Basic). This will be combined with your token in the Authorization header. Leave empty if no prefix is required.
• Token - The complete personal access token value. This will be combined with the token type in the Authorization header (e.g. Bearer your-token-here).

Additional configuration:

• Authentication validation API - Enter the relative path that will be used to verify your authentication credentials (e.g. /api/v1/me, /user/profile, /auth/validate). This API route should return a successful response when your credentials are valid.

Add the HTTP connection

1. Selecciona Integration Service en la barra izquierda.
2. From the Connectors list, select HTTP. You can also use the search bar to find the connector.
3. Select the Connect to HTTP button.
4. In the connection screen, provide the required details.
5. Select Connect.
6. Se ha agregado su conexión.