Unable to download PDF which is previously working under ControlCenter Product

[kongaravinatha]

Product

Control Center

Page

https://developer.fiserv.com/product/ControlCenter/api/?type=post&path=/v1/statement/pdf&branch=main&version=1.0.0

Description

in this URL : https://developer.fiserv.com/product/ControlCenter/api/?type=post&path=/v1/statement/pdf&branch=main&version=1.0.0

Open the page and execute the Run request for v1/statement/pdf and check if the pdf is being downloaded or not.

BUG : I am seeing the error :

{
"errorCode": 400,
"errorType": "SANDBOX_EXECUTION_ERROR",
"message": "Unable to to execute sandbox call"
}

Expectation : A pdf should be downloaded when we execute the Run Request

Browser

Google Chrome

[russnicoletti]

@kongaravinatha We are investigating the issue. One issue we've found is the example request for that API is missing a comma after the value of the stmtKey field and before the cccStatement field. Fixing this example will not solve the problem but it is a necessary part of solving the problem.

[russnicoletti]

@kongaravinatha Also, please add an appropriate example for Content-Type parameters in the spec, for example application/json where that is appropriate. This was not necessary previously but we are re-architecting part of the system such that for tenants that have their own sandbox server the values of the Content-Type parameters in the spec need to be proper as these values will be sent to your sandbox server. Please let me know if you have any questions.

[kongaravinatha]

@russnicoletti
I assume in the yaml, we already do have those parameters aligned.
Where do we need to add Content-Type parameters exactly?

[russnicoletti]

@kongaravinatha The spec does specify the Content-Type parameters. However, there is no example or default value. When there is no example or default value, the value of the parameter defaults to the type, in this case string. As a result, when the user runs the request, the value of the Content-Type parameter is string, which of course is not valid and results in an error from your sandbox server.

The solution is to provide a default value, for example:

    - name: Content-Type
      in: header
      description: The content type. Valid value (application/json).
      required: true
      schema:
        type: string
        default: 'application/json'