Developer Portal
 Developer Portal

PRODUCT DATA SHEET

Modern Awards APIs

Last Updated: December 2025

1. PRODUCT SUMMARY

Name: Intaxio Modern Awards APIs
SKU: [e.g. IA-MOD-AWARDS-STD]

Description: API-based access to configuration, classification structures, pay rates, allowances, penalty rules and related parameters for Australian Modern Awards, aligned with determinations and documentation published by the Fair Work Commission (FWC).

The Modern Awards APIs are designed to be embedded into payroll, workforce management and HR platforms to automate award interpretation and calculation logic.

2. KEY CAPABILITIES

  • Award Catalogue
    • Machine-readable representation of covered Modern Awards, including award codes and titles, coverage, industry and occupational scope, and operative dates / versions.
  • Classification Structures
    • Hierarchies of levels, streams and employment types (for example, full-time, part-time, casual).
  • Pay Rates
    • Minimum pay rates for each classification and employment type, including base hourly/weekly rates, age-based or competency-based differentials where applicable, and casual loadings.
  • Allowances
    • Definitions and parameters for award-specific allowances (for example, travel, tools, first aid).
  • Penalty and Overtime Rules
    • Rules for penalty rates for evenings, weekends, public holidays; overtime triggers and rates; minimum shift engagements and broken shifts (where applicable).
  • Working Time Rules
    • Maximum ordinary hours, breaks, rostering rules, and spread of hours parameters to support downstream calculation engines.
  • Metadata and Versioning
    • Effective dates, superseded versions, references to FWC decisions/determinations for traceability.

3. DATA SOURCES AND UPDATE POLICY

3.1 Primary Source

FWC-published awards content, including consolidated modern awards, determinations, variation decisions, and associated guidance where applicable.

3.2 Update Triggers

The Modern Awards APIs are updated when:

  • FWC publishes its Annual Wage Review decisions/variations;
  • FWC issues variations to specific awards (for example, industry-specific changes); and
  • FWC or government publishes other changes that impact minimum rates, penalty structures, allowances or key parameters.

3.3 Update Timeframes (Example Targets)

These example targets can be adjusted to reflect operational reality:

  • Annual Wage Review – general increases: new minimum rates for covered Modern Awards reflected in production within 5 Business Days of the relevant FWC consolidated award/determination becoming available in a stable form suitable for implementation.
  • Other award variations with prospective effect: changes reflected in production within 10 Business Days of the relevant FWC materials being available in a stable form.

3.4 Retrospective Changes

  • Where FWC issues retrospective or backdated changes, Intaxio will reflect the updated rules in the Modern Awards APIs for the effective periods within a commercially reasonable timeframe given complexity.
  • Intaxio is not responsible for reprocessing historical payroll or for any business or compliance decisions made by Customer before those retrospective changes were published or implemented.

3.5 Data Quality and Warranties

  • For production SKUs, and subject to the Customer API Agreement, Intaxio warrants that award minimum rates, allowances and penalty data exposed via the Modern Awards APIs are consistent with the underlying FWC source materials and guidance at the time they are implemented, and that updates are applied in accordance with the timeframes above (or, where not feasible, with reasonable effort and communication).

4. ENVIRONMENTS AND DATA PACKS

4.1 Production Environment

  • Full, current Modern Awards data for the licensed set of awards.
  • Subject to SLA and service-specific warranties.

4.2 Non-Production / Test Environment (if provided)

  • May contain a subset of awards, synthetic or obfuscated data, or earlier snapshots for testing.
  • Test data is not warranted for correctness or completeness and must not be used for live payroll or compliance decisions.

4.3 Test and Enablement Data Packs

  • Designed for implementation, QA, and demonstration, for use in sandbox / staging environments.
  • Excluded from formal SLA commitments and from the service-specific warranties on data correctness.

5. API INTERFACES AND LIMITS

5.1 API Style

REST-style JSON APIs (or equivalent), documented in the Developer Portal. Example patterns (illustrative only; actual endpoints may differ):

  • /awards – list and search awards;
  • /awards/{awardId} – retrieve a specific award;
  • /awards/{awardId}/classifications – retrieve classification structures;
  • /awards/{awardId}/rates – retrieve pay rates for given date, classification and employment type;
  • /awards/{awardId}/penalties and /awards/{awardId}/allowances – retrieve relevant rules and parameters.

5.2 Rate Limits and Quotas (Illustrative)

Default tenant-level limits (per production tenant, unless otherwise specified in the Order Form):

  • Up to 100 requests per second sustained;
  • Up to 500,000 requests per day.

Different limits may be agreed in the Order Form for higher tiers or dedicated capacity. Rate limits for non-production environments may be lower.

5.3 Payload Size and Pagination

  • API responses may be paginated where result sets are large (for example, listing awards or classification tables).
  • Specific pagination parameters are documented in the Developer Portal.

6. DEPENDENCIES AND CUSTOMER RESPONSIBILITIES

6.1 Dependencies

Modern Awards APIs assume that Customer:

  • correctly maps its employees to the appropriate award and classification;
  • supplies the correct effective date and relevant parameters when requesting rate or rule data;
  • integrates the API outputs into its own calculation logic or payroll engine in accordance with the API specifications.

6.2 Customer Responsibilities

  • validate the integration in its own environment before relying on it in production;
  • ensure it has obtained any necessary legal, HR or tax advice about its obligations;
  • apply the API data correctly to its specific employment arrangements and contracts; and
  • comply with all applicable laws and industrial instruments.

7. LOGS, MONITORING AND AUDIT

  • Intaxio logs API calls (endpoint, timestamps, response status), authentication events, and changes to configuration at the Developer Portal level (for example, API keys, webhooks).
  • Logs are used for operational support and troubleshooting, security monitoring and incident investigation, and limited analytics and capacity planning.
  • Retention periods are as described in the Security Overview and may be adjusted for operational or legal reasons.

8. VERSIONING, DEPRECATION AND BACKWARDS COMPATIBILITY

8.1 Versioning

  • Modern Awards APIs are versioned (for example, v1, v2) to manage non-backwards- compatible changes.

8.2 Minor Changes

  • Backwards-compatible changes (for example, new optional fields, new awards) may be introduced without a major version increment.

8.3 Deprecation Policy

  • When Intaxio intends to deprecate a major version, it will notify customers via the Developer Portal and/or email and provide a reasonable migration period (for example, at least 6 months) before retirement of the deprecated version, unless required to accelerate by law or regulator.

9. COMMERCIAL MODEL (HIGH LEVEL)

Actual pricing and commercial terms for the Modern Awards APIs are specified in the relevant Order Form or pricing schedule. Typical components include:

  • Base subscription – access to a defined set of Modern Awards APIs, a baseline usage allowance and standard support.
  • Add-ons (optional) – coverage of additional awards or industries, higher rate limits or dedicated capacity, enhanced support (for example, extended hours, priority routing) and implementation/consulting services.