Noname

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 fetch specific issue allows you to retrieve the details of a specific issue by providing the corresponding id 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 id string required unique identifier output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] 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 id string required unique identifier output parameter type description status code number http status code of the response reason string response reason phrase example \[ { "status code" 200, "response headers" { "content type" "application/json", "date" "thu, 01 jan 2024 00 00 00 gmt" }, "reason" "ok" } ] 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