projects/{projectId}/items/{itemId}:transition

Transitions a submittal item to a specified state in the submittal workflow, allowing it to progress according to the defined process. This transition is determined based on its current state and the permitted actions, such as moving an item from Draft to Submitted or from In Review to Closed.

To identify permitted transitions and required fields, call GET Item/:id.

If the submittal workflow includes predefined steps and tasks, these are managed through templates. Templates define the sequence of required actions and roles in the review process. You can create templates in the UI and retrieve them programmatically by calling GET Templates. When transitioning an item, ensure that it aligns with the steps and constraints set in the associated template.

For more infomration about transitions, see the Manage Submittal Item Transitions tutorial.

For information about submittals and their lifecycle, see the Help documentation.

Note that this endpoint is not compatible with BIM 360 projects.

Resource Information

Method and URI	POST https://developer.api.autodesk.com/construction/submittals/v2/projects/:projectId/items/:itemId:transition
Authentication Context	user context required
Required OAuth Scopes	`data:write`
Data Format	JSON

Request

Headers

Authorization* string	Must be `Bearer <token>`, where `<token>` is obtained via a three-legged OAuth flow.
Content-Type* string	Must be `application/json`

* Required

Request

URI Parameters

projectId string: UUID	The ID of the project. Use the Data Management API to retrieve the project ID. For more information, see the Retrieve a Project ID tutorial. You need to convert the project ID into a project ID for the ACC API by removing the “b." prefix. For example, a project ID of b.a4be0c34a-4ab7 translates to a project ID of a4be0c34a-4ab7.
itemId string	The ID of the submittal item. To find the item ID, call GET items.

Request

Body Structure

Expand all

customIdentifier string	A custom number to assign to the submittal item. Before updating an item, check what the custom numbering type is for the current project by calling GET metadata to get the custom identifier sequence type. Submittals support two custom numbering types: Global Numbering: The custom identifier only contains the sequential number. Spec Section Numbering: When the project uses spec section numbering for custom numbering, ensure that only the sequential number part of the custom identifier is sent in the request, excluding the spec ID. To find the next available custom number in the sequence, call GET items:next-custom-identifier. To verify whether the custom number has not been used and is in a supported format, call POST items:validate-custom-identifier. For more information on custom numbering, see the Help documentation.
typeId string: UUID	The ID of the item type to assign to the submittal item. To retrieve the type ID, call GET item-types or GET item-types/:id.
specId string: UUID	The unique identifier (UUID) of the spec section to assign to the submittal item, which can be obtained by calling GET specs.
subsection string	Define the subsection details of the submittal item. For example, `1.05-B`.
title string	The title of the submittal item defined by the user when updating the submittal item.
description string	A description of the submittal item to add context about its purpose.
priority enum:string	The priority level of the submittal item. Possible values: `Low` `Normal` `High` When the priority is not set, the default value is `Normal`.
manager string	The Autodesk ID (`autodeskId`) or Group ID (`memberGroupId`) specifying the manager to assign to the submittal item. The manager could be a user, role, or a company. Note that the user must be defined as a manager in the project. You can verify this by calling GET mappings. To get the possible values for a manager, call GET mappings and check the autodeskId. This returns a list of all the users, roles, and companies that are managers in the project. Call GET projects/users to verify the actual name of the user. If a copmany is a manager, call GET companies to verify the actual name of the company. Note that we do not currently support verifying names of roles.
managerType enum:string	The type of manager. This attribute is required when a manager is specified. To determine the type of manager, call GET mappings and check the user type. Possible values: `1` (user), `2` (company), `3` (role).
subcontractor string	The Autodesk ID of the subcontractor to assign to the submittal item. When updating a submittal item as a manager in the UI, you will see ‘assign to responsible contractor’. The subcontractor can be a user (`autodeskId`), role (`memberGroupId`), or company (`memberGroupId`). For users, call GET users. For companies, call GET companies. Note that we do not currently support finding details about roles for a project.
subcontractorType enum:string	The type of subcontractor. This attribute is required when a subcontrator is specified. Possible values: `1` (user), `2` (company), `3` (role).
sentToSubmitter datetime: ISO 8601	The date and time when the submittal was sent to the subcontrator for review, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
receivedFromSubmitter datetime: ISO 8601	The date and time when the submittal was received back from the subcontractor after review, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
sentToReview datetime: ISO 8601	The date and time when the submittal item was transitioned to the `rev` state `(Open - In review)`, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
receivedFromReview datetime: ISO 8601	The timestamp marking when the item transitioned from the `rev` state `(Open - In Review)` to the `mgr-2` state `(close and distribute)`, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
publishedDate datetime: ISO 8601	The date when the manager closed and distributed the submittal item, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
watchers array: object	A list of project watchers, who can be individual users, roles, or companies.
id* string	The Autodesk ID of the watcher. The watcher can be a user (`autodeskId`), role (`memberGroupId`), or company (`memberGroupId`). To find details about users, call GET users, to find details about companies, call GET companies. Note that we do not currently support finding details about roles for a project.
userType* object	The type of watcher assigned to the submittal item. Possible values: `1` (user) `2` (company) `3` (role)
requiredOnJobDate string	The date when the materials are expected to arrive on the site, in the following format: YYYY-MM-DD (ISO 8601) in UTC. For example, `2018-02-15`.
leadTime int	The duration (in days) from the approval of the submittal to the delivery of materials or products to the construction site.
requiredDate string	The date the responsible contractor needs to submit the submittal to the submittal manager, in the following format: YYYY-MM-DD (ISO 8601) in UTC. For example, `2018-02-15`.
requiredApprovalDate string	The date by which approval for the submittal is required, in the following format: YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`.
submitterDueDate string	The date by which the subcontractor is expected to submit the submittal to the manager, formatted as YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`.
managerDueDate string	The date by which the manager is expected to prepare the submittal item for review to the reviewer, in the following format: YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`.
packageId string: UUID	The ID of the package associated with the submittal item. This attribute is optional and is used for workflows involving attachments. To retrieve package details, call GET packages.
stateId* enum:string	Specifies the target state to which the submittal item will transition according to the user’s permitted actions. To determine available transitions, call GET Item/:id and check the `permittedActions` field. Note that submittal items cannot be transitioned to a `draft - (Draft)` state, only from a `draft - (Draft)` state to another state. To transition a submittal item to a `rev - (Open - In Review)` state, the associated template must include predefined steps and tasks, and a custom identifier must already be set. See the Create Submittal Items tutorial (step 6) for more details. Possible values: `sbc-1` (Waiting for Submission) – Assigned to the Responsible Contractor, who needs to submit the submittal to the Manager. `mgr-1` (Open - Submitted) – Assigned to the Manager, who needs to prepare it for review. `rev` (Open - In Review) – Under review by the reviewers defined in the submittal workflow. `mgr-2` (Open - Reviewed) – The review is complete, and the submittal is returned to the Manager, who needs to set the final response and close the submittal. `sbc-2` (Closed) – The submittal has been closed and assigned to the Responsible Contractor. `void` (Voided): The item has been voided.
mailNote string	A note (comment) that is used in transition and will be sent in email and appear in the activity log.
stepDueDate string	The due date for the next Step in ISO 8601, in the following format YYYY-MM-DD in UTC. For example, `2024-02-15`. This is relevant only when transitioning to a `rev` state (equivalent to `Open (In review)` in the UI).
responseId string	The ID of the response associated with the transition, linking to the specific feedback or action taken. This is relevant only when transitioning to the `sbc-2` state (equivalent to Closed in the UI). To find the response ID, call GET Responses.
responseComment string	The body of the response comment, containing feedback or instructions related to the transition. This is relevant only when transitioning to the `sbc-2` state (equivalent to Close and Distribute in the UI).
saveAttachmentDrafts array: string	Not relevant
duplicateAttachments array: string	A list of attachment IDs to duplicate from a submittal item’s previous stage in the workflow. To retrieve available attachments, call GET items/:itemId/attachments.

* Required

Response

HTTP Status Code Summary

200 OK	Successfully transitioned the submittal item to a new state.
400 Bad Request	The request could not be understood by the server due to malformed syntax or missing request headers.
401 Unauthorized	Invalid or missing authorization header. Verify the Bearer token and try again.
403 Forbidden	The user is not authorized to perform this action.
404 Not Found	The specified resource was not found.
500 Internal Server Error	An unexpected error occurred on the server while processing the request.

Response

Body Structure (200)

Expand all

id string: UUID	The internal, globally unique identifier (UUID) for the submittal item.
identifier int	The unique ID assigned to the submittal item within the UI. This ID is system-generated and serves as a reference for users interacting with submittal items through the UI. For example, `111`.
customIdentifier string	`customIdentifier` and `customIdentifierHumanReadable` relate to the `Number` column in the UI. Submittal managers assign custom numbers to items (manually or automatically). Custom numbers are configured either in global numbering format: <global number>, or in spec section numbering format: <spec ID>-<sequential number>. For projects with a global numbering format, both `customIdentifier` and `customIdentifierHumanReadable` represent the global number. For projects with a spec section numbering format (<spec ID>-<sequential number>), `customIdentifier` represents the sequential number. For example, for a full number of `033100-01`, `customIdentifier` is `01`. Note that for unnumbered items `customIdentifier` is `null`. For more information on custom numbering, see the Help documentation.
customIdentifierHumanReadable string	`customIdentifierHumanReadable` and `customIdentifier` relate to the `Number` column in the UI. Submittal managers assign custom numbers to items (manually or automatically). Custom numbers are configured either in global numbering format: <global number>, or in spec section numbering format: <spec ID>-<sequential number>. For projects with a global numbering format, both `customIdentifier` and `customIdentifierHumanReadable` represent the global number. For projects with a spec section numbering format (<spec ID>-<sequential number>), `customIdentifierHumanReadable` represents the full number - both the spec ID and the sequential number. For example, for a full number of `033100-01`, `customIdentifierHumanReadable` is `033100-01`. Note that for unnumbered items `customIdentifierHumanReadable` is `Unspecified`. For spec section numbering it also includes the spec ID. For example, `033100-Unspecified`. For more information on custom numbering, see the Help documentation.
typeId string	The ID representing the type of submittal item.
specId string: UUID	The unique identifier (UUID) of the spec assigned to the submittal item.
specIdentifier string	The identifier of the spec section that is associated with the submittal item. The identifier is assigned to the spec section in the UI.
specTitle string	The title of the spec associated with the submittal item.
subsection string	The sub-spec section associated with the submittal item, providing additional categorization within the main spec.
title string	The title of the submittal item.
description string	The description of the submittal item.
priority enum:string	The priority of the submittal item. Possible values: `Low` `Normal` `High`
revision int	The revision number of the submittal item, indicating the version of the item in the submittal workflow. For example, `1` for the initial submission or `2` for the first revision.
stateId enum:string	The current state of the submittal item after the transition. Possible values: `sbc-1` (Waiting for Submission) - Assigned to the Responsible Contractor, who needs to submit the submittal to the Manager. `mgr-1` (Open - Submitted) - Assigned to the Manager, who needs to prepare the submittal item for review. `rev` (Open - In Review) - Under review by the reviewers defined in the submittal item’s review workflow. `mgr-2` (Open - Reviewed) - The review is complete, and the submittal is returned to the Manager, who needs to set the final response and close the submittal. `sbc-2`: (Closed) - The submittal has been closed and assigned to the Responsible Contractor. `void` (Voided) - The submittal item has been voided. `draft` (Draft) - Assigned to the Manager, who must send the submittal item to the Responsible Contractor.
statusId enum:string	The status of the submittal item. Possible values: `1` - (Required), `2` - (Open), `3` - (Closed), `4` - (Void), `5` - (Empty), `6` - (Draft). To retrieve the full list of possible statuses, call GET metadata.
ballInCourtUsers array: string	The Autodesk IDs of users who are currently assigned to the submittal item at this stage of the workflow.
ballInCourtCompanies array: string	The member group IDs of the companies currently assigned to the submittal item at this stage of the workflow.
ballInCourtRoles array: string	The member group IDs of user roles that are currently assigned to the submittal item at this stage of the workflow.
ballInCourtType enum:string	‘The type of submittal role assigned to the user currently assigned to the submittal item. Possible values: `reviewer`, `manager`, `subcontractor`.’
manager string	The ID that was assigned to the manager of the submittal item. To determine the type of the manager (user, role, or company), refer to the manager type (`managerType`) attribute. In order to get more info about the manager, use: GET projects/users to verify the actual name of the user in case the typs is a `user` (1). GET companies to determine the name of the company in case the typs is a `company` (2). Note that we do not currently support verifying names of roles.
managerType enum:string	The type of manager associated with the submittal item. Possible values: `1` (user), `2` (company), `3` (role).
subcontractor string	The ID that was assigned to the subcontractor for the submittal item. If a non-manager user created the submittal item and chose a manager, they are automatically assigned as the `subcontractor` of the submittal item. In order to get more info about the subcontractor, use: GET projects/users to verify the actual name of the user in case the typs is a `user` (1). GET companies to determine the name of the company in case the typs is a `company` (2). Note that we do not currently support verifying names of roles.
subcontractorType enum:string	The type of subcontractor associated with the submittal item. Possible values: `1` (user), `2` (company), `3` (role).
watchers array: object	A list of project watchers, who can be individual users, roles, or companies.
id string	The Autodesk ID of the watcher. The watcher can be a user (`autodeskId`), role (`memberGroupId`), or company (`memberGroupId`). To find details about users, call GET users, to find details about companies, call GET companies. Note that we do not currently support finding details about roles for a project.
userType object	The type of watcher assigned to the submittal item. Possible values: `1` (user) `2` (company) `3` (role)
dueDate string	The due date for the submittal item, formatted as YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`.
requiredOnJobDate string	The date when the materials are expected to arrive on the construction site, formatted as YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`.
leadTime int	The duration (in days) from the approval of the submittal to delivery of materials or products to the construction site.
requiredDate string	The date by which the Responsible Contractor must submit the submittal to the submittal manager, formatted as YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`.
requiredApprovalDate string	The date by which approval for the submittal is required, formatted as YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`.
submitterDueDate string	The date by which the subcontractor is expected to submit the submittal to the manager, formatted as YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`. This corresponds to the `sbc-1` state `Waiting for submission`.
sentToSubmitter datetime: ISO 8601	The date and time when the submittal was sent to the subcontractor for review, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`. This corresponds to transition to the `sbc-1` state.
receivedFromSubmitter datetime: ISO 8601	The date when the submittal was received back from the subcontractor after review, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`. This corresponds to transition to `mgr-1` state `Open (Submitted)`.
submittedBy string	The Autodesk ID of the user who submitted the submittal item. This is the user who transitioned the item to the manager.
managerDueDate string	The date by which the manager is expected to prepare the submittal item for review, formatted as YYYY-MM-DD in UTC (ISO 8601). For example, `2018-02-15`. This corresponds to the `mgr-1` state `Open (Submitted)`.
sentToReview datetime: ISO 8601	The date and time when the submittal item transitioned to the `rev` state `(Open - In review)`, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
sentToReviewBy string	The Autodesk ID of the user who transitioned the item to the `rev` state `(Open - In review)`.
receivedFromReview datetime: ISO 8601	The date and time when the submittal item transitioned from the `rev` state `(Open - In Review)` to the `mgr-2` state `(Close and distribute)`, formatted as YYYY-MM-DD (ISO 8601) in UTC. For example, `2022-03-02T12:09:24Z`.
publishedDate datetime: ISO 8601	The date when the manager closed and distributed the submittal item, in the following format: YYYY-MM-DD (ISO 8601) in UTC. For example, `2018-02-15`.
publishedBy string	The Autodesk ID of the user who published the submittal item.
responseId string	The ID of the response associated with the submittal item, linking to the specific feedback or action taken.
responseComment string	The body of the response comment, containing feedback or instructions related to the submittal item.
respondedAt datetime: ISO 8601	The date and time when the response was added, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
respondedBy string	The Autodesk ID of the user that gave the response to the submittal item.
packageId string: UUID	The ID of the package associated with the submittal item.
packageIdentifier string	The package identifier as displayed in the UI.
packageTitle string	The title of the package associated with the submittal item.
packageSpecIdentifier string	The identifier of the submittal spec associated with the package. This value corresponds to the “Spec section” displayed in the UI, such as `1 - Cement`.
folderUrn string	The URN of the folder that contains the attachments associated with the submittal items.
revisionsFoldersUrns object	An object containing URNs that represent folders associated with the revisions of the submittal item. These URNs can be used to access and identify specific folders related to submittal item revisions within the system.
createdAt datetime: ISO 8601	The date and time when the submittal item was originally created, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
createdBy string	The Autodesk ID of the user who created the submittal item.
updatedAt datetime: ISO 8601	The time and date when the submittal item was last updated, formatted as YYYY-MM-DDTHH:mm:ss.SSSSSSZ (ISO 8601) in UTC. For example, `2018-02-15T12:09:24.198466Z`.
updatedBy string	The Autodesk ID of the user who last updated the submittal item.
permittedActions array: object	The list of actions the user is allowed to perform on the submittal item.
id string	The ID of the action in the format `type_of_object::action`. For example, `Item::retrieve`.
fields object	A list of field names for which values must be provided when performing the action. An empty array indicates no specific set of values.
mandatoryFields array: string	Lists the fields that are required when updating a submittal item. The required fields depend on the action being performed, the item’s current state, and the user’s role. For example: To transition the state of a submittal item, `stateId` and `responseId` are required. To reassign the manager, `manager` and `managerType` are required. To modify the spec section, `specId` is required.
transitions array: object	The list of possible state transitions for a submittal item within the review workflow.
id string	The ID of the transition in the format `from-state::to-state`. For example, `create::mgr-1`, `mgr-1::mgr-2`, `rev::void`.
name string	The descriptive name of the transition. For example, `Create`, `Send to Manager`, `Send to void`.
stateFrom object	The starting state of the transition, representing the current position of the submittal item in the workflow.
id string	The unique ID of the starting state. For example, `create`, `mgr-1`, `rev`. The `rev` state indicates that the submittal item is currently under review.
name string	The name of the starting state. For example, `Create`, `Manager Review`, `Review`.
stateTo object	The target state of the transition, indicating the next position of the submittal item in the workflow.
id string	The unique ID of the target state. For example, `mgr-1`, `mgr-2`, `void`.
name string	The name of the target state. For example, `Manager Review`, `Manager Final Review`, `Void`.
transitionFields array: string	Fields that are used in the transition. For example, [`subcontractor`, `subcontractorType`, `watchers`, `responseId`].
mandatoryFields array: string	A list of required fields for the transition. For example, [`responseId`].
actionId string	Not relevant

Example

Successfully transitioned a submittal item to a new state

Request

curl -v 'https://developer.api.autodesk.com/construction/submittals/v2/projects/9eae7d59-1469-4389-bfb2-4114e2ba5545/items/767b5888-2c6a-413d-8487-613966dd64ce:transition' \
-X 'POST' \
-H 'Authorization: Bearer AuIPTf4KYLTYGVnOHQ0cuolwCW2a' \
-H 'Content-Type: application/json' \
-d '{
      "customIdentifier": "A-111",
      "priority": “High”,
      "manager": "WD43ZJGKDFLFH",
      "managerType": "1",
      "leadTime": 100,
      "stateId": "mgr-1",
      "mailNote": "Transitioning to manager review.",
      "stepDueDate": "2024-02-15”,
      "duplicateAttachments": [
        "f572d479-ede1-4654-a895-f669c2639b26",
        "06b3d2b0-bd5a-4aa2-b35f-4ae55fe8fd5d"
      ]
    }'
Show More

Response

{
 "id":"b8cc9324-6759-4f07-8ce3-725d5afd4f11",
 "identifier":1111,
 "customIdentifier":"A-111",
 "customIdentifierHumanReadable":"0001-A-111",
 "typeId":"06fa0c1b-6462-459d-8a38-0aff11bfe868",
 "specId":"62d6f245-b470-4af4-802b-4cb94b5dead1",
 "specIdentifier":"09-5300",
 "specTitle":"Acoustical Ceilings",
 "subsection":"1.05-B",
 "title":"Shop Drawings",
 "description":"Detailed plans by subcontractor, showing project dimensions.",
 "priority":"High",
 "revision":0,
 "stateId":"mgr-1",
 "statusId":"2",
 "ballInCourtUsers":[
    "WD43ZJGKDFLFH"
 ],
 "ballInCourtCompanies":[
    "WD43ZJGKDFLFH"
 ],
 "ballInCourtRoles":[
    "WD43ZJGKDFLFH"
 ],
 "ballInCourtType":"manager",
 "manager":"WD43ZJGKDFLFH",
 "managerType":"1",
 "subcontractor":"WD43ZJGKDFLFH",
 "subcontractorType":"1",
 "watchers":[
    {
       "id":"224356",
       "userType":"2"
    },
    {
       "id":"3522614",
       "userType":"3"
    }
 ],
 "dueDate":"2024-02-15",
 "requiredOnJobDate":"2024-02-15",
 "leadTime":100,
 "requiredDate":"2024-02-15",
 "requiredApprovalDate":"2024-02-15",
 "submitterDueDate":"2024-02-15",
 "sentToSubmitter":"2024-02-01T12:09:24.198466Z",
 "receivedFromSubmitter":"2024-02-01T12:09:24.198466Z",
 "submittedBy":"WD43ZJGKDFLFH",
 "managerDueDate":"2024-02-15",
 "sentToReview":"",
 "sentToReviewBy":"",
 "receivedFromReview":"",
 "publishedDate":"",
 "publishedBy":"",
 "responseId":"",
 "responseComment":"",
 "respondedAt":"",
 "respondedBy":"",
 "packageId":"e8302552-fc5a-42ac-ba4b-e9de9760c356",
 "packageIdentifier":"222",
 "packageTitle":"my package1",
 "packageSpecIdentifier":"A-500",
 "folderUrn":"urn:adsk.wipprod:fs.file:vf.hvNfeldTPm_aDqRNZgKjD",
 "revisionsFoldersUrns":{
    "0":{
       "folderUrnCreatedAt":"2024-01-28 09:26:36.371607",
       "revision":0,
       "folderUrn":"urn:adsk.wipprod:fs.folder:co.r04fl5B7QCa1731EeH5dYDQ"
    }
 },
 "createdAt":"2024-02-01T12:09:24.198466Z",
 "createdBy":"WD43ZJGKDFLFH",
 "updatedAt":"2018-04-04T12:09:24.198466Z",
 "updatedBy":"WD43ZJGKDFLFH",
 "permittedActions":[
    {
       "id":"Item::retrieve",
       "fields":{

       },
       "mandatoryFields":[
          ""
       ],
       "transitions":[
          {
             "id":"mgr-1::void",
             "name":"Send to void",
             "stateFrom":{
                "id":"mgr-1",
                "name":"MGR-1"
             },
             "stateTo":{
                "id":"void",
                "name":"VOID"
             },
             "transitionFields":[

             ],
             "mandatoryFields":[

             ],
             "actionId":"ITEM_TRANSITION_MGR-1_VOID"
          }
       ]
    }
 ]
}
Show More

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Request

Response

Jump To

projects/{projectId}/items/{itemId}:transition

Resource Information

Request

Headers

Request

URI Parameters

Request

Body Structure

Response

HTTP Status Code Summary

Response

Body Structure (200)

Example

Request

Response

Cookie preferences

Strictly necessary – required for our site to work and to provide services to you

Improve your experience – allows us to show you what is relevant to you

Customize your advertising – permits us to offer targeted advertising to you

Strictly necessary – required for our site to work and to provide services to you

Improve your experience – allows us to show you what is relevant to you

Customize your advertising – permits us to offer targeted advertising to you

Are you sure you want a less customized experience?

Your experience. Your choice.

Request

Response

Jump To

projects/{projectId}/items/{itemId}:transition

Resource Information

Request

Headers

Request

URI Parameters

Request

Body Structure

Response

HTTP Status Code Summary

Response

Body Structure (200)

Example

Request

Response

Cookie preferences

Strictly necessary – required for our site to work and to provide services to you

Improve your experience – allows us to show you what is relevant to you

Customize your advertising – permits us to offer targeted advertising to you

THIRD PARTY SERVICES

Strictly necessary – required for our site to work and to provide services to you

Improve your experience – allows us to show you what is relevant to you

Customize your advertising – permits us to offer targeted advertising to you

Are you sure you want a less customized experience?

Your experience. Your choice.