-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Description
Is your feature request related to a problem? Please describe.
A user is getting getting HTTP 429 when using Brillium with the Pipedream’s authentication method and then changing to use API Key and API Password works for them.
Describe the solution you'd like
Implement an authentication method that uses API Key and API Password, such as in the code
import { axios } from "@pipedream/platform";
const base64Encoded = Buffer.from(`${this.brillium.$auth.api_key}:${this.brillium.$auth.api_password}`).toString('base64');
return await axios($, {
url: `${this.brillium.$auth.api_url}Accounts`,
headers: {
Authorization: `Basic ${base64Encoded}`,
},
})
and consider the API URL is provided with leading /api/ as part of the URL, this is to honor improved instructions in the connection dialog.
Do you have a workaround?
No, the other authentication method doesn't seem reliable.
As of the leading /api/, the user can remove /api/ if he had to follow existing API credentials instructions in the connection dialog.
Comparable features in other tools?
N/A
Additional context
Reported by a user,
please use creds in 1PW using new trial Brillium account using sergio@pipekit.com
Metadata
Metadata
Assignees
Labels
Type
Projects
Status