11---
2- title : Custom Mime Types | GitHub API
2+ title : Custom Media Types | GitHub API
33---
44
5- # GitHub Mime Types
5+ # GitHub Media Types
66
7- Custom mime types are used in the API to let consumers choose the format
7+ Custom media types are used in the API to let consumers choose the format
88of the data they wish to receive. This is done by adding one or more of
9- the following types to the ` Accept ` header when you make a request. Mime
10- types are specific to resources, allowing them to change independently
11- and support formats that other resources don't.
9+ the following types to the ` Accept ` header when you make a request. Media types
10+ are specific to resources, allowing them to change independently and support
11+ formats that other resources don't.
1212
13- All GitHub mime types look like this:
13+ All GitHub media types look like this:
1414
1515 application/vnd.github[.version].param[+json]
1616
17- The most basic mime types the API supports are:
17+ The most basic media types the API supports are:
1818
1919 application/json
2020 application/vnd.github+json
@@ -53,14 +53,14 @@ For specifics on versions, check the [API changelog](/v3/changelog).
5353
5454The body of a comment can be written in [ GitHub Flavored Markdown] [ gfm ] .
5555Issues, Issue Comments, Pull Request Comments, and Gist Comments all
56- accept these same mime types:
56+ accept these same media types:
5757
5858### Raw
5959
6060 application/vnd.github.VERSION.raw+json
6161
6262Return the raw markdown body. Response will include ` body ` . This is the
63- default if you do not pass any specific mime type.
63+ default if you do not pass any specific media type.
6464
6565### Text
6666
@@ -85,7 +85,7 @@ Return raw, text and html representations. Response will include `body`,
8585
8686## Git Blob Properties
8787
88- The following mime types are allowed when getting a blob:
88+ The following media types are allowed when getting a blob:
8989
9090### JSON
9191
0 commit comments