ART INSTITUTE OF CHICAGO FULL
ART INSTITUTE OF CHICAGO CODE

It can be convenient to use our search endpoint to filter records and retrieve only the fields you need.

That said, we don't mind small-scale scraping of our API. Instead of scraping, please download the data dumps and filter them locally to obtain the data you need. Scraping our API puts undue stress on our systems. The data dumps are meant for backups and analysis. The API is meant for direct integration into websites and applications. Generally, we ask that you avoid extensive scraping of our API. You want to integrate our data into a website or application.Use our API if the following fits your use case: You want to analyze or enhance our data.You want to scrape a large result set (>10,000 records).

ART INSTITUTE OF CHICAGO FULL

You want to have a full copy of our data for archival purposes.

We recommend using the data dumps for scenarios such as the following: If you notice schema discrepancies between the data dumps and the API, or if you need help with using our data dumps, please open an issue (opens new window) in the api-data repo. Since the schema is the same, switching between the two should be relatively straight-forward.

ART INSTITUTE OF CHICAGO CODE

Our intention with this approach is to make it easier to adapt code to draw from the data dumps instead of the API, and vice-versa. Records are grouped by API resource type. The data is dumped in JSON format, with one JSON file per record. As such, they contain the same data as our API, and their schema mirrors that of the API. You can download a dump that contains all of our public data here: When scraping, please use a single thread and self-throttle.Ĭonsider using data dumps instead of scraping our API. When downloading images, use /full/843,/0/default.jpg parameters. Use the fields parameter to tell us exactly what fields you need.īatch detail queries with the multi-id parameter ( ?ids=).īatch search queries with multi-search ( /msearch). Here are some tips that will make your application run faster and/or reduce load on our systems:Ĭache API responses in your system when possible. This is done in part for backwards-compatibility reasons. If a field typically returns an array, we prefer to return an empty array, rather than returning null. If a field that typically returns a string, number, or object is empty for a given record, we return it as null, rather than omitting it. We prefer to always show all fields, even if they are null for the current record: 'date_display' : '', // BAD 'artist_display' : null, // GOOD

Art institute of chicago