Skip to main content

I'm trying to access the LucidChart API via the following documentation:


https://developer.lucid.co/api/v1/#overview


I'm using the OAuth 2.0 client. I obtained a Client ID and Client Secret. What is not clear to me is that the App Registration step is the section around the URI and what needs to be done to fill out. Below are the steps in the API documentation.


App registration



Note: Registering a new application requires Team Admin permissions for the Lucid account.


To set up an app to use OAuth 2.0 perform the following steps:



  1. Obtain an OAuth 2.0 client ID and client secret from the account's Lucid team administration page.

  2. Register at least one redirect URI on that page. Lucid will redirect the user to this location once they have granted access. This should be a URL that the app controls. Lucid will append the authorization code to the URL in the code query parameter.


Test redirect URI

As a service Lucid provides a redirect uri that can be used to allow the user to copy the authorization code to the clipboard.


To use it register the redirect URI:


https://lucid.app/oauth2/clients/{client id}/redirect


When this redirect URI is used and a user grants access to the app Lucid will redirect the user to a page on our site where they can view and copy the authorization code.



 


 

Hi Chirag thank you for contributing to the Lucid Community! We will follow-up tomorrow with a response to your question.


Thank you in advance for your help and patience!


hey Richard just following up to see if you had an update? thanks!


Hi Chirag thank you for following up. We've responded to your question directly in the Support ticket you submitted. 


Just modify the redirect Uri to your Web application.


Hope that helps


Thanks @michel l!


For any future viewers of this thread - here's a breakdown of the steps in our documentation:




  1. Obtain Client ID and Client Secret: You've already obtained these from your Lucid team administration page which is great.




  2. Register Redirect URI: This step is crucial. You need to specify where Lucid should redirect the user after they grant access. This should be a URL controlled by your app. Lucid will append the authorization code to the URL as a query parameter called code. For example if your app's URL is https://example.com the redirect URI could be https://example.com/auth-callback.




  3. Test Redirect URI: Lucid offers a convenient redirect URI for testing purposes. You can register it as follows:



    • Redirect URI: https://lucid.app/oauth2/clients/{client id}/redirect


    When you use this redirect URI and a user grants access to your app Lucid will redirect them to a page on their site where they can view and copy the authorization code.




Make sure that your app's logic is set up to capture the code parameter from the redirect URL and use it to complete the OAuth 2.0 flow. If you have any more questions or need further assistance feel free to ask! Good luck with your Lucid API integration. 🚀

If you're looking for support using Lucid's Public APIs head over to the Lucid for Developers Community! We're here to help.


​@Richard Udell I am getting the “no valid scopes available” error but I have set the scope in the request for code url to account.user which I found on the list of scopes in the documentation, https://developer.lucid.co/reference/access-scopes. Does my app need permission to the scopes before creating the code?


Hi ​@Amanda.DeLeo!

 

Does my app need permission to the scopes before creating the code?

Yes! The authorization URL used to generate the authorization code must include the scopes you’d like to have in your OAuth2 token.

 

To make sure I’m fully grasping the issue, can you please share your authorization URL and the specific endpoint you’re requesting?


​@Richard Udell I was using the wrong url,

 

versus

 

Once I switched to the correct url it worked. Thanks for getting back to me!


I’m glad to hear that! Thanks for reporting back the solution. Don’t hesitate to reach out if anything else comes up.


Reply