[Mismatch between API response and API specification] Missing "requestUrl" property in "metadata" object

[apibugsreporting]

Bug Description

The following API request obtains a response that contains inconsistencies with respect to the API specification.

General Information

Please include the following general information about the issue and list any additional steps needed to reproduce the bug.

• Version of the ohsome API [e.g. 1.5.0]
  • 1.6.1
• Which API instance was requested [e.g. remote instance at https://api.ohsome.org/v1, local instance with an h2 file or connected to the cluster, etc.]
  • Remote instance at https://api.ohsome.org/v1
• Affected endpoint(s) [e.g. /contributions/count]
  • /elements/perimeter/density/groupBy/boundary/groupBy/tag
• URL of your request (and request body if applicable)
  • https://api.ohsome.org/v1/elements/perimeter/density/groupBy/boundary/groupBy/tag?types=way%2Crelation&groupByKey=building&showMetadata=true&time=2015-08-16&timeout=56&bcircles=EB%3A8.7280%2C49.40533%2C46%7CM%3A8.712%2C49.4157%2C2
• Used HTTP method [GET or POST]
  • POST
• Utilized tool/library for the request [e.g. cURL, Postman, ohsome-py, etc.]
  • RESTest

Expected Behaviour

The response should contain the property "requestUrl" in the "metadata" object, which is defined as "required" in the API specification.

Surprisingly, this property is present when making a GET request, but not when making a POST request.

The OpenAPI specification I am referring to is available at:

• [UI] https://api.ohsome.org/v1/swagger-ui.html
• [JSON] https://api.ohsome.org/v1/docs?group=Data%20Aggregation

Further Information

Error Messages, Logs, Screenshots

See attached screenshot.

Additional Information

A test report revealing this issue is available at the following URL (it might take some time to load):

• http://apitesting.ddns.net/fse2022/restest/target/allure-reports/ohsome__r_rt_custom/#categories/3ca717b43fa7843ff86d06df1715634d/320dd8795d7ba343/

Screenshot