Thank you for this video. It's the only one I see on youtube that explains this. Could you do another one on how to follow up on this by extracting data from the API?
Thanks for the comment. I’ve seen several request to do follow ups. I’m in the process of working on some but not sure when I will be able to finish them 😅 But! They are on the way!
@@hxlng Give me a few more days I have something in the works that will be a step up. I was trying to find ways to keep the code super simple and vanilla but decided to bring in a framework to help out.
Without full trace I can’t give a thorough answer but shooting in the dark, try down grading your version of python (3.8 or 3.7) try googling the name of the package that failed with the error description, might have a easy fix.
First, thanks for watching! Second, depending on the issuer, tokens are normally configured to expire at some interval and they will usually provide some sort of contract/guidelines for refreshing that token (without having to re-authenticate). This information is normally found in the resource providers docs. It should be possible code a helper/refresher function and kick it off after checking the token or on failure. By design the tokens aren't really suppose to be reusable. Here is a short article that helps explain the design principles from the point of view of the issuer. www.oauth.com/oauth2-servers/access-tokens/access-token-lifetime/
Looks like indeed requires some additional scopes to refresh tokens, check out the docs here: developer.indeed.com/docs/authorization/3-legged-oauth#refresh-your-token And the requests-oauthlib OAuth2Session object has a method, refresh_token(), that will probably get you going in the right direction here.
@@tekksparrowprograms Found the way to save the token and then reuse. But i got a bug for the token_refresh function but could change the original module files and it works now yes! And I was using it for an other application but the example worked to get started thx!
Hi, can you please make a video or guide how to do job posting using indeed api. I have completed authorization and have bearer token but every time i send the jobposting api it shows 403 forbidden.
If you are positive you have a good token here are some things I would check when getting a 403: double check the api endpoint, make sure it matches exactly, don't forget to check the API versioning, sometimes resource providers manager multiple APIs during updates/migration/etc... Another thing it COULD be is the scope that is registered with your app, make sure you have the proper scope, I would imagine making requests "out-of-scope" could result in a 403. I would check the headers, just console print or breakpoint before the get request is sent and look into the OAuth2Session and see if all the properties look ok (it will have thinks like token, headers, etc.) GLHF
Thank you so much sir for this video , Will you be able to make video on Indeed Oauth API using django Question : actually i am working on production , How to check this API response on postman ? i am facing issue that how to implement it
I'm planning on uploading one using the Flask framework. I think you might be able to derivate some solutions from it even being a different framework.
Thank you for this video. It's the only one I see on youtube that explains this. Could you do another one on how to follow up on this by extracting data from the API?
Thanks for the comment. I’ve seen several request to do follow ups. I’m in the process of working on some but not sure when I will be able to finish them 😅 But! They are on the way!
@@tekksparrowprograms do you still plan on making a follow up? Would be very helpful!
@@hxlng Give me a few more days I have something in the works that will be a step up. I was trying to find ways to keep the code super simple and vanilla but decided to bring in a framework to help out.
is it possible to post job offers with indeed api?
lots good stuff in the docs docs.indeed.com/dev/reference/jobposting
@@tekksparrowprograms thank you !! 👻👻 Can i only Ask if there is some paid membership in need to post job offers though their API? Or its costless
Failing requirements to build the wheel. Wheel 'six' is giving error. I'm using windows
Without full trace I can’t give a thorough answer but shooting in the dark, try down grading your version of python (3.8 or 3.7) try googling the name of the package that failed with the error description, might have a easy fix.
Thanks for the video whaty is the best way to save that token for reuse?
First, thanks for watching! Second, depending on the issuer, tokens are normally configured to expire at some interval and they will usually provide some sort of contract/guidelines for refreshing that token (without having to re-authenticate). This information is normally found in the resource providers docs. It should be possible code a helper/refresher function and kick it off after checking the token or on failure.
By design the tokens aren't really suppose to be reusable. Here is a short article that helps explain the design principles from the point of view of the issuer. www.oauth.com/oauth2-servers/access-tokens/access-token-lifetime/
Looks like indeed requires some additional scopes to refresh tokens, check out the docs here: developer.indeed.com/docs/authorization/3-legged-oauth#refresh-your-token
And the requests-oauthlib OAuth2Session object has a method, refresh_token(), that will probably get you going in the right direction here.
@@tekksparrowprograms Found the way to save the token and then reuse. But i got a bug for the token_refresh function but could change the original module files and it works now yes!
And I was using it for an other application but the example worked to get started thx!
@@kamperzoid glad you were able to work something out. Feel free to raise a PR for the issue you found.
Hi, can you please make a video or guide how to do job posting using indeed api. I have completed authorization and have bearer token but every time i send the jobposting api it shows 403 forbidden.
If you are positive you have a good token here are some things I would check when getting a 403: double check the api endpoint, make sure it matches exactly, don't forget to check the API versioning, sometimes resource providers manager multiple APIs during updates/migration/etc... Another thing it COULD be is the scope that is registered with your app, make sure you have the proper scope, I would imagine making requests "out-of-scope" could result in a 403. I would check the headers, just console print or breakpoint before the get request is sent and look into the OAuth2Session and see if all the properties look ok (it will have thinks like token, headers, etc.) GLHF
Thank you so much sir for this video , Will you be able to make video on Indeed Oauth API using django
Question : actually i am working on production , How to check this API response on postman ? i am facing issue that how to implement it
I'm planning on uploading one using the Flask framework. I think you might be able to derivate some solutions from it even being a different framework.