Double slash in an event from requests.json

App Platform
, , , ,
1

We developed a custom app with events defined in requests.json:

"events": {
  "onConversationCreate": {
    "handler": "onConversationCreateHandler"
  }
}

However, when the event handlers are triggered by Freshdesk, a double slash suddenly appears after the host. As a result, the request looks like this:

POST //api/v1/webhook/freshdesk/ HTTP/1.1

Example logs:

44.220.48.85 - - [28/Apr/2026:11:19:16 +0000] "POST //api/v1/webhook/freshdesk/ HTTP/1.1" 200 89 "-" "-" "-"
52.23.223.95 - - [28/Apr/2026:11:19:21 +0000] "POST //api/v1/webhook/freshdesk/ HTTP/1.1" 200 89 "-" "-" "-"
3.236.124.24 - - [28/Apr/2026:11:19:27 +0000] "POST //api/v1/webhook/freshdesk HTTP/1.1" 200 5 "-" "-" "-"

We do not have a double slash in the requests.json file, and it shouldn’t be possible to include one because the Freshdesk CLI validates the files before packaging the app.

In our configuration, it looks like this:

"host": "channels-staging.ocdn.cloud",
"path": "/api/v1/webhook/freshdesk"

Our app uses platform version 3.0:

"platform-version": "3.0",
"engines": {
  "node": "24.11.0",
  "fdk": "10.1.1"
}
2

Hi @eugborisov,

The occurrence of a double slash in the request path is often related to how the platform concatenates the host and path variables defined in the requests.json file.

Based on the provided configuration, the following points should be verified:

  • Path Definition: It is recommended to check if the path value begins with a forward slash. If the platform automatically appends a slash after the host, a leading slash in the path attribute (e.g., "/api/v1/...") may result in the observed // format.

  • Trailing Slashes: The host definition should be checked to ensure no trailing slash is present.

  • Server Compatibility: Most modern web servers treat // as a single /. It should be confirmed whether these requests are being rejected or whether the concern is strictly about log formatting.

Regards,
Himanshu

3

Hi @Himanshu_Sharma ,

Thank you for your message.

Just to clarify, when you refer to the “platform,” do you mean Freshdesk? In our case, the webhook URL is triggered on the Freshdesk side.

Regarding the double slashes: the host does not include a trailing slash, and the path must start with a leading slash. Removing the leading slash from the path is not possible, as it would cause validation to fail in the Freshdesk CLI.

For reference, this is how it is defined in our requests.json file:
“host”: “channels-staging.ocdn.cloud”,
“path”: “/api/v1/webhook/freshdesk”

Best regards,

Evgeniy

4

@Himanshu_Sharma hello, any update on this?

5

Hi @eugborisov,

Apologies for the delay in following up on this thread.

“Platform” in this context refers to the underlying Freshworks App Ecosystem (FDK) request-handling service.

Since the requests.json configuration is correctly structured, and the leading slash is mandated by the CLI validation, the unexpected double slash (//) concatenation appears to be an issue with how the platform constructs the final URL for version 3.0 apps.

This behavior has been shared with the engineering team for internal investigation. An update will be provided here as soon as feedback is received.

Regards,
Himanshu