HRTEQ is a global AI-powered HRTech, RecruitTech and CRM platform for recruitment agencies, HR consultancy firms, staffing companies and corporate HR teams. These guides cover applicant management, configurable workflows, document control, audit trails, charges and payments, automation, and the HTTP API behind the app.
Start here
Three articles cover most of what a new team needs before its first intake.
Quickstart
Provision an organization workspace, review the configurable defaults that are seeded for you, and take one applicant from intake to a live pipeline card.
Core concepts
The five objects that carry almost everything in HRTEQ, why the deployment lifecycle lives on the application rather than the person, and how tenant isolation is enforced.
Roles and permissions
The nine staff roles, the read-all write-by-module matrix behind them, who may move an application into which stage, and who may override a blocking requirement.
Browse by area
Get started
Provision a workspace, learn the vocabulary, and understand who can do what.
Recruitment
Intake through deployment: applicants, job orders, the pipeline board, and the gate that governs it.
Documents & compliance
Document control, verification, expiry, the audit trail, and data privacy practices.
Finance
Fee configuration, charges, payments, receipts, and financial clearance.
Automation
Rules that assign work and chase deadlines, plus the scheduled sweeps behind them.
Reference
Workflow reference and a plain-language index of common statuses and values.
Developers
How the HTTP API authenticates and responds, and what is not available yet.
How the system fits together
Four objects carry almost everything. Getting them straight makes the rest of the docs read quickly.
- An applicant is a person. They are created once and keep their own documents — identity records, qualifications and employment history.
- A job order is demand from a principal, the employer. It holds one or more positions, each with a quota.
- An application is one applicant against one position. This is the object that moves through stages, holds the per-deployment documents, and carries the charges.
- A stage has requirements. They are checked when an application tries to enter, and the officer who owns that stage is the one who may move it there.
Read Core concepts for the full object graph, then Stage gates for the rule engine.
Create an applicant
The API is the same one the app uses. Sign in, keep the session cookie, and echo the CSRF token on every write. The response returns the new id and the allocated applicantNo.
# $API_URL is your deployment's API origin.
# In development that is http://localhost:4000.
curl -X POST "$API_URL/v1/applicants" \
-H "Content-Type: application/json" \
-H "X-CSRF-Token: $CSRF" \
--cookie "hrteq_session=$SESSION" \
-d '{
"firstName": "Maria",
"lastName": "Santos",
"mobile": "+639171234567",
"sourceChannel": "ONLINE_FORM",
"dataPrivacyConsent": true
}'dataPrivacyConsent must be literally true, and at least one of mobile or email is required. See the API page for authentication, error codes and limits.
Every article
Get started
- Quickstart
- Provision an organization workspace, review the configurable defaults that are seeded for you, and take one applicant from intake to a live pipeline card.
- Core concepts
- The five objects that carry almost everything in HRTEQ, why the deployment lifecycle lives on the application rather than the person, and how tenant isolation is enforced.
- Roles and permissions
- The nine staff roles, the read-all write-by-module matrix behind them, who may move an application into which stage, and who may override a blocking requirement.
Recruitment
- Applicants
- Intake, numbering, duplicate detection, source attribution and résumé parsing — everything that happens before an applicant is endorsed to a position.
- Job orders and positions
- How demand from a principal is recorded: job order fields, positions and quotas, validity and expiry, and which matching fields must never be published.
- The pipeline board
- How applications appear on the board, what a card tells you, how a move is attempted, and which parts of the current screen are real data versus placeholder.
- Stage gates
- Configure workflow requirements: the five requirement types and exactly what satisfies each, blocking versus advisory, the order the checks run in, and how an override is recorded.
- Interviews
- Interview plans, the numbered participant queue, running a session live with the elapsed timer, and how a Passed result feeds the pipeline gate.
- Endorsements and the portals
- How an application is put in front of a principal, why contact details stay hidden until selection, and precisely what the applicant and employer portals can do today.
Documents & compliance
- Documents and verification
- Uploading, the verification queue, rejection reasons, expiry handling, file storage and access control, and the limits the API enforces on every upload.
- Document type reference
- Selected document type examples for identity, qualifications, employment and workforce administration, with their stored codes, attachment scope and expiry settings.
- Audit trail
- What the append-only audit log records, the full list of canonical action names, how gate overrides are snapshotted, and the reporting that does not exist yet.
- Data privacy and retention
- Consent capture under RA 10173, the three-year retention horizon, how the nightly retention sweep behaves, and which obligations still need a manual process.
Finance
- Fees and payments
- Selected fee configuration examples, charge eligibility, payment reconciliation, receipts and the financial clearance requirements that connect finance to recruitment workflows.
Automation
- Automation rules
- The rule engine behind routing and deadline chasing: seven trigger types, eleven condition operators, seven action types, the run log, and selected default rules.
- Notifications, email and scheduled jobs
- Selected email templates, in-app notifications, staff messaging, and the five nightly sweeps that keep expiry, retention and stalled work visible.
Reference
- Stage reference
- Selected configurable workflow stages with their codes, owning roles and entry requirements, the six terminal stages, and examples of operational checklist codes.
- Glossary of statuses
- Plain-language meanings for common statuses and enumerated values in the interface, from applicant status through visa, workforce support and invoice states.
Developers
- HTTP API
- How the API authenticates with a session cookie and a CSRF header, the response envelope and error codes, transport limits, a worked create-an-applicant example, and what is not available yet.
Get help
Email support@hrteq.com for account, data and compliance questions, or info@hrteq.com for anything commercial. Toll free: +63 1800 1 550 0097.
These docs describe what is built today. Where a capability is planned rather than shipped it is called out on the page rather than implied, so you can tell the difference before you promise it to a principal.