SpaceX-API VS Strapi

SpaceX REST API

This is what i meant by that explanation. In this project we will make a request to a SpaceX API and the results we want from the huge chunk of data we will be receiving from the API are: id of type string, flight_number of type int, name and details of type string and success of type boolean.

This is a cool api, spacex posts all of their flight info on here, and there's no auth which might make it easier for testing/learning: https://github.com/r-spacex/SpaceX-API

I like this unofficial SpaceX API. I am using it in examples for API-related tutorials and to train less experience technical personnel. Works like a charm so far :)

5. SpaceX API

Here's one that I've made showing all the active boosters using the unofficial SpaceX API

To display the next scheduled launch date, we have to fetch our data from the API. Therefore we will use the following API Documentation spacexdata.com API.

Strapi provides a centralized data managing platform. This makes it easier to organize, update, and maintain the FAQ data. It also automatically generates a RESTful API for accessing the content stored in its database.

https://prisma.io is popular as I understand it. I've been trying out https://strapi.io the last week and am thoroughly impressed.

They both do much more than build queries. One big thing both do is automate database migration calculations. Strapi goes further and gives you a CMS and admin UI on top, as well as doing a lot more of the complex query building from a json object. Both still require a fundamental understanding of the data model and SQL

As of April 2024, Strapi's GitHub repository has garnered 59.7k stars and 7.5k forks, showcasing its widespread adoption. The project has also secured a substantial $45+ million in funding, cementing its position as a prominent player in the headless CMS space.

const pages = await client.GET("/pages", { params: { query: { filters: { // @ts-ignore - openapi generated from strapi results in Record // https://github.com/strapi/strapi/issues/19644 path: { $eq: path, }, }, // @ts-ignore populate: { blocks: { populate: "*" }, }, }, }, });

On a side note. Where do all these endpoints come from? Strapi is open source. We can read the source code. All these endpoint come from the Users and permissions plugin. So, if we go to Strapi on github and browse around the files a bit eventually you will find the auth.js file that contains all of the routes. You can also find the Strapi controllers in there if you're interested.

Strapi

Strapi: The Code Anarchist

Strapi - Open source Node.js Headless CMS 🚀