---
title: Noname
slug: connectors/noname
docTags: 
createdAt: 2026-06-09T16:29:50.103Z
---

The Noname API Connector is a powerful tool designed to bridge the gap between your applications and the Noname API. By leveraging this connector, you can conveniently streamline your access to various functionalities provided by the Noname API.

## Getting Started

Before you begin, ensure you meet the following prerequisites:

- You must have a valid email address and password associated with your Noname API account.

## Key Features

The Noname API Connector offers a robust set of capabilities aimed at improving the efficiency of your operations:

1. **Fetch Specific Issue:** Allows you to retrieve the details of a specific issue by providing the corresponding ID.
2. **Access Issue Evidence:** Empowers you to gather supportive evidence associated with a specific issue. The required input is the respective Issue ID.

Please note that your ability to use these features effectively may depend on the permissions and access rights tied to your Noname API account. Always ensure that your account has sufficient privileges for the operations you wish to carry out.

# Configurations

## Noname Authentication

Authenticates using email and password.

### Configuration Parameters

| **Parameter** | **Description**                    | **Type** | **Required** |
| ------------- | ---------------------------------- | -------- | ------------ |
| url           | A URL to the target host           | string   | Required     |
| email         | Email                              | string   | Required     |
| password      | Password                           | string   | Required     |
| verify\_ssl   | Verify SSL certificate             | boolean  | Optional     |
| http\_proxy   | A proxy to route requests through. | string   | Optional     |

# Actions

## Get Issue by ID

Get issue by ID

### Endpoint

- **URL:** `/api/v3/issue/{{id}}`
- **Method:** `GET`

### Input

| **Argument Name**    | **Type** | **Required** | **Description**                           |
| -------------------- | -------- | ------------ | ----------------------------------------- |
| `path_parameters.id` | string   | Required     | Parameters for the Get Issue by ID action |

### Input Example

`{"path_parameters":{"id":"12345678-1234-1234-1234-123456789abc"}}`

### Output

| **Parameter** | **Type** | **Description**                  |
| ------------- | -------- | -------------------------------- |
| `status_code` | number   | HTTP status code of the response |
| `reason`      | string   | Response reason phrase           |

### Output Example

`{}`

## Get Issue Evidence

Get issue evidence by using the issue ID

### Endpoint

- **URL:** `/api/v3/issue/{{id}}/evidence`
- **Method:** `GET`

### Input

| **Argument Name**    | **Type** | **Required** | **Description**                              |
| -------------------- | -------- | ------------ | -------------------------------------------- |
| `path_parameters.id` | string   | Required     | Parameters for the Get Issue Evidence action |

### Input Example

`{"path_parameters":{"id":"12345678-1234-1234-1234-123456789abc"}}`

### Output

| **Parameter** | **Type** | **Description**                  |
| ------------- | -------- | -------------------------------- |
| `status_code` | number   | HTTP status code of the response |
| `reason`      | string   | Response reason phrase           |

### Output Example

`{}`

# Response Headers

| **Header**   | **Description**                                       | **Example**                   |
| ------------ | ----------------------------------------------------- | ----------------------------- |
| Content-Type | The media type of the resource                        | application/json              |
| Date         | The date and time at which the message was originated | Thu, 01 Jan 2024 00:00:00 GMT |