Enter the URL for the OpenAPI specification JSON or YAML file. Alternatively, upload the OpenAPI specification file to the SLDB by clicking the  button. 

Supported file protocols are:

• http://
• https://
• sldb:///

Syntax for file path in SLDB:

• Same project as the Pipeline:
  sldb://<filename>.json
  sldb://<filename>.yaml
  <filename>.json

• Different project:
  sldb://<project_space>/<project>/<filename>.json
  sldb://Docmentation/OpenAPI/openapi.json

  This Snap supports external files referenced in this field and gets the data from the referenced files upon connecting to the file location. For example, $ref: 'reference to definition'

Required. Enter the path defined for the given OpenAPI URL. Alternatively, click the  to retrieve a list of available paths based on the value in the OpenAPI specification field. However, Snap suggestions work only when the OpenAPI specification field's value is not a Pipeline/upstream parameter.

Specify the key name for HTTP Header.

Use this field set to specify additional parameters for the intended operation. Most of these parameters control how you display the output, for example, Pagination interval (seconds) and Maximum pages. Specify each parameter as a separate row. Click  to add a new row.

This field set consists of the following fields:

• Properties
• Values

Select and specify additional parameters for the intended operations upon the endpoint. 

Available options are:

• Has next. Enter an expression that is evaluated with the output document to true or false indicating whether the Snap must get the next page. Depending on the server implementation, the hasNext information is contained in the response headers or entity. The value of this parameter must be expression-enabled. The Snap stops the pagination when this parameter is evaluated to false or the number of pages reaches the Maximum pages parameter value.
• Next URL. Enter an expression that is evaluated with the output document to a URL that the Snap uses to get the next page. Depending on the server implementation, the next page URL information is contained in the response headers or entity. The value of this parameter must be expression-enabled.
• Pagination interval (seconds). The number of seconds for the Snap to wait before attempting to get to the next page.
• Maximum pages. The maximum number of pages to download. Use -1 is for unlimited pagination.
• Enable process array. If the schema of the response entity is expected to be an array as specified in the endpoint’s OpenAPI specification, the Snap parses the array and writes a stream of output documents to the output view without other HTTP response data such as status line or headers. You can also disable this Snap behavior by entering false for this parameter.
• Multipart file content key. The key name used for the file content in the input data and the multipart form-data.
• Multipart filename key. The key name used for the filename in the input data and the multipart form-data.

Enter the values to use for the additional parameters that you specify above.