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

# Laddro Career API

The Laddro Career API rewrites a resume to match a specific job posting and returns the tailored version as a PDF, optionally with a matching cover letter in a ZIP. It parses an uploaded PDF into a stored resume, generates or saves cover letters, re-renders resumes and letters with a chosen template, font, spacing, and color, and exports any stored resume as a PDF. AI endpoints can stream progress as Server-Sent Events, and calls draw on a monthly credit quota.

## For AI agents

Tailor a stored or uploaded resume to a job description or job URL, generate a cover letter, and render or export the result as a styled PDF.

## Scope

Does not handle job applications to employers, applicant tracking, or job search listings. Use for tailoring, generating, and rendering resumes and cover letters only.

## Capabilities

- Tailor a resume to a job by positionName plus a jobDescription or jobUrl, returning a PDF and the new resume id in X-Resume-Id
- Generate a cover letter for a position from a stored resume or an uploaded file, or save one from your own letterContent
- Parse an uploaded PDF resume into a stored, editable resume with a chosen template
- Re-render a resume or cover letter with a different templateId, locale, font, fontSize, spacing, margin, or colorId
- Export a stored resume as a PDF by resumeId
- List resume templates, fonts, and supported languages before rendering

## Use cases

### Job-Specific Resume Tailoring

A job-search agent applies to each role with a resume rewritten for that posting. It sends the positionName with either the pasted jobDescription or a jobUrl that Laddro fetches and extracts, along with a stored resumeId or an uploaded PDF, and receives a tailored PDF. Setting includeCoverLetter returns a ZIP with both documents, and response headers carry the ids of the saved resume and cover letter.

Example prompt: Call POST `/v1/tailor` with resumeId from GET `/v1/resumes`, positionName 'Senior Data Engineer', jobUrl 'https://example.com/jobs/123', and includeCoverLetter 'true', then save the returned ZIP

### Cover Letter Generation

When only a letter is needed, the agent calls the generate operation with the positionName and a job description or URL, using a stored resume or an uploaded file as the source. A letter written elsewhere can be saved instead with fullName and letterContent, then rendered with a template so it matches the resume's styling.

Example prompt: Call POST `/v1/cover-letters/generate` with resumeId, positionName 'Product Manager', and jobDescription text, then PUT `/v1/cover-letters/{coverLetterId}/render` with a templateId from GET `/v1/templates`

### Resume Import and Restyling

A candidate's existing PDF becomes a structured resume through the parse operation, after which the agent can re-render it with any template, locale, font, and color, or export it to a PDF. The templates, fonts, and languages lists need no API key, so the agent can show options before spending credits.

Example prompt: Call POST `/v1/resumes/parse` with the PDF file and a templateId, then POST `/v1/export` with the returned resumeId and a font from GET `/v1/fonts`

### AI Agent Job Applications via Jentic

An AI job-search agent calls Laddro through Jentic without holding the laddro_live_ key. It searches by intent, receives the tailoring or cover-letter operation with its input schema, and executes with the x-api-key injected at run time, so producing a tailored resume is one step in a larger application workflow.

Example prompt: Search Jentic for 'tailor a resume to a job', load the POST `/v1/tailor` schema, and execute it with a resumeId, positionName, and jobUrl

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/tailor` | Tailor resume for a job |
| POST | `/v1/cover-letters/generate` | Generate cover letter |
| POST | `/v1/resumes/parse` | Create resume from PDF |
| POST | `/v1/export` | Export resume as PDF |
| GET | `/v1/resumes` | List resumes |
| PUT | `/v1/resumes/{resumeId}/render` | Render resume with new template settings |
| GET | `/v1/templates` | List resume templates |

## Key resources

- **Tailor** — Rewrite a resume for a job description or job URL, optionally with a cover letter
- **Resumes** — List, read, parse from PDF, render with template settings, and export as PDF
- **Cover letters** — List, read, create, generate, and render cover letters
- **Templates and settings** — List resume templates, fonts, and supported languages

## 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:** 44 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 76 / 100
  - AI-Readiness & Agent Experience: 20 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 80 / 100
- **View full report:** https://jentic.com/apis/laddro.com/laddro/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 Laddro by hand means sending a laddro_live_ key in x-api-key, choosing between JSON and multipart uploads, handling PDF or ZIP binary responses, and watching for 402 when credits run out. Through Jentic you install once, import Laddro from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Laddro puts the resume id in the URL path (`/v1/resumes/{resumeId}/...`), so a rule can pin your agent to one resume for reads and re-renders. Tailoring, generation, and export carry their targets in the request body, so for those you choose which operations it may call, and credit-spending ones are not included unless you add them.
- **Credential handling:** Your Laddro 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 'tailor a resume to a job' or 'export a resume as PDF', and Jentic returns the matching Laddro operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **OpenAI API** — General-purpose language models
- **Affinda API** — Resume and document parsing into structured data
- **Careerjet Job Search API** — Job listings search

## FAQ

### What authentication does the Laddro Career API use?

Per its OpenAPI spec, the Laddro Career API uses an API key, starting with laddro_live_, sent in the x-api-key header. Keys come from console.laddro.com. The templates, template detail, fonts, and languages endpoints are public and need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

### Can I tailor a resume from a job URL with the Laddro Career API?

Yes. POST `/v1/tailor` takes positionName (required) and either jobDescription or jobUrl, which Laddro fetches and extracts. Use a stored resumeId, upload a PDF or DOCX file, or send neither to use your default resume. Set includeCoverLetter to true to receive a ZIP with the tailored resume and a cover letter.

### What are the rate limits for the Laddro Career API?

The OpenAPI spec describes credit-based usage rather than a fixed request rate: each action consumes credits from a monthly quota that depends on your plan, then from prepaid credits. When credits run out the API returns 402. See https://console.laddro.com for your current quota.

### How do I generate a cover letter through Jentic with the Laddro Career API?

Search Jentic for 'generate a cover letter for a job' and it returns the cover-letter generation operation with its input schema. Execute POST `/v1/cover-letters/generate` with positionName and a jobDescription or jobUrl, plus a resumeId. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Laddro MCP server?

You don't need an MCP server to give your agent the Laddro Career API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered by intent on demand, so no extra server's tool definitions sit in the agent's context.

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

Yes. Give a browsing agent only the template, font, language, and resume read operations, so it can show options without spending credits. If it should work on one document, allow the render operation on a single resumeId and nothing else, and every call is logged by your own instance.