Colon in endpoint url

Options
Vikrant -1766326
Vikrant -1766326 Member ✭
in ? Working with APIs
I am trying to set up a webhook but the source (a Payment Gateway - PayU) is not accepting a webhook with ":" in its url. Any suggestions?
· Share on Twitter

Comments

  • Steve Stava
    Steve Stava Member ✭
    Options
    It might not need the "https://". Try using your Xano api url without "https://" 
    · Share on Twitter
  • Vikrant -1766326
    Vikrant -1766326 Member ✭
    Options
    There is another one actually, just after the text API, between the asterisks below:

    https://xmfp-jqys-l9nm.n7.xano.io/*api:TcrCOaZG*/orderitemsUPDATEPRICE_1
    · Share on Twitter
  • Steve Stava
    Steve Stava Member ✭
    Options
    Good call! That does make it a little more complicated 😅
    · Share on Twitter
  • Steve Stava
    Steve Stava Member ✭
    Options
    I was hopeful to have an easy win on this...I think we need to ping  since this looks like a URL edit issue on the PayU side 😬
    · Share on Twitter
  • Sean Montgomery
    Sean Montgomery Administrator

    ADMIN
    Options
     I would open a support ticket with them. Colons are valid characters in the url path.
    · Share on Twitter
  • Vikrant -1766326
    Vikrant -1766326 Member ✭
    Options
    Thanks, Sean. Btw, I had tried %3A - no luck. For now, I am thinking of using webhook.site as the bridge
    · Share on Twitter
  • Ferdi Boxman
    Ferdi Boxman Member ✭
    Options

    When i did that i received this message back:

    "The : after /api is what is causing the issue.
    The use of a colon (:) after the "/api" segment in a URL is not a valid approach in a standard URL.


    According to the RFC specifications for URLs, the colon character has a reserved meaning in a URL, and is typically used to indicate a scheme, such as "https://" or "ftp://". Using a colon in any other context in a URL, such as in the middle of a path segment like "/api:VWn65kol", would be considered non-standard.


    While it's possible that some web servers or APIs may use this non-standard syntax for their own URLs, it's generally recommended to follow standard URL conventions whenever possible to ensure maximum compatibility with web browsers and other tools that work with URLs, which is what we currently use to validate our URLs."

    :(

    · Share on Twitter
  • Juraj-QikBuild
    Juraj-QikBuild Member ✭
    Options

    By the way, I have the same issue with PandaDoc - it doesn't support colon in URL…
    Although I understand it is a valid character in URLs, clearly it's not so standard and some 3rd party services might have an issue with that.

    · Share on Twitter
  • Nathan Cox
    Nathan Cox Member ✭
    Options

    I have this issue with the Fireflies API, I'm trying to use Xano for my webhook and it gets rejected as invalid. Does anyone have any further insight into this in terms of what can be done? I might not be able to use Xano for this project otherwise.

    · Share on Twitter

Categories