paulhallett

Good ol' scraping from websites like wookiepedia.

And watching lots and lots of Star Wars.

I have the blurays, so I should be in for a fun experience whilst collecting the nitty gritty data.

So RESTfully, I think this is normal. You should be able to call a resource and then be fed back all of those resources (usually paginated to say, 20 per request).

It will have this style of lookup.

PokeAPI is getting an update - http://phalt.co/if-you-have-data-they-will-consume-it/

and it will have better fuzzy matching.

Ah, you didn't see the film_id & episode_id reference in the second example?

:D My other API for Pokémon is also great for demos and teaching APIs - http://pokeapi.co

Check the bottom of the page ;)

We'll have episode VII details as and when it gets released.

The data is being scraped from sources online and by watching the films about a thousand times.

As the data is already available freely elsewhere, I won't be charging or keeping the data, I'll provide it just like I do on http://pokeapi.co

Ah thanks! It would be far more exciting if it was the weapon though...

I guess the main reason is that data dumps are sometimes hard to sift through, can become inconsistent (if there are multiple copies) and because from my experience, if you provide an API for something, someone will use it. On the flip side: I've found that often people have always asked "why isn't there an API for that?"

And of course, you can easily get a data dump from this by just cURLing all the resources and storing them :)

This is awesome, and another great example that "If you provide data, people will consume it"!

Please do :D

As well as ID, we'll do some fuzzy matching on the URLs as well, so

GET /api/vehicle/t-65-x-wing

and

GET /api/planets/mustafar

will also work

ETA is end of January :)

Good point. I set the URL config to catch all URLs and redirect back to the home page (anticipating people would try the API).

Once things die down I'll push up an update. Getting a heavy bit of traffic right now.

Good spot!

We're working on it, sorry!

Hi Mike, this is Paul, I am making this API too :D

Hey! Thanks. I made the Pokémon API as well - http://pokeapi.co

The backend on that is Django. I might stick with what I know, or build SWAPI in Go. At the moment, we're still very early stage, so we can choose soon.

Congratulations Tom. This trend of crowdfunding development for Django and Python projects should be copied by other communities. It's amazing how much high quality work is coming out of it.