Tadata

https://docs.tadata.com/
Admin
Tadata is an AI-agent builder that provides optimized, pre-configured integrations and one-click...
Tokens:13,150
Snippets:203
Trust Score:7
Update:10 months ago
Show doc for...
Tokens:
Raw
### Passthrough Authentication Request Examples

Source: https://docs.tadata.com/authentication/passthrough

Demonstrates how to send credentials (OAuth Bearer token or API Key) in the Authorization header for tool execution requests within Tadata's passthrough authentication mode. This ensures secure and direct credential handling.

```http
POST https://your-toolset.mcp.tadata.com/execute
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...
Content-Type: application/json

{
  "tool": "create_issue",
  "parameters": { ... }
}
```

```http
POST https://your-toolset.mcp.tadata.com/execute
Authorization: Bearer sk_live_abc123xyz789
Content-Type: application/json
```

```http
POST https://your-toolset.mcp.tadata.com/execute
X-API-Key: abc123xyz789
Content-Type: application/json
```

--------------------------------

### API Key (Query Param) Authentication Configuration

Source: https://docs.tadata.com/guides/bringing-your-own

Configures API key authentication using a query parameter. This method is less common but supported by some APIs. It requires the authentication type, the name of the query parameter, and the API key. An example request is provided.

```json
{
  "authType": "query",
  "paramName": "api_key",
  "apiKey": "your-api-key-here"
}
```

--------------------------------

### API Key (Header) Authentication Configuration

Source: https://docs.tadata.com/guides/bringing-your-own

Configures API key authentication using a header. This is common for internal APIs. It requires specifying the authentication type, header name, optional header prefix, and the API key itself. The example shows a Bearer token format.

```json
{
  "authType": "header",
  "headerName": "Authorization",
  "headerPrefix": "Bearer ",
  "apiKey": "your-api-key-here"
}
```

--------------------------------

### Debug: Missing Required Parameter Error JSON

Source: https://docs.tadata.com/guides/testing-playground

This JSON snippet indicates a 'Missing required parameter' error, occurring when an AI agent fails to provide a necessary parameter for a tool's execution. Solutions involve improving tool descriptions, providing examples, or being more specific in prompts.

```json
{
  "error": "Missing required parameter: title"
}
```

--------------------------------

### Basic Auth Authentication Configuration

Source: https://docs.tadata.com/guides/bringing-your-own

Configures Basic Authentication using a username and password. Credentials are automatically base64-encoded and sent in the `Authorization` header. This is a simple authentication method.

```json
{
  "authType": "basic",
  "username": "your-username",
  "password": "your-password"
}
```

--------------------------------

### Debug: 403 Forbidden Error JSON

Source: https://docs.tadata.com/guides/testing-playground

This JSON snippet represents a 403 Forbidden error, indicating that the authenticated user does not have permission to access the requested resource. Causes include insufficient account permissions, non-existent or private resources, or exceeding rate limits.

```json
{
  "error": "Forbidden",
  "code": 403
}
```

--------------------------------

### OAuth 2.0 Authentication Configuration

Source: https://docs.tadata.com/guides/bringing-your-own

Configures OAuth 2.0 authentication for APIs that support it. This is more complex and requires the client ID, client secret, authorization URL, token URL, and the desired scopes. Tadata handles the OAuth flow and token refresh.

```json
{
  "authType": "oauth",
  "clientId": "your-client-id",
  "clientSecret": "your-client-secret",
  "authorizationUrl": "https://api.example.com/oauth/authorize",
  "tokenUrl": "https://api.example.com/oauth/token",
  "scopes": ["read", "write"]
}
```

--------------------------------

### Debug: Invalid Parameter Value Error JSON

Source: https://docs.tadata.com/guides/testing-playground

This JSON snippet illustrates an 'Invalid parameter value' error, where a provided parameter does not match the expected format or enum values. Troubleshooting involves checking tool documentation, updating prompts, or adding enum constraints.

```json
{
  "error": "Invalid status: 'Completed'. Must be one of: backlog, todo, in_progress, done, canceled"
}
```

--------------------------------

### API Key Passthrough Authentication

Source: https://docs.tadata.com/authentication/passthrough

Configure and use passthrough authentication with API keys. This method is simpler and suitable when you don't want Tadata to store API keys.

```APIDOC
## API Key Passthrough Authentication

### Description
This endpoint facilitates passthrough authentication using API keys. Your AI agent securely stores and provides the API key with each request.

### Method
POST

### Endpoint
`/execute` (within your configured toolset endpoint)

### Parameters
#### Request Headers
- **[Configured Header Name]** (string) - Required - The API key, potentially prefixed as configured (e.g., `Authorization: Bearer <your-api-key>` or `X-API-Key: <your-api-key>`).

#### Request Body
- **tool** (string) - Required - The name of the tool to execute.
- **parameters** (object) - Required - The parameters for the tool execution.

### Request Example (Bearer Token)
```json
{
  "tool": "send_message",
  "parameters": { ... }
}
```

### Request Example (Custom Header)
```json
{
  "tool": "get_data",
  "parameters": { ... }
}
```

### Response
#### Success Response (200)
- **result** (any) - The result of the tool execution.

#### Response Example
```json
{
  "result": "Data retrieved successfully."
}
```
```

--------------------------------

### Debug: Timeout Error JSON

Source: https://docs.tadata.com/guides/testing-playground

This JSON snippet represents a 'Timeout' error, signifying that an API request exceeded the allowed response time. This can be due to service issues, large request scopes, or the need for pagination.

```json
{
  "error": "Request timeout after 30s"
}
```

--------------------------------

### Debug: 401 Unauthorized Error JSON

Source: https://docs.tadata.com/guides/testing-playground

This JSON snippet represents a 401 Unauthorized error, indicating issues with authentication such as an expired token, incorrect API key, or insufficient permissions. It's commonly encountered when a service cannot verify the client's identity.

```json
{
  "error": "Unauthorized",
  "code": 401
}
```

--------------------------------

### OAuth Passthrough Authentication

Source: https://docs.tadata.com/authentication/passthrough

Configure and use passthrough authentication with OAuth tokens. This method requires the AI agent to control the OAuth resource, handle the OAuth flow, and manage tokens.

```APIDOC
## OAuth Passthrough Authentication

### Description
This endpoint facilitates passthrough authentication using OAuth tokens. Your AI agent must manage the OAuth flow, token generation, and refresh.

### Method
POST

### Endpoint
`/execute` (within your configured toolset endpoint)

### Parameters
#### Request Headers
- **Authorization** (string) - Required - The OAuth access token in the format `Bearer <your-access-token>`.

#### Request Body
- **tool** (string) - Required - The name of the tool to execute.
- **parameters** (object) - Required - The parameters for the tool execution.

### Request Example
```json
{
  "tool": "create_issue",
  "parameters": { ... }
}
```

### Response
#### Success Response (200)
- **result** (any) - The result of the tool execution.

#### Response Example
```json
{
  "result": "Issue created successfully."
}
```
```
Tokens:
Raw