Skip to content
Beta

Scholardemia is in beta.

API access & review contexts

3 min readUpdated 10 July 2026Integrations & connected apps

Review contexts give departments, funders, and programmes a structured review workflow of their own; see Review contexts for institutions. Each context also exposes a REST API, so institutions can drive submissions and reviews from their own systems instead of the web interface.

The ReviewContext API

All endpoints live under /api/review-contexts/{contextId} on scholardemia.com and exchange JSON. The surface covers the full editorial flow:

  • Submissions: list with filters, create, fetch, update, and assign reviewers.
  • Reviews: list reviewer evaluations and fetch or update an individual review.
  • Configuration: templates, categories, and rubrics that shape how the context reviews work.

Listings are paginated with limit and offset parameters (limit up to 100) and support sorting and status filters. A formal OpenAPI 3.1 specification of the API is available on request.

Authentication and permissions

  • Requests authenticate with a signed-in session, the same way the web interface does. If you need server-to-server credentials, arrange them with support when your context is set up.
  • Access is scoped per context: you can only reach contexts where your account holds the appropriate role, and the API enforces the same permissions as the interface.
  • Keep request volumes reasonable; abusive traffic may be throttled.

Getting set up

API access accompanies an institutional review context, so the starting point is the context itself. Email support@scholardemia.com describing your workflow and the systems you want to connect, and the team will set up the context, credentials, and the specification for your developers.

Keep API credentials server-side and out of shared code. Anyone holding them can act with their permissions inside the context.

Still stuck? Talk to a person.

Our support team reads every message. Include what you were doing, any error message, and a screenshot if you have one; it usually saves a round-trip.

Email support