medium-api-docs VS tokens

For more Reference you can check this API documentation of Medium Here.

Figure out why the Medium API is not working!! According to their site their API has been deprecated so even after reviewing with Allen the whole code, I keep getting an error that my AuthorId is wrong. We believe it's a problem on their side but I still want it to work.

More Information regarding the medium.com api: https://github.com/Medium/medium-api-docs

We will be using Medium's REST API for this part. You can find the documentation here.

Medium's API does not support such a use case so you'll have to hire someone on Fiverr to write a custom script to do that

Like Dev.to, Medium also has REST API to create posts. In this tutorial, we are going to work with /posts endpoint to create a new blog post.

There is some documentation on Medium API, we can even post to a Publication, that shall be created in future. Also the cover images can be posted on medium, it is not currently done but that can again be a #TODO. The tags are not rendered on Medium yet with the script. The way we can parse strings is limited in BASH, so this might still be a doable thing later. Most of the checkboxes are ticked like title, subtitle, cover-image, canonical url, and importantly the content.

Okay so today's post is actually kind of fun. As you probably don't know, Medium doesn't have a proper fetch API. They only have a publishing API which makes sense as they want to be own the reading experience, not just the publishing. So, if you want to show your Medium posts on your site, you'll need to do a bit of work.

Documentation - https://github.com/Medium/medium-api-docs

Click on your profile in the top right corner > Settings > Developer settings, or visit: https://github.com/settings/tokens.

First of all, you need to generate a new GitHub Token. You can generate a token in your GitHub account settings at https://github.com/settings/tokens. Make sure to add the ‘read:packages’ scope to your token.

First, generate the GitHub token here.

Environment Variables Create a file .env in the root folder and add your own github api token as below

Go to the Personal access tokens area in the Developer settings of your GitHub profile and click Generate new token.

Versioning The initial step in this workflow involves generating version numbers based on git tag numbers. To access repository information, it's necessary to include a GitHub token in the secrets. You can create a GitHub token by following this link. Please keep in mind that secret names cannot start with the term GITHUB. For instance, you might save your GitHub token as TOKEN_GITHUB.

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

Generate a classic PAT (personal access token) from Github with repo and admin:org scopes at least.

YOUR_TOKEN="no_token_for_you" # IMPORTANT: your Github API access key, make one at "https://github.com/settings/tokens"

You should click on that and then you will see Tokens (classic) which will bring you to https://github.com/settings/tokens