Thank you for this tutorial Alex, it's straight forward and easy to follow. I did not tried yet their API but it will be useful to dynamically nourish my website telling what i'm working on. You gained a new follower :)
Thank you for this tutorial. Did you try to get a file from Notion database ? I got in the react app the files with its url and expiry_time, but impossible to access to the url destination with the app.
Because doing so directly on the front end would require you to expose your Notion integration secret to the client. Even with "read only" permissions token, although the risk is minimal, anyone could still take your token and create their own app reading your DBs and impact your rate limits.
That's a fantastic way to do it. Most devs I know who had success were driven by having a specific project in mind and learning each piece to to get there, rather than just learning for its own sake. One thing I will say to keep in mind though is that the Notion API is constantly evolving and in active development. I've seen cases where the documentation wasn't keeping up with the actual responses/shape of the API. If just starting, maybe worth practicing on a simple stable one as a stepping stone briefly to get comfortable with the basics then moving onto the Notion APi next (unless you have already). I still think it's great to learn on, and as long as you're prepared for that possibility you're in great shape. Get comfortable checking the network response tab and looking at the data directly as an additional sanity check to what the documentation (or my videos) tell you Good luck!
Thank you for this tutorial Alex, it's straight forward and easy to follow. I did not tried yet their API but it will be useful to dynamically nourish my website telling what i'm working on.
You gained a new follower :)
Glad it helped!
Love your videos! Thank you 💜🔥🙏🏾
Thank you for this tutorial.
Did you try to get a file from Notion database ?
I got in the react app the files with its url and expiry_time, but impossible to access to the url destination with the app.
Im confused, why aren't you just directly calling the Notion API? Why do you need a server?
Because doing so directly on the front end would require you to expose your Notion integration secret to the client.
Even with "read only" permissions token, although the risk is minimal, anyone could still take your token and create their own app reading your DBs and impact your rate limits.
@@AlexEagleson also cors does not let you hit the api from your frontend.
I use notion for my RPG game I run as the DM. Trying to change careers and this may be a good way of getting used to using dbs!
That's a fantastic way to do it. Most devs I know who had success were driven by having a specific project in mind and learning each piece to to get there, rather than just learning for its own sake.
One thing I will say to keep in mind though is that the Notion API is constantly evolving and in active development. I've seen cases where the documentation wasn't keeping up with the actual responses/shape of the API. If just starting, maybe worth practicing on a simple stable one as a stepping stone briefly to get comfortable with the basics then moving onto the Notion APi next (unless you have already).
I still think it's great to learn on, and as long as you're prepared for that possibility you're in great shape. Get comfortable checking the network response tab and looking at the data directly as an additional sanity check to what the documentation (or my videos) tell you
Good luck!
@@AlexEagleson Thanks, man! Good luck with the little one. I've got two, one six and one eleven. It's a ride!
Muito obrigado!