Forum Discussion

jsmith141's avatar
jsmith141
New Contributor III
4 years ago

Passing Body Content in Post Snap

Hi,

This is a very novice question, but I am having trouble with a post request snap. This is just to authenticate with the RingCentral platform to receive a token for API consumption. I am able to successfully retrieve an access token when calling the oauth/token endpoint in Postman. The issue arises when I try to move this post call into SnapLogic. The call requires certain parameters to be passed through the body and I am not sure how to duplicate this in SnapLogic post snap. Please see the screenshot of the Postman call Body tab below.

I have created a basic account in SnapLogic to store the username and password and my post snap references that account. I am also aware that the credentials of a basic account can be accessed using the “Account.Username” and Account.Password" of the respective referenced account within the snap.

I am just not sure how to build out the body section in the “x-www-form-urlencoded” format as shown in the screenshot? The error I get back when validating this post snap is just a 400: Bad Request.

Any insight/help that anyone could provide would be greatly appreciated. Please let me know if additional information is needed to provide assistance.

Thanks,
James

48 Replies

  • d_talevski's avatar
    d_talevski
    New Contributor
    4 years ago

    Hi @jsmith141 ,

    When the content type is x-www-form-urlencoded then the format of the body should be the same as the query string:

    parameter1=value1&parameter2=value2

    In SnapLogic you can send the request body in the HTTP entity field of the REST Post snap.
    Example expression:

    “param1=”+encodeURIComponent($param1)+“&param2=”+encodeURIComponent($param2)

    Best Regards,
    Dragan Talevski

    • jsmith141's avatar
      jsmith141
      New Contributor III
      4 years ago

      Hi Dragan,

      Thank you for your reply. I have implemented the encodeURIComponent call as you describe but I am getting the same 400 error. Please see the exact line below…

      “grant_type=”+encodeURIComponent(“password”)+“&username=”+encodeURIComponent(account.username)+“&password=”+encodeURIComponent(account.password)

      I have the Upload body type fields set to “Multipart form-data”. Does this need to be changed, or is there another setting on this snap that may need to be adjusted?

      Thanks,
      James

      • d_talevski's avatar
        d_talevski
        New Contributor
        4 years ago

        @jsmith141 You can try removing the account from the REST Post snap and send the account username and password through pipelines parameters to check if it’s working.

  • ptaylor's avatar
    ptaylor
    Employee
    4 years ago

    I am also aware that the credentials of a basic account can be accessed using the “Account.Username” and Account.Password" of the respective referenced account within the snap.

    I’m not sure what you mean by that. I’m not aware of any way to reference account fields through expressions in the snap.

    Here’s a simple example with no account where the credentials come from the input document.
    REST Post Echo Form URL Encoded_2022_03_09.slp (4.8 KB)

    • jsmith141's avatar
      jsmith141
      New Contributor III
      4 years ago

      Hi Ptaylor,

      Thanks for your reply. please note that these containers should be all lowercase, “account.username” not “Account.Username”. This was a feature that I came across in the community. This is not the exact article that first came across this feature, but it references the same containers. Perhaps it is not available for all account types, or maybe it is in the process of being deprecated?

  • ddellsperger's avatar
    ddellsperger
    Admin
    4 years ago

    I see that you have the extension specified in postman, is that required for your particular instance? If not, you can just use the OAuth2 Account within the REST snap pack as it has a grant type of password that you can use. It seems the only missing item at that point would be the ability to get the endpoint_id back from the request, if that’s an important step, it might be worth looking into the authorization_code flow in their documentation as that seems to not require the additional parameters in the body of the password grant flow. Again, this can be achieved with the REST OAuth2 Account. It also looks like they provide an OpenAPI specification, so you could use the appropriate account type for the Open API Snap to potentially achieve the same thing, assuming you’re able to get it working in the REST OAuth2 Account

    • jsmith141's avatar
      jsmith141
      New Contributor III
      4 years ago

      Thanks for your response. That entry is actually not selected. The extension can be concatenated to the username( a phone number in this case) and passed with the username at that point. That is what I am currently doing in that snapshot you see above.

      I am trying to get an OAuth2 account working in this case. The app in Ring Central does not provide a redirect URL, which if I understand correctly, rules out the option of authorization_code flow. I am trying to get it to authorize using the password flow but I get an error string in a new tab. See below.

      {“response_map”: {“error_list”: [{“message”: “Request from platform.devtest.ringcentral.com returned an error (response code: 400, response: {\n "error" : "invalid_client",\n "errors" : [ {\n "errorCode" : "OAU-123",\n "message" : "Client authentication is required"\n } ],\n "error_description" : "Client authentication is required"\n})”}]}, “http_status_code”: 500}

      Do you know what I might be missing? Again please forgive my lack of knowledge in this area.

      • ddellsperger's avatar
        ddellsperger
        Admin
        4 years ago

        redirect_uri is what is provided for SnapLogic to respond, in this case, it would likely be (in the rest account) https://elastic.snaplogic.com/api/1/rest/admin/oauth2callback/rest which redirects back to the base url for snaplogic to complete the next step of the auth. If you move to openAPI, you’ll replace rest with openapi. The REST OAuth2 Account documentation has it right at the top under Account Settings, it’s quite a bit confusing here because in this case you may not know what a POD is.