Skip to content
Tigy AI
/
Legal centerDashboard
OverviewDeveloper
Overview

Get started

  • Introduction
  • Overview
  • First agent
  • Tools and data
  • Concepts
    • How it works
    • Calls and runs

Configure

  • Behavior
    • Prompting
    • Conversation flow
  • Voice and models
    • LLM
    • Voice
    • Transcription
    • Fallbacks
    • Audio library
  • Tools
    • Tools
    • HTTP API
    • MCP
    • Credentials
    • Call transfer
    • End call
  • Knowledge base
  • Testing
  • Agent ID

Deploy

  • Publishing
  • Versions
  • Telephony
    • Introduction
    • Connect telephony
    • Inbound calls
    • Twilio
    • Telnyx
    • SIP

Monitor

  • Runs and usage
  • Reports
  • Troubleshooting

Workspace

  • Workspace
  • Members and permissions
  • Billing
  • Security
  • Privacy

Developer

  • Call data
Dashboard
Explore pages
Overview

Get started

  • Introduction
  • Overview
  • First agent
  • Tools and data
  • Concepts
    • How it works
    • Calls and runs

Configure

  • Behavior
    • Prompting
    • Conversation flow
  • Voice and models
    • LLM
    • Voice
    • Transcription
    • Fallbacks
    • Audio library
  • Tools
    • Tools
    • HTTP API
    • MCP
    • Credentials
    • Call transfer
    • End call
  • Knowledge base
  • Testing
  • Agent ID

Deploy

  • Publishing
  • Versions
  • Telephony
    • Introduction
    • Connect telephony
    • Inbound calls
    • Twilio
    • Telnyx
    • SIP

Monitor

  • Runs and usage
  • Reports
  • Troubleshooting

Workspace

  • Workspace
  • Members and permissions
  • Billing
  • Security
  • Privacy

Developer

  • Call data
Dashboard

Documentation / Tool credentials

Tool credentials

Authenticate HTTP tools, MCP servers and external data requests.

Credentials store the authentication Tigy AI uses to access an external system.

Before you start

Get authentication details from the external service's documentation. You need permission to manage the tool and select or create its workspace credential.

Configure authentication

  1. Open the HTTP or MCP tool.
  2. In the credential selector, choose an existing credential or create one for the service.
  3. Enter the authentication type and fields required by the form, such as API key, Bearer, Basic or a custom header.
  4. Associate the credential with the tool and save.
  5. Run a test lookup and inspect the external system's result.

The header name must match the service. Authorization and a header such as X-API-Key are not interchangeable unless the server supports both.

Keep secrets out of prompts

Do not put keys in agent instructions, prompt examples or public content. Use the stored credential in request configuration. For tests, prefer an account limited to the data and actions required.

Investigate rejections

ResultCheck
401Missing/expired key or incorrect authentication format
403Recognized account without access to the resource or operation
Connection failureURL and network; rotating a key does not fix an unreachable destination

Also confirm that the credential belongs to the tool's workspace. When changing a secret at the external service, update the associated credential and repeat a test before publishing.

← Back to documentation
© 2026 Tigy AItigyai.com ↗

On this page

  • Before you start
  • Configure authentication
  • Keep secrets out of prompts
  • Investigate rejections