forked from microsoft/workshop-library
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
100 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -4,15 +4,15 @@ | |
|
||
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). | ||
|
||
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below. | ||
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below. | ||
|
||
## Reporting Security Issues | ||
|
||
**Please do not report security vulnerabilities through public GitHub issues.** | ||
|
||
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report). | ||
|
||
If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc). | ||
If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/msrc/pgp-key-msrc). | ||
|
||
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc). | ||
|
||
|
@@ -36,6 +36,6 @@ We prefer all communications to be in English. | |
|
||
## Policy | ||
|
||
Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd). | ||
Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/msrc/cvd). | ||
|
||
<!-- END MICROSOFT SECURITY.MD BLOCK --> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,69 @@ | ||
# Explore the art world by using RESTful APIs | ||
|
||
## Module Source | ||
|
||
[Explore the art world by using RESTful APIs](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/?WT.mc_id=academic-56423-jelooper) | ||
|
||
## Goals | ||
|
||
In this workshop, you will learn the basics of REST APIs, a way to securely query a datasource from an external source. Using Museum APIs, you will discover interesting art via API queries. | ||
|
||
| **Goal** | Description | | ||
| ----------------------------- | --------------------------------------------------------------------- | | ||
| **What will you learn** | Explore the art world by using RESTful APIs | | ||
| **What you'll need** | A modern web browser and an internet connection | | ||
| **Duration** | 20 minutes | | ||
| **Slides** | [slides](./slides.pptx) | | ||
|
||
## Video | ||
|
||
coming soon! | ||
|
||
## What you will learn | ||
|
||
You're a web developer with a passion for the art world. You'd love to create a web page to showcase examples of art through the ages. But you're not sure about the best way to get images of art for your web page. That's where APIs come in! In this module, you'll learn the basics of APIs that help you get images of artwork made public by museums around the world. | ||
|
||
In this workshop, you'll learn about: | ||
|
||
- RESTful APIs | ||
- Strategies to connect to an external API | ||
- Two different museum APIs and how to connect to them using authentication | ||
|
||
## Introduction to RESTful APIs | ||
|
||
Read about RESTful APIs [in this introduction](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/2-what-is-api/?WT.mc_id=academic-56423-jelooper). | ||
|
||
## Query the Metropolitan Museum API | ||
|
||
A great API to query to discover the shape of its data structures as well as its collections is the Metropolitan Museum API from New York. [Let's query it](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/4-query-met-api?/?WT.mc_id=academic-56423-jelooper)! | ||
|
||
## Learn about Authentication Strategies | ||
|
||
While some APIs are open and don't require authentication, many do. Learn more about authentication strategies [in this introduction](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/5-authentication-strategies?WT.mc_id=academic-56423-jelooper). | ||
|
||
## Query the Cooper Hewitt API | ||
|
||
Now that you know how to get an authentication key, practice by [querying another museum api](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/6-query-cooper-hewitt-api/?WT.mc_id=academic-56423-jelooper), the Cooper Hewitt Museum of Art. | ||
|
||
## Handle responses | ||
|
||
[Handle API responses](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/7-handle-responses?WT.mc_id=academic-56423-jelooper) by understanding status codes and what they indicate. | ||
|
||
## Test your knowledge! | ||
|
||
[Take a quiz](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/9-knowledge-check/?WT.mc_id=academic-56423-jelooper)! | ||
|
||
## Next steps | ||
|
||
Explore more about ways to build and use APIs by completing [the other elements](https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art/?WT.mc_id=academic-56423-jelooper) of this module. | ||
|
||
## Optional Transfer Knowledge activity | ||
|
||
Now that you know about APIs and how interesting they can be to discover art, look for other interesting APIs throughout the internet. A good place to start is Todd Motto's [API list](https://github.com/public-apis/public-apis). | ||
|
||
## Feedback | ||
|
||
Be sure to give [feedback about this workshop](https://forms.office.com/r/MdhJWMZthR)! | ||
|
||
[Code of Conduct](CODE_OF_CONDUCT.md) | ||
|
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
|
||
## Explore the art world by using RESTful APIs | ||
|
||
## Workshop Source | ||
|
||
https://docs.microsoft.com/learn/modules/use-apis-discover-museum-art | ||
|
||
## Stage 1: Desired Results | ||
|
||
1. Students will discover various strategies to query APIs by practicing using Museum APIs. | ||
|
||
## Stage 2: Evidence | ||
|
||
By the end of the workshop, students will be able to query the APIs that require various strategies to authenticate. A quiz is included in the slides and lesson plan. | ||
|
||
## Stage 3: Learning Plan | ||
|
||
- Learn about RESTful APIs | ||
- Query an open, public API | ||
- Query an API that requires authentication | ||
|