Reference
API Documentation
User Endpoints

User API Endpoints Documentation

Endpoints

1. Get All Users

Endpoint: GET /users

Description: Retrieves a paginated list of all users with optional filtering by location and dependencies.

Query Parameters:

ParameterTypeRequiredDefaultDescription
pageintegerNo1Page number for pagination
per_pageintegerNo30Number of items per page (max: 100)
locationstringNo-Filter users by location (partial match)
dependency_namesstringNo-Comma-separated list of dependency names to filter by

Example Request:

GET /users?page=1&per_page=50&location=San Francisco&dependency_names=react,typescript&dependency_files=package.json

Response:

{
  "data": [
    {
      "github_rest_id": 123456,
      "github_graphql_id": "MDQ6VXNlcjEyMzQ1Ng==",
      "login": "octocat",
      "name": "The Octocat",
      "email": "[email protected]",
      "avatar_url": "https://avatars.githubusercontent.com/u/123456?v=4",
      "company": "GitHub",
      "location": "San Francisco",
      "bio": "GitHub's mascot",
      "followers": 1000,
      "following": 500,
      "type": "User",
      "created_at": "2011-01-25T18:32:29Z",
      "updated_at": "2024-01-15T10:30:00Z"
    }
  ],
  "meta": {
    "request_id": "req-123",
    "timestamp": 1642233600,
    "execution_time": 45
  }
}

Pagination: This endpoint uses GitHub-style pagination with Link headers for navigation.


2. Get User by Login

Endpoint: GET /users/{login}

Description: Retrieves detailed information about a specific user by their GitHub login/username.

Path Parameters:

ParameterTypeRequiredDescription
loginstringYesGitHub username/login

Example Request:

GET /users/octocat

Response:

{
  "github_rest_id": 123456,
  "github_graphql_id": "MDQ6VXNlcjEyMzQ1Ng==",
  "login": "octocat",
  "name": "The Octocat",
  "email": "[email protected]",
  "avatar_url": "https://avatars.githubusercontent.com/u/123456?v=4",
  "company": "GitHub",
  "location": "San Francisco",
  "bio": "GitHub's mascot",
  "followers": 1000,
  "following": 500,
  "type": "User",
  "created_at": "2011-01-25T18:32:29Z",
  "updated_at": "2024-01-15T10:30:00Z"
}

Error Responses:

  • 400 Bad Request - Missing or invalid login parameter
  • 404 Not Found - User not found

Common Response Fields

Meta Information

All endpoints return a meta object with the following fields:

FieldTypeDescription
request_idstringUnique identifier for the request
timestampintegerUnix timestamp of the response
execution_timeintegerRequest execution time in milliseconds

User Object

User objects contain the following fields:

FieldTypeDescription
github_rest_idintegerGitHub REST API user ID
github_graphql_idstringGitHub GraphQL API user ID
loginstringGitHub username
namestringUser's display name (nullable)
emailstringUser's email (nullable)
avatar_urlstringURL to user's avatar image (nullable)
companystringUser's company (nullable)
locationstringUser's location (nullable)
biostringUser's bio/description (nullable)
followersintegerNumber of followers
followingintegerNumber of users being followed
typestringUser type (typically "User")
created_atstringISO 8601 timestamp of account creation
updated_atstringISO 8601 timestamp of last update

Error Handling

All endpoints return appropriate HTTP status codes:

  • 200 OK - Request successful
  • 400 Bad Request - Invalid request parameters
  • 401 Unauthorized - Missing or invalid authentication
  • 404 Not Found - Resource not found
  • 500 Internal Server Error - Server error

Error responses follow this format:

{
  "error": "Error message describing what went wrong"
}
OpenQ Logo
The CRM for developer relations to connect community, product and customer data.
Company
About
Careers
Made by dev rels for dev rels
in Germany, US, Canada, Austria & Spain
© 2025 OpenQ Labs GmbH. All right reserved.