Discover/Orangehrmlive API
live

Orangehrmlive APIopensource-demo.orangehrmlive.com

Create and edit employee records on OrangeHRM's demo instance via 3 endpoints. Authenticate, create new profiles, and update personal details programmatically.

This API takes change requests — .
Endpoint health
verified 4d ago
login
1/1 passing latest checkself-healing
Endpoints
3
Updated
9d ago

What is the Orangehrmlive API?

This API exposes 3 endpoints for managing employee records on the OrangeHRM open-source HR platform. Starting with the login endpoint to establish a session, you can then call create_employee to add new staff profiles — returning a system-assigned emp_number — or edit_employee to update personal details such as name, birthday, gender, and employee ID on any existing record.

This call costs2 credits / call— charged only on success
Try it

No input parameters required.

api.parse.bot/scraper/382e0e00-bf4e-4e90-b0df-d97361bbcd13/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X POST 'https://api.parse.bot/scraper/382e0e00-bf4e-4e90-b0df-d97361bbcd13/login' \
  -H 'X-API-Key: $PARSE_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{}'
All endpoints · 3 totalmissing one? ·

Authenticate with the OrangeHRM demo site using the publicly available demo credentials. This must be called before create_employee or edit_employee. Establishes a session cookie used by subsequent API calls.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "message": "string",
    "logged_in": "boolean"
  },
  "sample": {
    "data": {
      "message": "Login successful",
      "logged_in": true
    },
    "status": "success"
  }
}

About the Orangehrmlive API

Authentication

All write operations require a valid session. Call login first — it accepts no inputs (the demo credentials are fixed) and returns a session_id and encryption_key. Both values are required inputs for create_employee and edit_employee. Without a successful login response, subsequent calls will fail.

Creating Employee Records

create_employee accepts first_name and last_name as required strings, plus optional middle_name and employee_id. The employee_id field takes a custom string (for example '0418'); if omitted, the system may auto-assign one. The response returns the submitted name fields plus the system-assigned emp_number integer, which is the persistent identifier you'll use for future edits.

Editing Employee Records

edit_employee targets an existing record by its emp_number. All personal detail fields — first_name, last_name, gender, birthday, other_id, and employee_id — are optional. If first_name or last_name are not supplied, the endpoint preserves the current values rather than blanking them. The response includes the full updated state of the record: name fields, emp_number, gender as an integer (1 for Male, 2 for Female), birthday in yyyy-mm-dd format, marital_status, other_id, and a nationality object containing id and name.

Reliability & maintenanceVerified

The Orangehrmlive API is a managed, monitored endpoint for opensource-demo.orangehrmlive.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when opensource-demo.orangehrmlive.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official opensource-demo.orangehrmlive.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
4d ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Seed a test OrangeHRM instance with a batch of employee records using create_employee.
  • Sync external HR data into OrangeHRM by updating birthday, gender, and employee_id via edit_employee.
  • Verify that new employee profiles receive a system-assigned emp_number before downstream processing.
  • Automate onboarding flows that create an OrangeHRM record as part of a broader provisioning pipeline.
  • Update marital_status and nationality fields on existing employees after a data migration.
  • Test HR workflow integrations against OrangeHRM's demo environment without manual data entry.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does OrangeHRM have an official developer API?+
OrangeHRM's open-source edition includes a REST API accessible on self-hosted instances, documented at https://opensource-demo.orangehrmlive.com/web/index.php/api/v2/. This Parse API targets the publicly available demo instance specifically.
What does `edit_employee` return beyond the fields I submit?+
edit_employee always returns the full updated record: emp_number, first_name, last_name, middle_name, employee_id, gender (as integer 1 or 2), birthday (yyyy-mm-dd), marital_status, other_id, and a nationality object with id and name. Fields you did not submit are preserved and still appear in the response.
Can I retrieve a list of existing employees or look up an employee by name?+
Not currently. The API covers creating and editing employee records. You can fork it on Parse and revise it to add a read or search endpoint that returns employee listings.
Can I delete an employee record through this API?+
Not currently. The three endpoints cover session authentication, record creation, and record editing. You can fork it on Parse and revise it to add a delete endpoint targeting the relevant OrangeHRM resource.
Does this API work against my own self-hosted OrangeHRM instance?+
No — the endpoints target the public OrangeHRM demo instance at opensource-demo.orangehrmlive.com, which uses fixed demo credentials. Any records you create or edit there are shared with all other demo users and are periodically reset.
Page content last updated . Spec covers 3 endpoints from opensource-demo.orangehrmlive.com.
Related APIs in OtherSee all →
maersk.com API
Track your Maersk shipping containers in real-time, monitor vessel schedules and locations, and discover available routes between ports and countries. Access comprehensive port data, search for specific locations, and view detailed shipping route information to plan your logistics more effectively.
pexels.com API
Search and browse millions of free stock photos and videos on Pexels. Access trending content, photographer galleries, photo/video challenges, and search suggestions via a clean API.
cgccards.com API
Access data from cgccards.com.
megamillions.com API
Check the latest Mega Millions winning numbers and jackpot amounts, browse historical drawings, and discover the top jackpots across participating lottery states. Stay updated on lottery results and track winning combinations whenever you need them.
powerball.com API
Check the latest Powerball drawing results, historical winning numbers, current jackpot amounts, and prize information all in one place. Browse past draws by date, view odds and prize breakdowns, and explore stories from winners to stay informed about your favorite lottery game.
pageviews.wmcloud.org API
Access Wikipedia pageview analytics across articles, languages, and time periods. Retrieve per-article view counts, top-viewed pages, cross-language traffic breakdowns, site-wide aggregates, category-level mass analysis, redirect traffic attribution, user contribution metrics, and Wikimedia Commons media request counts.
identify.plantnet.org API
Identify and explore plant species by searching through Pl@ntNet's comprehensive botanical database to access detailed information like taxonomic families, genera, species descriptions, photos, and community observations. Track plant distributions, view contribution trends, and discover expert contributors within the platform's collaborative plant identification community.
ifixit.com API
Access data from ifixit.com.