Skip to main content
Question

How to trigger approval workflow when creating a record via REST API?

  • April 27, 2026
  • 3 replies
  • 63 views
H
Data Voyager

Hello, I'm working on a MDM project and need help with workflow-governed record creation via the REST API.

I have an integration where record creation requests come in from a third party application with the required record details.
I pick up those details and use them to create a new master record in MDM via POST /api/rest/master/{viewName}/{typeName}
Currently the record gets created and published immediately, completely bypassing the workflow.
What I actually need is for this record creation to go through the workflow, meaning it should create a task in draft state with the actual record details, and then go through the configured approval workflow steps before being published.

Is there a way to achieve this via the REST API? Any workarounds or approaches others have used for this would be really helpful.

 

3 replies

Ales
Ataccamer
Forum|alt.badge.img+2
  • AlesAtaccamer
  • Ataccamer
  • May 26, 2026

Hi ​@Harsh , 

have you tried to create a task using this endpoint:

https://docs.ataccama.com/mdm/16.3.0/configuration/rest-api.html#create-multiple-tasks

Ales

 

Ales
H
Data Voyager
  • HarshData Voyager
  • Author
  • Data Voyager
  • June 11, 2026

Hi ​@Ales, thanks for the suggestion!

I did look into POST /api/rest/v2/tasks but I think the request body there expects IDs of records that already exist in MDM so it can link an existing record to a task, but it can't create a new record as a draft inside the task. What I actually need is for the incoming record data to be staged as a draft within the task like when you create a record manually in the web app and it shows task of type Create with the actual record details staged as a draft, which a reviewer can then approve before it gets published.

 

Ales
Ataccamer
Forum|alt.badge.img+2
  • AlesAtaccamer
  • Ataccamer
  • June 22, 2026

Hi ​@Harsh, I see. I don’t think there is a native API which could be used for your case then. 

Thinking about this workaround:

Create master first, then immediately create a change task (if “record exists but not yet approved” is acceptable)
  • Create master record via REST (as today).
  • Immediately create a RECORD_CHANGE task for that record and require workflow approval before it’s considered “usable”.
 
This is of course not the same as “create-as-draft” (because the record exists in master), but you can combine it with permissions/visibility rules so unapproved records at least don’t appear in normal views.
 
I’m afraid this is the best I can think of at the moment. 
Ales
Ales
Community Terms of Use & ConditionsAccessibility statement