Skip to main content

I am facing some difficulties with integrating your application. Your documentation left me with a few questions regarding creating an OAuth application:

  1. What is a callback URL in the OAuth application registration form? How will it be used, and can it be changed in the future?
  2. If I have multiple environments for my application (e.g., production, staging, dev), do I need to create three different applications with different callback URLs?
  3. My use case for the OAuth application: the user registers on my website, adds their Unbounce account to my site, and can view their works from Unbounce on my site. Could you help me understand how to achieve this? For example, how Zapier integrates with Unbounce.

Thank you for your assistance!

Hi @vasamal, 

I'm happy to help clarify these points for you.

  1. Callback URL in the OAuth Application Registration Form:

    • The callback URL (also known as the redirect URI) is the URL where the authorization server sends the user once they have approved the application. This URL is crucial for the OAuth flow as it receives the authorization code, which is then exchanged for an access token.
    • Yes, the callback URL can be changed in the future. However, it's important to update it in your OAuth provider settings and ensure that your application handles the new URL correctly.

  2. Multiple Environments (Production, Staging, Dev):

    • If you have multiple environments, it is recommended to create separate OAuth applications for each environment. This approach helps isolate the environments and manage different callback URLs without causing conflicts.
    • For example, you might have:
      • Production: https://yourapp.com/callback
      • Staging: https://staging.yourapp.com/callback
      • Development: https://dev.yourapp.com/callback

  3. Integrating with Unbounce:

    • To allow users to register on your website and add their Unbounce account, you'll need to set up an OAuth integration with Unbounce. This involves:

      1. Registering your application with Unbounce and obtaining the client ID and secret.
      2. Implementing the OAuth flow to authenticate users and request access to their Unbounce data.
      3. Using the access token received to make API calls to Unbounce and fetch the user's works.

    • For a detailed example, you can refer to how Zapier integrates with Unbounce:

      1. User Authorization: When a user connects their Unbounce account, they are redirected to Unbounce's authorization page.
      2. Callback Handling: After authorization, the user is redirected back to your specified callback URL with an authorization code.
      3. Token Exchange: Your server exchanges this code for an access token.
      4. API Requests: Using the access token, your server can make authenticated requests to Unbounce's API to fetch the necessary data.

I hope this helps! If you have any further questions or need additional assistance, please feel free to ask.

Hi @Md_Mahinur_Khan 

Thank you so much for your reply! This is just what I needed

Hi @vasamal,

You're very welcome! I'm glad I could help. If you have any other questions or need further assistance, feel free to reach out.

Reply


Terms & ConditionsCookie settings