Skip to content

Authentication and API Keys

Choose browser authorization or an API Key and generate configuration safely.

Browser authorization

Clients that support OAuth can open a browser when connecting to PeopleRouter. Sign in to DINQ and authorize access, following the relevant client guide. You do not need to create an API Key first.

Signing in to your account does not mean a client is connected. Return to the client after authorization and confirm that the PeopleRouter tools are loaded. Workspace administrator permissions may also affect connector availability.

API Keys

Scripts, backend services, and integrations requiring a fixed credential can use a DINQ API Key. Create or revoke credentials in API Key management; the client guides show the appropriate configuration fields.

A DINQ API Key is different from an OpenAI or Anthropic API Key. They are not interchangeable. Keep real credentials out of chats, screenshots, and source control.

Generate configuration examples

Expand developer settings in a client guide, explicitly enable Key mode, then enter the credential. Configuration updates as you type, and each copy button copies only its current code block. Setup instructions intended for an agent always use a placeholder instead of the entered Key.

To resume setup, the entered Key is stored in the current browser. Use this only on a trusted device; select Clear in the guide or sign out to remove it. Reopening the documentation never enables Key mode automatically, even when a Key was saved.

You can read every guide without entering a credential. Examples that need one retain a <DINQ_API_KEY> placeholder; replace it locally or configure an environment variable as required by your client.

Troubleshoot authentication

  • Browser authorization incomplete: return to the client's MCP or connector settings and start authorization again.
  • Key revoked or incorrect: check its status in Key management and update the local configuration. Do not print credentials in public logs.
  • Network or tool error: inspect the actual error and response, and read Troubleshooting. An authentication failure is not an empty search result.