> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocketpunch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rocketpunch Open API Changelog and Release History

> Track every release, new endpoint, behavior change, and deprecation for the Rocketpunch Open API. Check here before updating your integration.

The Rocketpunch Open API changelog records every release, new endpoint, behavior change, and deprecation notice in one place. Bookmark this page and check it whenever you update your integration. Entries are ordered newest-first.

<Note>
  The Rocketpunch Open API is currently in **Invited Builder Beta**. The API surface is stable and production-ready for approved builders, but new endpoints and capabilities will be added as the beta progresses. Subscribe to announcements at [developers.rocketpunch.com](https://developers.rocketpunch.com) to be notified of changes.
</Note>

## v1 — Builder Beta

**Released: 2025**

The initial public release of the Rocketpunch Open API, available to invited builders. This version establishes the foundational endpoint set, authentication model, and data schema that future versions will build on.

### Endpoints

<Card title="GET /api/v1/jobs" icon="briefcase">
  Search job listings across Rocketpunch's indexed positions. Filter by keyword and language. Returns paginated job objects including title, company, location, and tags.
</Card>

<Card title="GET /api/v1/companies" icon="building">
  Search and retrieve company profiles from over 170,000 indexed companies. Filter by keyword and language. Returns company name, industry, size, location, and social links.
</Card>

<Card title="GET /api/v1/profiles" icon="user">
  Access public user profile data. Returns career history, skills, and public contact information for a given user. Requires OAuth 2.0 for user-specific profile access.
</Card>

<Card title="GET /api/v1/events" icon="calendar">
  Browse and search Rocketpunch networking events. Returns event name, date, location, organizer, and registration link.
</Card>

### Authentication

* **App Key authentication** via the `X-RP-API-Key` request header. Keys follow the format `rp_app_xxxxxxxxxxxxxxxx` and are issued through the developer portal.
* **OAuth 2.0 Authorization Code Flow** for user-consent data access. Register a redirect URI at [developers.rocketpunch.com/apps/new](https://developers.rocketpunch.com/apps/new) and implement the four-step flow described in the [Auth Flow guide](/api/oauth/flow).

### Platform Features

* **Multilingual support** — All endpoints accept a `lang` parameter. 11 languages supported with consistent response schema across all locales: Korean, English, Japanese, Chinese (Simplified), Chinese (Traditional), Spanish, French, German, Portuguese, Indonesian, and Vietnamese.
* **99.95% availability SLA** — The API is backed by a 99.95% uptime commitment for invited builder partners.
* **Paginated responses** — All list endpoints return paginated results with `page`, `per_page`, and `total_pages` fields in the response envelope.
* **Rate limit headers** — Every response includes `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset` headers. See the [Rate Limits](/api/rate-limits) page.

***

## Versioning Policy

The Rocketpunch API uses **URL-based versioning**. The current version is `v1`, reflected in every endpoint path:

```
https://openapi.rocketpunch.com/api/v1/{resource}
```

### What triggers a new version

A new major version (e.g. `v2`) is released when a change would break existing integrations. Examples of breaking changes include:

* Removing an endpoint
* Renaming or removing a required request parameter
* Changing the data type of a response field
* Removing a field from the response schema

### What does not trigger a new version

Additive changes are made within the current version without a version bump. These changes are backward-compatible and will not break existing integrations:

* Adding a new endpoint
* Adding optional request parameters
* Adding new fields to response objects
* Adding new supported values to existing parameters (such as new `lang` codes)
* Performance improvements and bug fixes

### Deprecation policy

When a version is scheduled for retirement, Rocketpunch will:

1. Announce the deprecation date at least **six months** in advance via the developer portal and email to registered app owners.
2. Continue serving the deprecated version for the full notice period.
3. Return a `Deprecation` header on all responses from the deprecated version as the retirement date approaches.

<Tip>
  Watch [developers.rocketpunch.com](https://developers.rocketpunch.com) for announcements about new endpoints, beta features, and upcoming releases. You can also follow the changelog via the RSS feed linked in the developer portal.
</Tip>