Welcome to the Atlassian developer community @AlekseiBiriukov,
No.
The options I would recommend instead:
- For other languages (Python & Java), I’ve recommended the style provided by Refit. I find this style strikes the best balance between having a type-safe SDK and being overly coupled to the OpenAPI Spec. Another similar library would be Flurl, which solves many of the same problems with a fluent interface instead of annotations. Flurl is less helpful in manipulating responses with native types.
- Generate a C# client from the OpenAPI spec available for download from the Jira Cloud Platform REST API docs. The official OpenAPI project maintains CSharp Code Generator. Microsoft seems to prefer NSwag because it’s written in .NET with its own CSharp Code Generator. Both would provide a strongly-typed interface to both response & requests. While I haven’t used either library specifically, I have used other generators. They can be very sensitive to problems in the underlying spec, even if you don’t care about that part of the API. And I know there are bugs in our OpenAPI specs.
- Use any general HTTP/REST client lib. I’ve seen many references to RestClient and RestSharp in community posts. These usually leave a lot of JSON handling up to you. However, that might be the case in any of these solutions because Jira Issues aren’t well-typed. The configuration of issue types & custom fields makes issues look a lot more like loosely-typed dictionaries than a well-structured class.