Skip to main content
The Profiles endpoint gives you access to Rocketpunch user profile data including professional headlines, skills, and current company affiliations. Public profile data is accessible using your App Key alone, making it straightforward to build candidate search, skill-matching, or directory features. For accessing private or user-specific profile information — such as contact details or non-public career history — your request must carry an OAuth access token obtained with the user’s explicit consent.

​
Endpoint

GET https://openapi.rocketpunch.com/api/v1/profiles

​
Authentication

This endpoint supports two authentication modes depending on the data you need:
  • App Key only — Returns publicly available profile data. Suitable for search, discovery, and directory use cases.
  • OAuth access token — Returns additional profile fields authorized by the user, such as private career history or contact information.
To set up OAuth and obtain user tokens, see the OAuth Overview.

​
Request Headers

When authenticating with your App Key, include:
HeaderRequiredDescription
X-RP-API-KeyYes (App Key mode)Your App Key in the format rp_app_xxxxxxxxxxxxxxxx.
When authenticating with an OAuth token on behalf of a user, replace the App Key header with:
HeaderRequiredDescription
AuthorizationYes (OAuth mode)Bearer token in the format Bearer {oauth_token}.

​
Query Parameters

​
keyword
string
Search term for filtering profiles. Matched against user names, professional headlines, and listed skills. For example, React, data scientist, or product designer.
​
lang
string
default:"ko"
Language code for the response content. Common values are ko (Korean) and en (English). Rocketpunch supports 11 languages and returns a consistent schema regardless of language.
​
page
integer
default:"1"
The page number to retrieve. Page numbering starts at 1.
​
per_page
integer
The number of profiles to return per page. Adjust this to suit the throughput and payload needs of your integration.

​
Example Request

// App Key authentication — public profiles
const response = await fetch(
  "https://openapi.rocketpunch.com/api/v1/profiles?keyword=React&lang=en",
  {
    method: "GET",
    headers: {
      "X-RP-API-Key": "rp_app_xxxxxxxxxxxxxxxx",
    },
  }
);

const data = await response.json();
console.log(data.items);

​
Response

A successful request returns HTTP 200 with a JSON body containing a paginated list of user profile objects under the items key. 
{
  "items": [
    {
      "handle": "jane-doe",
      "name": "Jane Doe",
      "headline": "Frontend Engineer · React · TypeScript",
      "skills": ["React", "TypeScript", "Next.js", "GraphQL"],
      "current_company": {
        "name": "Rocketpunch Labs",
        "handle": "rocketpunch-labs"
      }
    }
  ],
  "total": 512,
  "page": 1,
  "per_page": 20
}
The field values shown above are illustrative examples. Profile data is subject to each user’s individual privacy settings. Fields may be null or absent for profiles where the user has not made that information public, or where OAuth consent has not been granted for private fields.

​
Response Fields

​
items
array
required
An array of user profile objects matching your query. Returns an empty array if no profiles match.
​
total
integer
required
The total number of profiles matching your query across all pages.
​
page
integer
required
The current page number reflected in this response.
​
per_page
integer
required
The number of results per page reflected in this response.

​
Error Responses

HTTP StatusMeaning
401 UnauthorizedYour X-RP-API-Key or OAuth token is missing or invalid.
403 ForbiddenYou attempted to access private profile data without a valid OAuth token, or the user has not granted consent.
429 Too Many RequestsYou have exceeded your plan’s rate limit.
500 Internal Server ErrorAn unexpected server-side error occurred. Retry with exponential backoff.
Profile data is personal information. You must handle all data returned by this endpoint in accordance with applicable privacy laws and Rocketpunch’s API Terms of Service. Do not cache or store user profile data beyond what is necessary for your application’s stated purpose.