Integration documentation for editorial and journal management systems
Scholvet Integration Documentation

API

Registering reviewers

Your editors know reviewers who are not on Scholvet yet. Register them so they can be matched for future articles, at your journal and elsewhere.

When to call it

POST /v1/reviewers

Registers a reviewer or adds the article's keywords to their existing profile. Always returns 202 Accepted.

Request body

Field Type Description
fullName required string Full name, up to 200 characters.
email required string E-mail address you correspond with. Used to find an existing profile and to inform the person.
orcid string ORCID iD, if known. Preferred over the e-mail for finding an existing profile.
academicTitle string Academic title.
institution string Institution, used for conflict-of-interest checks.
rorId string ROR identifier of the institution.
source required "journal" | "author" journal for reviewers your editors chose, author for reviewers suggested by authors.
articleRef string The article that brought you together, for the audit trail.
keywords string[] Up to 30 keywords of that article. They are added to the reviewer's profile with less weight than the reviewer's own keywords and lose weight over the years.
keywordYear integer The year the reviewer worked on these topics, for an import of past reviews. Keywords count less as they age; the default is the current year.
completedReviews[] object[] Reviews the person completed for your journal before it used Scholvet, up to 200. They show the reviewer's experience and never earn points. Sending the same review again does not duplicate it.
completedReviews[].completedOn required date Day the review was completed, e.g. 2023-05-14.
completedReviews[].articleRef string Your identifier for the article; it keeps the record unique. Without it, the day is used.
culture "en" | "tr" Language of the e-mail to the person. Default en.
Request
curl -X POST https://api.scholvet.com/v1/reviewers \
  -H "X-Api-Key: $SCHOLVET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "fullName": "Deniz Yılmaz",
    "email": "[email protected]",
    "orcid": "0000-0003-1415-9265",
    "academicTitle": "Dr.",
    "institution": "Ege University",
    "source": "journal",
    "articleRef": "JMIR-2026-0104",
    "keywords": ["graph neural networks", "drug discovery"],
    "culture": "tr"
  }'
Response
HTTP/1.1 202 Accepted

What happens next

  1. If the person has no profile, Scholvet creates one and the person can be matched straight away.
  2. Scholvet sends the person a single e-mail: who registered them, what is kept, and links to claim the profile with ORCID or to delete it.
  3. If the person already has a profile, only the keywords are added. A profile its owner has claimed is never overwritten.
  4. If the person deleted their record, nothing is stored: journals cannot register them again. The answer is the same 202, so you cannot tell which case applied.

Your responsibility

Send only people your journal works with and has a lawful basis to share with Scholvet under KVKK and GDPR, and say so in your own privacy notice. Scholvet informs every registered person and lets them delete their record at any time.

Next: Usage and quota →