Webhook Handler for Windows Server 2022 -- 2

En curso Publicado hace 8 meses Pagado a la entrega
En curso Pagado a la entrega

FINISH THIS PROJECT

Files have been made - Although am not sure how complete - Hasn't been implemented on server or tested.

Need someone who can verify the work. Teamview into implement on server and test.

I think this should take less than an hour to complete.

Project Description:

I am looking for a skilled developer to create a webhook handler for Windows Server 2022. The handler should be written in C# and be capable of accepting REST API webhooks.

Requirements:

- Proficiency in C# programming language

- Experience in developing webhook handlers

- Familiarity with Windows Server 2022 environment

Skills and Experience:

- Strong knowledge of C# programming language and .NET framework

- Experience in working with REST APIs

- Familiarity with Windows Server 2022 environment

- Ability to create efficient and reliable webhook handlers

- Strong problem-solving skills

This project does not require authentication. The main goal is to create a webhook handler that can process incoming REST API webhooks efficiently. If you have the required skills and experience, please submit your proposal.

To process this JSON payload effectively, the webhook handler should be designed to handle the specific fields present in the payload. The handler will need to access each field and its corresponding value to construct the CSV files as per the project requirements.

Here's a summary of some of the key fields present in the payload:

Alert: Indicates the type of alert, in this case, "Entered Position."

Copy Path: The path of the copied value, represented with bullet points in the payload example.

Copy Value: The value copied.

Close: Closing price, represented as 15846.75.

Direction: Direction of the position, e.g., "Short."

Entry: Entry price, represented as 15847.

Exchange: Exchange information, e.g., "CME_MINI:NQ1!"

Indicator: Indicator used, e.g., "Harmonic Pattern."

Instrument: Trading instrument, e.g., "NQ1!"

Loss in Pips: Loss in pips, represented as 131.

Pattern: The pattern identified, e.g., "Double Top."

Pattern ID: Unique identifier for the pattern.

Profit 1 in Pips: Profit target 1 in pips, represented as 51.8.

Profit 2 in Pips: Profit target 2 in pips, represented as 89.5.

SL: Stop-loss price, represented as 15879.75.

T1: Target 1 price, represented as 15834.

T2: Target 2 price, represented as 15824.5.

TV-Time: Time of the TV (Television) data, represented as 15:29:49.

TimeFrame: The timeframe, e.g., 1.

The webhook handler needs to extract these fields and their respective values from the JSON payload and use them to create the CSV files. The CSV files will likely contain rows of data, with each row representing an alert or position and the associated information.

The exact CSV file format will depend on the specific requirements and the intended use of the CSV files. The handler will be responsible for organizing the extracted data into the appropriate CSV format, which may include column headers and rows with corresponding values.

It's important to ensure that the webhook handler is robust and handles various edge cases, such as handling missing or invalid fields in the JSON payload and gracefully handling any errors that may occur during processing. Additionally, proper validation and error handling should be implemented to guarantee the accuracy and reliability of the generated CSV files.

PHP .NET Programación en C# Arquitectura de software ASP.NET

Nº del proyecto: #37061824

Sobre el proyecto

1 propuesta Proyecto remoto Activo hace 8 meses