Access status: this is a request-access preview. API keys are issued only for approved customer, partner, and automation use cases.
What you can build
RTOFlow's developer surface is designed for controlled document-generation workflows where an LMS-ready workflow, internal automation, or AI agent needs to request RTO resource drafts from a unit code.
- LMS-ready workflow integration: trigger draft resource generation when a unit or qualification is planned for delivery, then review exports before operational use.
- AI agent actions: let approved assistants request learner guide, assessment, mapping, or RPL draft jobs.
- Bulk generation pipelines: plan resource generation across a scope, qualification, or delivery stream.
- Brand-aware output: connect generated drafts to an approved organisation branding profile.
API overview
| Item | Current position |
|---|---|
| Base URL | https://api.rtoflow.au/v1 for approved preview integrations |
| Authentication | Bearer API key issued after access approval |
| Spec | Download OpenAPI YAML |
| Output status | Generated outputs are practitioner-reviewed drafts, not automatic compliance sign-off |
Core preview endpoints
| Endpoint | Method | Purpose |
|---|---|---|
/generate/learner-guide | POST | Queue a learner guide draft from a unit code. |
/generate/assessment | POST | Queue an assessment workbook draft. |
/generate/observation-checklist | POST | Queue an observation checklist draft. |
/generate/mapping-matrix | POST | Queue a mapping matrix draft. |
/generate/rpl-kit | POST | Queue an RPL evidence kit draft. |
/units/search | GET | Search unit metadata for planning workflows. |
/jobs/{job_id} | GET | Poll async generation job status. |
Quick start shape
Approved integrations use bearer-token authentication and queue asynchronous generation jobs.
curl -X POST https://api.rtoflow.au/v1/generate/learner-guide \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"unit_code":"BSBWHS411","format":"docx"}'Request access
For developer access, send your intended use case, organisation name, integration type, and expected volume to hello@rtoflow.au.
RTOFlow provides controlled preview access from this page. API keys are issued only after use-case review so customer data, model usage, and compliance workflows remain governed.
Human review requirement
RTOFlow can draft mapped training and assessment resources quickly, but qualified RTO practitioners remain responsible for review, contextualisation, validation, and final approval before use.