Skip to content
emploreadocs

Quickstart - five minutes to your first leave request

1. Get an API key

A company admin creates one in Settings, then Integrations, then Create key. Pick the read and write scopes. The key (emp_live_...) is shown once - store it securely.

2. Read the company context

curl https://app.emplorea.com/api/v1/company \
  -H "Authorization: Bearer $EMPLOREA_KEY"

# => { "data": { "name": "Acme Pty Ltd", "jurisdiction": ["AU"],
#      "currency": "AUD", "financial_year_start": "07-01", ... } }

3. List employees and leave types

curl "https://app.emplorea.com/api/v1/employees?status=active" \
  -H "Authorization: Bearer $EMPLOREA_KEY"

curl https://app.emplorea.com/api/v1/leave-types \
  -H "Authorization: Bearer $EMPLOREA_KEY"

4. Check the balance, then request leave

curl "https://app.emplorea.com/api/v1/leave/balances?employee_id=EMPLOYEE_ID" \
  -H "Authorization: Bearer $EMPLOREA_KEY"

curl -X POST https://app.emplorea.com/api/v1/leave \
  -H "Authorization: Bearer $EMPLOREA_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "employee_id": "EMPLOYEE_ID",
    "leave_type_id": "LEAVE_TYPE_ID",
    "start_date": "2026-07-14",
    "end_date": "2026-07-18",
    "notes": "Family holiday"
  }'

# => 201 { "data": { "id": "...", "days": 5, "status": "pending" },
#          "warnings": [] }
# Day counts exclude weekends and public holidays automatically.
# warnings are never blocking - the request is saved regardless.

5. Approve it

curl -X PATCH https://app.emplorea.com/api/v1/leave/REQUEST_ID/approve \
  -H "Authorization: Bearer $EMPLOREA_KEY"

That is the whole loop. From here: subscribe to webhooks for real-time events, connect the MCP server to work from inside an AI assistant, or script everything with the CLI.