# Create Feedback

Submits Feedback for the VBA application.

Endpoint: POST /feedback
Version: v1
Security: apiKeyAuth, bearerAuth

## Security:

  - `apiKeyAuth` (unknown)
    apiKey in header x-api-key

  - `bearerAuth` (unknown)
    http bearer JWT

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Request fields (application/json):

  - `screen` (string, required)
    Represents the specific screen from which feedback is submitted. This attribute serves as a contextual identifier, aiding in the precise location of user feedback within the application.

  - `issue_Type` (string, required)
    Categorizes the type of the issue or feedback being reported. It provides valuable context regarding the specific problem or concern encountered.

  - `description` (string, required)
    Provides a textual representation of the feedback or issue reported. It allows users to elaborate on their experiences, providing essential details, observations, or suggestions related to the reported concern.

  - `logs` (string)
    Refers to any relevant log files or records associated with the reported issue or feedback. These logs provide valuable technical data and context, aiding in the investigation and resolution of complex issues.

## Response 202:

  - `202` (unknown)
    Accepted

## Response 202 fields (application/json):

  - `data` (string)

  - `error` (object)

  - `error.detail` (string)
    A human-readable explanation specific to this occurrence of the problem.

  - `error.instance` (string)
    A URI reference that identifies the specific occurrence of the problem.It may
or may not yield further information if dereferenced.

  - `error.status` (integer)
    The HTTP status code([RFC7231], Section 6) generated by the origin server for
this occurrence of the problem.

  - `error.title` (string)
    A short, human-readable summary of the problem type.It SHOULD NOT change from
occurrence to occurrence of the problem, except for purposes of localization(e.g.,
using proactive content negotiation; see[RFC7231], Section 3.4).

  - `error.type` (string)
    A URI reference [RFC3986] that identifies the problem type. This specification
encourages that, when dereferenced, it provide human-readable documentation for
the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member
is not present, its value is assumed to be "about:blank".

  - `debug` (object)

  - `debug.activityID` (string, required)

## Response 401:

  - `401` (unknown)
    Unauthorized

## Response 403:

  - `403` (unknown)
    Forbidden. The x-api-key header is missing or not valid. The API gateway sends this response, not VBAPI, so the body is not the VBAPI envelope; see Errors and troubleshooting.

## Response 429:

  - `429` (unknown)
    Too many requests. The limit is 25 requests per second sustained, with bursts up to 50, per API key. Wait and retry with exponential backoff and jitter.