# Project Creation API in Oracle Fusion

> Source: https://netray.co/erp-help/project-creation-api-in-oracle-fusion
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

Oracle Fusion Cloud creates projects through the Project Management REST API: a POST to the projects resource under /fscmRestApi/resources/ with a JSON body naming the project, number, organization, legal entity, project unit and usually a source template. Tasks, team members and classifications are then added through child resources of the new project.

## Kind

how-to

## System

oracle-fusion

## Erp

Oracle Fusion Cloud Project Management

## Module

Project Management / REST API

## Query

project creation api in oracle fusion

## Alternate Queries

- oracle fusion create project rest api
- project api in oracle fusion
- oracle fusion projects POST payload
- create project from template fusion rest

## Applies To

Oracle Fusion Cloud Project Management (Project Financial Management), REST API version path as published for your release, such as 11.13.18.05

## Steps

### How to create a project with the Fusion REST API

**Items:**

Create an integration user and give it a job role that carries project creation privileges, such as Project Application Administrator or a custom role copied from Project Manager. Without it you get 403 or an empty list.

Identify the setup values you must send by name or ID: project unit, organization, legal entity and the source project template. Look them up with GET calls on the matching REST resources or in Setup and Maintenance.

Open the REST API for Oracle Fusion Cloud Project Management guide for your release and confirm the exact attribute names of the projects resource, because they differ slightly between releases.

POST to /fscmRestApi/resources/<version>/projects with Content-Type application/json and basic or OAuth/JWT authentication.

Read the response: it returns the generated ProjectId and the created project record. Store ProjectId for follow-up calls.

Add tasks with POST to /projects/{ProjectId}/child/Task, and team members with the ProjectTeamMember child resource, if the template does not already supply them.

Verify in the UI under Project Management > Project Financial Management > Manage Project, then check the project status and that the project unit security lets the intended users see it.

## Sections

### A minimal request

**Body:**

A typical request creates the project from a template so that tasks, classifications, burden schedules and the project type are inherited instead of repeated in the payload. The attribute names below follow the project resource as commonly documented; treat them as a starting point and validate against the describe endpoint of your own pod.

Use the describe call (append /describe to the resource URL) to see every attribute, which are required, and which child resources exist. That is faster and more reliable than any blog post, including this one, because Oracle adds attributes each quarterly update.

**Code:**

POST https://<pod>.fa.<region>.oraclecloud.com/fscmRestApi/resources/11.13.18.05/projects
Content-Type: application/json

{
  "ProjectName": "Line 4 Retrofit",
  "ProjectNumber": "PRJ-2026-0412",
  "SourceTemplateNumber": "CAPEX_STD",
  "OrganizationName": "Plant 2 Operations",
  "LegalEntityName": "Example Manufacturing Inc",
  "ProjectUnitName": "North America Projects",
  "StartDate": "2026-11-01",
  "FinishDate": "2027-03-31",
  "Description": "Retrofit of assembly line 4"
}

GET .../fscmRestApi/resources/11.13.18.05/projects/describe

### Templates, tasks and child resources

**Body:**

Creating a project without a template means you must also send the project type-driven defaults yourself, and most integrations fail on missing required fields because of that. Keep a small set of templates per project type and let the API pick one by number.

Child resources such as Task, ProjectTeamMember and ProjectClassification are written either inline in a deep-insert payload or with separate POSTs. Separate POSTs are easier to retry and debug when one task fails validation. For bulk loads of hundreds of projects, the File-Based Data Import for projects is usually faster than one REST call per record.

### Errors you will meet

**Body:**

A 400 with a message that a value is invalid almost always means a name did not resolve: the organization is not a project-owning organization, the legal entity is not assigned to the project unit, or the template is not active for that unit. A 401 means the credentials or token are wrong, a 403 means the role lacks the privilege or the data security scope.

A duplicate project number returns a validation error. If your numbering is automatic in setup, omit ProjectNumber and read it back from the response instead of generating your own.

## Pitfalls

- Copying attribute names from an older release and getting silent ignores or 400 errors. Always check the /describe output for your pod.
- Using a personal user for the integration. Password resets and role changes will break the job. Use a dedicated service user.
- Sending organization or template display names that differ by a trailing space or case from setup.
- Skipping the project unit, which controls who can see and edit the project through data security.
- Creating thousands of projects serially through REST instead of using file-based import for bulk migration.

## Ai Angle

A grounded assistant can read the /describe metadata of your pod, show which attributes are required for your template and generate a correct payload from a plain request such as 'new capex project for line 4'. With a private deployment it does this without sending your project data outside your network, and any POST stays behind human approval.

## Faq

### What is the endpoint to create a project in Oracle Fusion?

**Answer:** It is a POST to the projects resource of the Fusion REST API, under /fscmRestApi/resources/<version>/projects. The version segment depends on your release, so read it from the REST API guide or from your pod's describe endpoint rather than assuming one.

### Do I need a template to create a project through the API?

**Answer:** Strictly it depends on setup, but in practice yes. A source template supplies the project type, tasks, burden and other defaults, which keeps the payload small and consistent. Without one you must provide many more attributes.

### Can I add tasks in the same call?

**Answer:** Fusion supports deep insert for child resources in many cases, but separate POSTs to the Task child resource are easier to retry and debug. Inheriting tasks from a template avoids the question entirely.

### Which role do I need?

**Answer:** A job role with the project creation and management privileges, such as Project Application Administrator or a custom role copied from Project Manager, plus data security access to the project unit and organization.

## Search terms

oracle fusion project creation api, fusion projects rest api, fusion create project rest, oracle fusion project management rest api, fscmRestApi projects, project api oracle fusion, oracle fusion project template api, fusion ppm rest

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json
