BusyBot

Reference · Credentials

HTTP Query Auth credentials

Used by 2 BusyBot nodes.

Type httpQueryAuth 2 fields

HTTP Query Auth appends an authentication value as a URL query parameter — the pattern older APIs use, such as `?api_key=…`. You supply the parameter name and value, and the node adds it to every request.

Fields

FieldTypeRequiredNotes
Name
name		 string Yes Query parameter name
Value
value		 password Yes Query parameter value

Getting your credentials

  1. Check the target API’s documentation for the query parameter name it expects — commonly api_key, apikey or token.
  2. Obtain the key value from that service.
  3. Enter the parameter name into Name and the key into Value.

Permissions and scopes

The key carries whatever access the issuing service granted. Where the service supports scoped or read-only keys, prefer one.

A caution worth knowing: values in a URL are more exposed than values in a header — they appear in server access logs, proxy logs and browser history. Where an API supports header authentication, prefer HTTP Header Auth instead.

Troubleshooting

  • 401 Unauthorized — the parameter name is wrong, or the API expects the key in a header instead.
  • Key visible in logs — that is inherent to query-parameter authentication. Switch to header auth if the API allows it.
  • Works in a browser — confirm the browser is not also sending a session cookie that is doing the real authentication.

Frequently asked questions

Is this less secure than header auth?

In practice yes — URLs are logged by servers, proxies and browsers, so the key is more exposed. Prefer HTTP Header Auth whenever the API supports it.

What parameter name should I use?

Exactly what the API documents — commonly `api_key`, `apikey` or `token`. There is no universal convention.

Which nodes use it?

The HTTP Request and GraphQL nodes.

Nodes that use HTTP Query Auth

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.