Advertising. No advertising or sponsorship of any kind may appear on or be associated with any App (unless included in the Content made available by Marvel).
No Charge. All Apps must be offered free of charge to download or otherwise access and may not contain any in-App purchase features or any other method of monetization, unless approved in writing by Marvel pursuant to a separate written agreement as described below.
If you are interested in creating an App that is paid and/or contains monetization features, please contact us at Marvel-api-help@marvel.com to discuss a potential business relationship. All for-profit Apps must be pre-approved in writing by Marvel (such approval to be granted or withheld in Marvel's sole discretion). To the extent any for-profit Apps are approved in writing by Marvel (in its sole discretion), you will be solely responsible for any and all taxes due in connection with the distribution of such App in any territory.
It's a great go-to for an API that provides relatable, recognizable data for a demo, class, or darn near anything else you build that doesn't need selling.
If I was still teaching I could see myself using it in a class, as a demo. One of the hardest things to come up with is good data, and enough of it, to keep students entertained with their assignments.
yeah, until you build it into a product that is used by developers and then when the Marvel API is down you can't work.
Looking at you, Elastic. Whatever shithead developer decided that was a good idea should be fired immediately. ESVM is the worst product you've ever made.
In the case of using an API to demonstrate how to use an API, the fact it might be unavailable is a feature. Waaaaaay too many developers write code that assumes a service will always be up.
I've written an extensive reading list manager using the marvel API which I use personally. It's only a day or so of development from being publicly usable, and would really improve the experience of Marvel Unlimited for a lot of people.
This is why it will probably never be public. Why bother when I would have to cover all the hosting costs myself?
Back in 2005ish, I worked for the digital agency that built and managed all of Campbells Kitchen's online properties, including the Campbells Kitchen recipe database. It might seem trivial now, but at the time it was at least a few years of its time in terms of using the power of databased driven webapps.
I also personally built the first ever CSS-based layout site for Campbells - it was the marketing site for V8 Juice. Up until that point, everything was still built with tables holding sliced images.
At the same time, the internal computers at Campbells corporate offices ran IE5.5, which had terrible CSS support.
So I literally built two versions of the site - one that would pass muster on their outdated internal computers, and another would drag them into the era of modern layouts and accessibility.
I learned SO MUCH working on those sites.
It looks like the current CK website has been turned into a Wordpress site so I assumed my original work is long gone, but it's very cool to see the legacy of Campbells Kitchen database I worked on kicking as an API.
It's cute, but needs updated for a security vulnerability in jQuery, and I need to dig in and see why the mocha test for Absorbing Man got borked... although y'all are welcome to submit PRs if you're still looking for Hacktoberfest credits.
The README contains some of the oddities I found in the API, like some search types are more reliable than others, everyone eventually teams up with Iron Man or Wolvie, and the data is pretty incomplete (which makes sense if you have 79 years worth of data to compile from printed media).
* EDIT * - I've done the cardinal sin of leaving my API keys in the project. Marvel doesn't currently give you a way to generate new keys (that I could find), so enjoy while you can, but you should probably sign up your own account once my keys start hitting their API limit.
That reminds me of a project I've always wanted to do but keep putting on the backburner: for a while now, I've been wanting to scrape the Unofficial Handbook of Marvel Comics Creators (UHBMCC) [0] and turn it into an actual database that I can run arbitrary queries on instead of just a collection of flat files (it's a very well-put-together collection of flat files, though). Fortunately they provide an offline version (in the form of CAB files of all things!) so I'd be able to do everything without hammering their server.
IMO, when it comes to Marvel comics, they're a much more useful resource than even the GCD (and part of this is their UI: it may be dated, but putting all the information for a series on one page is ten times better than the GCD's issue-by-issue interface).
(so, several years ago I did do some scraping of a very old version of the UHBMCC, but it's really outdated, I used some awful scraping tools, and I just stored everything in pickled Python objects rather than a database... if I were to start the project up again, I'd want to do it right from the start)
Or he could alter his own brain so as to no longer care about overpopulation. For that, though, he doesn’t need the reality gem, he just needs the whiskey stone.
In fact, they're still using Swagger 1.0[0] from 2011 which wasn't even formally specified, and currently-available copies of the spec[1] had to be unearthed from the wayback machine.
I can't seem to get back Image result for a character. I want a way to see all the different art for one character.
Anyone manage to get back multiple Image results for a character?
This would have been a perfect use-case for an RDF store. But of course, the world has moved into different directions, so we get a rate-limited web-api instead.
What do you all think of their documentation? I don't have a specific reason for asking, other than that I'm a technical writer and this is a good opportunity to "pick your brains" [1] as they say...
A cool use case would be if they open sourced their designs for use in prototypes - it would be super compelling to pitch an app with Iron Man or Captain America as the central user.
Advertising. No advertising or sponsorship of any kind may appear on or be associated with any App (unless included in the Content made available by Marvel).
No Charge. All Apps must be offered free of charge to download or otherwise access and may not contain any in-App purchase features or any other method of monetization, unless approved in writing by Marvel pursuant to a separate written agreement as described below.
If you are interested in creating an App that is paid and/or contains monetization features, please contact us at Marvel-api-help@marvel.com to discuss a potential business relationship. All for-profit Apps must be pre-approved in writing by Marvel (such approval to be granted or withheld in Marvel's sole discretion). To the extent any for-profit Apps are approved in writing by Marvel (in its sole discretion), you will be solely responsible for any and all taxes due in connection with the distribution of such App in any territory.