Resource Allocation Record Now Exposed via REST Web Services

What changed

The Resource Allocation record (record ID: resourceAllocation) is now exposed through the SuiteTalk REST web services. Previously manageable only through the UI or SuiteTalk SOAP, resource allocations can now be created, retrieved, updated, and deleted via the REST API endpoint:

/services/rest/record/v1/resourceAllocation

This is a top-level record — it is not a subrecord and has no subrecords of its own. It lets you reserve an employee's time against a specific project and, optionally, a project task.

Key fields

• allocationAmount — numeric value representing hours or percentage, depending on allocationUnit.
• allocationUnit — "H" (hours) or "P" (percentage of time).
• allocationType — e.g., "1" for Hard allocation.
• allocationResource — reference to an employee record (by internal ID).
• project — reference to the project record.
• projectTask — optional reference to a projecttask record. If set at allocation time, the resource does not need to be re-assigned to the task separately.
• approvalStatus — internal ID of the approval state (e.g., "4").
• startDate / endDate — date range for the allocation (format YYYY-MM-DD).
• requestedBy / nextApprover — employee references.
• notes — free-text field.

The response also surfaces computed fields such as numberHours and percentOfTime, which are returned regardless of which allocationUnit was used to create the record.

Code samples

Create (POST)

POST /services/rest/record/v1/resourceAllocation

Minimum payload includes allocationAmount, allocationResource, allocationUnit, startDate, endDate, and project. The allocationType, approvalStatus, projectTask, requestedBy, nextApprover, and notes fields are optional or situational.

Retrieve (GET)

GET /services/rest/record/v1/resourceAllocation/{id}

Returns the full record with linked references (employee, project, project task) including refName values and nested links arrays for related record navigation.

Prerequisites

• The Resource Allocations feature must be enabled: Setup > Company > Setup Tasks > Enable Features (Administrator), on the Company subtab.
• The calling integration must have appropriate REST API permissions to the resourceAllocation record type.

What to do

1. Check feature enablement. Confirm that Resource Allocations is turned on in your target account before attempting REST calls.
2. Review the REST API Browser. Consult the resourceAllocation reference page in the REST API Browser for the complete list of supported HTTP methods (POST, GET, PATCH, DELETE), query parameters, and field definitions. Oracle's source does not enumerate every supported operation inline.
3. Update integrations. If you have existing SOAP-based or CSV-import workflows that manage resource allocations, you can now migrate them to REST. The record ID is resourceAllocation — use it in SuiteQL queries (SELECT * FROM resourceAllocation) and in REST endpoints.
4. Handle approval workflows. The approvalStatus and nextApprover fields indicate that approval routing applies. If your account uses resource allocation approvals, test that creating allocations via REST correctly triggers the approval chain.
5. Validate computed fields. The API returns both numberHours and percentOfTime on retrieval regardless of the input unit. If your integration consumes these, confirm the values align with your scheduling logic.