Quickstart

Authentication

Subscribe on RapidAPI and send your key on every request. RapidAPI handles the metering and the billing; this service checks that the call actually came through it.

To try the parser without a key, use the free browser tool — same endpoint, same model, smaller limits.

x-rapidapi-key: YOUR_KEY
x-rapidapi-host: resumejson-resume-cv-parser-api.p.rapidapi.com

RapidAPI shows the exact x-rapidapi-host for your subscription in the code snippet on the listing. Copy it from there — it is the authoritative value.

A request that reaches the origin without RapidAPI's proxy secret gets 403 not_via_rapidapi. A key that is sent through RapidAPI but is not on an active subscription never reaches us at all: the gateway answers 403 itself, with {"message": "…"} and no error.code.

Three ways to send a resume

1. JSON, when you already have the text

curl -X POST 'https://resumejson-resume-cv-parser-api.p.rapidapi.com/v1/parse' \
  -H 'x-rapidapi-key: YOUR_KEY' \
  -H 'x-rapidapi-host: resumejson-resume-cv-parser-api.p.rapidapi.com' \
  -H 'content-type: application/json' \
  -d '{"text":"Sarah Okonkwo\nStaff Engineer ..."}'

2. Multipart, straight from an upload form

curl -X POST 'https://resumejson-resume-cv-parser-api.p.rapidapi.com/v1/parse' \
  -H 'x-rapidapi-key: YOUR_KEY' \
  -H 'x-rapidapi-host: resumejson-resume-cv-parser-api.p.rapidapi.com' \
  -F 'file=@cv.pdf'

3. Raw bytes, when you are streaming a file through

curl -X POST 'https://resumejson-resume-cv-parser-api.p.rapidapi.com/v1/parse' \
  -H 'x-rapidapi-key: YOUR_KEY' \
  -H 'x-rapidapi-host: resumejson-resume-cv-parser-api.p.rapidapi.com' \
  -H 'content-type: application/pdf' \
  --data-binary @cv.pdf

PDF, DOCX and image types are recognised from the file's own bytes, so an upload labelled application/octet-stream still works. A JPEG, PNG or WebP of the page goes through the same three routes.

Getting the resume back in another language

By default a CV comes back in its own language: an Indonesian CV returns Indonesian job titles. Add output_language and the text values are written in the language you name instead.

curl -X POST 'https://resumejson-resume-cv-parser-api.p.rapidapi.com/v1/parse?output_language=French' \
  -H 'x-rapidapi-key: YOUR_KEY' \
  -H 'x-rapidapi-host: resumejson-resume-cv-parser-api.p.rapidapi.com' \
  -F 'file=@cv.pdf'

Any language the model can write is accepted — there is no fixed list. Send a name (French, Bahasa Indonesia, 日本語) or a code (fr, pt-BR, zh-Hans); a code is expanded for you, and meta.outputLanguage comes back with what was understood, so fr answers "French".

A JSON or multipart body can carry the same value as an output_language field instead. The query string works for all three ways of sending a CV, including raw bytes, which is why it is the one documented here. If you send both, the query string wins.

Translating is not inventing: a field the CV does not state is still null. A value that is not a language — too long, or carrying anything a language name does not — comes back as 400 unsupported_language before the document is read.

Limits

Every response through RapidAPI carries your position against that quota: x-ratelimit-requests-limit, x-ratelimit-requests-remaining, and x-ratelimit-requests-reset in seconds. The window runs from the day you subscribed, not the calendar month. Read x-ratelimit-requests-remaining to warn before the refusal rather than after it.

What it costs

The same rungs the listing meters, on the page you are reading. Billing and metering are RapidAPI's; these are the numbers it charges.

Basic is a hard cap and cannot bill you. The paid plans allow overage past the quota rather than blocking a working integration at it; every per-parse overage is in the table above. Subscribe on RapidAPI.

Every error, and what to do about it

Retry the transient one. The rest describe something about the request that a retry will not change.

Every row here still costs you a request. RapidAPI meters at its gateway, on the call rather than on the answer: measured 2026-09-16, a 400 decremented x-ratelimit-requests-remaining by exactly the same one as a 200. That includes the 500s, which are our fault and not yours. What costs nothing is a call the gateway turns away itself — the quota 429 below, and a request to a path the listing does not declare; those come back with no x-ratelimit-* headers at all.

Stuck on an error the table does not explain? Write to support@tiraisoft.com with the x-request-id, the status and the error.code, or ask on the RapidAPI listing.

Every response to /v1/parse carries an x-request-id header, and a 500 repeats it in the body as request_id. It identifies that one call. Quote it about a parse that came back wrong as well as one that failed — it saves you reproducing anything.

{
  "error": {
    "code": "too_large",
    "message": "That document is 91,204 characters; the limit is 60,000. Send the resume alone, not a bundle.",
    "limit": 60000
  }
}

Reading the response

Two keys: resume is the document, meta is what happened. Every field of resume is documented in the field reference.