Overview
What is Rezzy API and what can it do for you?
Traditionally, Rezzy has been a SaaS web app where you click around a dashboard to get things done. But let's be real, that's not how developers operate. You want to write scripts, automate workflows, plug things into your AI agents, and move fast without touching a UI.
That's exactly why we built the Rezzy API. It's the first API of its kind in the resume tooling space, and we're adding more capabilities over time. Right now, you can programmatically generate resumes and cover letters, with more endpoints on the way.
If you want to skip the intro and just get building, head over to the Quickstart. Otherwise, keep reading.
User Profile
To use the Rezzy API, you need a profile set up on the platform. Think of it like a LinkedIn profile - it holds all your information, and your agent refers to it when drafting a resume or cover letter for a specific role.
If you've used Rezzy before, you'll know that the UI lets you either upload a base resume or use your profile as the starting point. The API works the same way, with one difference: we don't support resume uploads via the API. Your profile is the only source of truth here.
If you call the API without a profile set up, you'll get an error telling you to create one first. Head over to rezzy.dev/dashboard/profile to get that sorted before making your first request.
Credits
The Rezzy API is credit-based: each operation costs credits (e.g. 5 for a resume, 3 for a cover letter). The Free plan includes 25 credits total; the Pro plan includes 1,000 per month. You can also buy credit packs. Purchased credits never expire and are only used after your included credits run out. See Pricing for full details on plans and credit packs.
Base URL
All API requests should be made to the following base URL:
https://api.rezzy.dev/v1Response Format
Every response from the Rezzy API follows the same envelope structure:
| Field | Type | Description |
|---|---|---|
success | boolean | true on success, false on error |
message | string | null | A human-readable message describing the result |
data | object | string | null | The response payload on success; may be a string or null on error |
On errors, the same structure is returned with success: false and an appropriate HTTP status code. See the Error Reference for the full list of error codes and what they mean.