canonical: https://jentic.com/apis/rocketlane.com/rocketlane

# Rocketlane API

Rocketlane is a customer onboarding platform. This API provides endpoints for managing projects, tasks, task comments, team members, users, and teams. The API exposes 28 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create project, update project. Covers 28 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Create Project
- Update Project
- Add task comment
- Invite member
- Get all Members

## Use cases

### HR and Recruiting Operations

Use the Rocketlane API to perform hr recruiting operations programmatically. The API provides 28 endpoints covering core functionality including create project, update project, create task.

Example prompt: Call POST /projects to create project

### Automated API Keys Management

Automate API keys operations by combining multiple Rocketlane API endpoints. Agents can update project and then create task in a single workflow.

Example prompt: Call PUT `/projects/{projectId}` to update project, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Rocketlane API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create project', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/projects` | Create Project |
| PUT | `/projects/{projectId}` | Update Project |
| POST | `/tasks` | Create Task |
| PUT | `/projects/{projectId}/tasks/{taskId}` | Update Task |
| POST | `/projects/{projectId}/tasks/{taskId}/comments` | Add task comment |
| POST | `/members` | Invite member |
| GET | `/members` | Get all Members |
| PUT | `/members` | Update member |

## Key resources

- **API Keys** — Operations related to API Keys
- **Members** — Operations related to Members
- **Projects** — Operations related to Projects
- **Tasks** — Operations related to Tasks
- **Teams** — Operations related to Teams

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/rocketlane.com/rocketlane/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Rocketlane API by hand means sending its api-key header on every request and handling the request plumbing yourself. Through Jentic you install once, import the Rocketlane API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Rocketlane puts the project and task ids in the URL path (`/projects/{projectId}/tasks/{taskId}`), so a rule can pin your agent to one project: it can read and update tasks and post comments there and nothing else. You choose the operations it may call, so writes like creating projects or updating members are not included unless you add them.
- **Credential handling:** Your Rocketlane API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a project' or 'add a comment to a task', and Jentic returns the matching Rocketlane operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Rocketlane API use?

The Rocketlane API uses an API key passed in the `api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create project with the Rocketlane API?

Yes. Use the POST /projects endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Rocketlane API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create project through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create project'. Jentic returns the matching Rocketlane API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Rocketlane API have?

The Rocketlane API exposes 28 endpoints covering API keys, members, projects operations.

### Can I limit what my agent is allowed to do with the Rocketlane API?

Yes. Because you run Jentic One yourself, your own rules decide which Rocketlane operations and credentials the agent may use. Since Rocketlane carries the project and task ids in the URL path, such as `/projects/{projectId}/tasks/{taskId}`, you can pin the agent to a single project so it only reads and updates tasks and posts comments there. Writes such as POST /projects to create projects or PUT /members to update members stay off unless you explicitly add them.