Find topics via various criteria. Results are sorted by best match. This method returns up to 100 results per page. See “Searching topics” for a detailed list of qualifiers.
When searching for topics, you can get text match metadata for the topic’s short_description, description, name, or display_name field when you pass the text-match media type. For more details about how to receive highlighted search results, see Text match metadata.
For example, if you want to search for topics related to Ruby that are featured on https://github.com/topics. Your query might look like this:
q=ruby+is:featured
This query searches for topics with the keyword ruby and limits the results to find only topics that are featured. The topics that are the best match for the query appear first in the search results.
The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
Topic Search Result Item
Find users via various criteria. This method returns up to 100 results per page.
When searching for users, you can get text match metadata for the issue login, email, and name fields when you pass the text-match media type. For more details about highlighting search results, see Text match metadata. For more details about how to receive highlighted search results, see Text match metadata.
For example, if you’re looking for a list of popular users, you might try this query:
q=tom+repos:%3E42+followers:%3E1000
This query searches for users with the name tom. The results are restricted to users with more than 42 repositories and over 1,000 followers.
The query contains one or more search keywords and qualifiers. Qualifiers allow you to limit your search to specific areas of GitHub. The REST API supports the same qualifiers as GitHub.com. To learn more about the format of the query, see Constructing a search query. See “Searching users” for a detailed list of qualifiers.
Sorts the results of your query by number of followers or repositories, or when the person joined GitHub Enterprise Server. Default: best match
Allowed values:followersrepositoriesjoined
Determines whether the first search result returned is the highest number of matches (desc) or lowest number of matches (asc). This parameter is ignored unless you provide sort.
Allowed values:descasc
Default:desc
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
User Search Result Item
Lists all teams in an organization that are visible to the authenticated user.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
Groups of organization members that gives permissions on specified repositories.
Example:https://github.com/orgs/rails/teams/core
Groups of organization members that gives permissions on specified repositories.
To create a team, the authenticated user must be a member or owner of {org}. By default, organization members can create teams. Organization owners can limit team creation to organization owners. For more information, see “Setting team creation permissions.”
When you create a new team, you automatically become a team maintainer without explicitly adding yourself to the optional array of maintainers. For more information, see “About teams”.
The name of the team.
The description of the team.
List GitHub IDs for organization members who will become team maintainers.
The full name (e.g., “organization-name/repository-name”) of repositories to add the team to.
The level of privacy this team should have. The options are:
For a non-nested team:
* secret - only visible to organization owners and members of this team.
* closed - visible to all members of this organization.
Default: secret
For a parent or child team:
* closed - visible to all members of this organization.
Default for child team: closed
Allowed values:secretclosed
Deprecated. The permission that new repositories will be added to the team with when none is specified. Can be one of:
* pull - team members can pull, but not push to or administer newly-added repositories.
* push - team members can pull and push, but not administer newly-added repositories.
Allowed values:pullpush
Default:pull
The ID of a team to set as the parent team.
The distinguished name (DN) of the LDAP entry to map to a team. LDAP synchronization must be enabled to map LDAP entries to a team. Use the “Update LDAP mapping for a team” endpoint to change the LDAP DN. For more information, see “Using LDAP.”
Response
Groups of organization members that gives permissions on specified repositories.
Unique identifier of the team
Example:42
Example:MDQ6VGVhbTE=
URL for the team
Example:https://api.github.com/organizations/1/team/1
Example:https://github.com/orgs/rails/teams/core
Name of the team
Example:Developers
Example:justice-league
Example:A great team.
The level of privacy this team should have
Allowed values:closedsecret
Example:closed
Permission that the team will have for its repositories
Example:push
Example:https://api.github.com/organizations/1/team/1/members{/member}
Example:https://api.github.com/organizations/1/team/1/repos
Groups of organization members that gives permissions on specified repositories.
Example:3
Example:10
Example:2017-07-14T16:53:42Z
Example:2017-08-17T12:37:15Z
Organization Full
Distinguished Name (DN) that team maps to within LDAP environment
Example:uid=example,ou=users,dc=github,dc=com
Gets a team using the team’s slug. GitHub Enterprise Server generates the slug from the team name.
Note: You can also specify a team by org_id and team_id using the route GET /organizations/{org_id}/team/{team_id}.
team_slug parameter
Response
Groups of organization members that gives permissions on specified repositories.
Unique identifier of the team
Example:42
Example:MDQ6VGVhbTE=
URL for the team
Example:https://api.github.com/organizations/1/team/1
Example:https://github.com/orgs/rails/teams/core
Name of the team
Example:Developers
Example:justice-league
Example:A great team.
The level of privacy this team should have
Allowed values:closedsecret
Example:closed
Permission that the team will have for its repositories
Example:push
Example:https://api.github.com/organizations/1/team/1/members{/member}
Example:https://api.github.com/organizations/1/team/1/repos
Groups of organization members that gives permissions on specified repositories.
Example:3
Example:10
Example:2017-07-14T16:53:42Z
Example:2017-08-17T12:37:15Z
Organization Full
Distinguished Name (DN) that team maps to within LDAP environment
Example:uid=example,ou=users,dc=github,dc=com