> ## Documentation Index > Fetch the complete documentation index at: https://docs.lendflow.com/llms.txt > Use this file to discover all available pages before exploring further. # Update Application Workflow Data > Applies partial updates to an application and its related business and owners. Submitted values are mapped through the workflow's field definitions and saved within a single transaction, so a failed update leaves nothing changed. ## OpenAPI ````yaml /openapi.yaml put /api/applications/{application_id}/workflow openapi: 3.0.3 info: title: Lendflow API docs description: '' version: 1.0.0 servers: - url: https://api.lendflow.com security: - default: [] tags: - name: Authentication description: >- Lendflow uses API Bearer Tokens to permit access to our API. You can register for a new Lendflow API key on our client portal in less than 60 seconds. The Bearer Token needs to be included in all API requests made to the API Service in the following form:
Authorization: Bearer [YOUR_TOKEN]
You must replace [YOUR_TOKEN] with your personal API key.
- name: Access Tokens description: |- Create and manage the personal access tokens used to authenticate API requests. - name: Workflow Management description: |- Create applications and manage them through every stage of their workflow, from intake through decision. - name: Documents description: |- Upload, retrieve, and manage the files attached to an application. - name: Placements description: |- Submit applications to lenders and manage each placement through its lifecycle. - name: Offers description: |- Create and manage offers on an application, from initial terms through funding. - name: Smartviews description: |- Save and manage reusable application filters that organize your pipeline. - name: Workflow Templates description: |- Browse the workflow templates available for creating applications. - name: Consent Templates description: |- Manage the consent documents presented to applicants for signature. - name: Offer Templates description: |- Manage the templates that define the structure and fields of your offers. - name: Data Orchestration description: |- Run data orchestration templates against applications and review their execution logs. - name: Attributes description: |- Define computed attributes and evaluate them against your applications. - name: Scorecards description: |- Run scorecards and scorecard groups against applications and retrieve their results. - name: Entity Profiles description: |- Manage the reusable business and individual profiles shared across applications. - name: Organization description: |- Manage the users in your organization. - name: Metadata description: |- Attach custom key-value data to your applications and files. paths: /api/applications/{application_id}/workflow: parameters: - in: path name: application_id description: The ID of the application. example: architecto required: true schema: type: string put: tags: - Workflow Management summary: Update Application Workflow Data description: |- Applies partial updates to an application and its related business and owners. Submitted values are mapped through the workflow's field definitions and saved within a single transaction, so a failed update leaves nothing changed. parameters: [] requestBody: required: false content: multipart/form-data: schema: type: object properties: client_tracking_token: type: string description: >- Client tracking token for the application. Must not be greater than 50 characters. example: lead-12345 tracking_tokens: type: array description: >- One additional tracking token. Must not be greater than 255 characters. example: - campaign-123 items: type: string utm_parameters: type: array description: UTM parameters to associate with the application. example: - type: utm_source value: newsletter items: type: object properties: type: type: string description: >- UTM parameter type. Valid values: utm_campaign, utm_source, utm_medium, utm_term, utm_content. example: utm_source enum: - utm_campaign - utm_source - utm_medium - utm_term - utm_content value: type: string description: UTM parameter value. example: newsletter move_to_next_stage: type: boolean description: Whether to move the application to its next workflow stage. example: true with_validation: type: boolean description: >- Whether to validate required workflow fields before moving to the next stage. example: true data_orchestration_template_id: type: string description: >- Data orchestration template ID to run for the application. Must match an existing stored value. example: 1ccdd4c1-52a9-4249-8d9a-e7ab500a2c1d bank_statements: type: array description: Must not have more than 10 items. example: null items: type: object properties: file: type: string format: binary description: >- This field is required when bank_statements is present. Must be a file. Must not be greater than 102400 kilobytes. type: type: string description: >- This field is required when bank_statements is present. example: bank_statements_1 enum: - bank_statements - bank_statements_1 - bank_statements_2 - bank_statements_3 - bank_statements_4 - bank_statements_5 - bank_statements_6 - bank_statements_7 - bank_statements_8 - bank_statements_9 - bank_statements_10 - bank_statements_11 - bank_statements_12 - personal_bank_statements with_underwriting: type: string description: '' example: null external_service_logs: type: string description: '' example: null note: type: object description: Application note to create. example: comment: Requested updated bank statements. visibility_scope: 1 properties: comment: type: string description: Application note content. example: Requested updated bank statements. visibility_scope: type: string description: >- Who can see the note. Valid values: All (1), Internal (2), Personal (3), Client (5), Client Team (6). example: 1 enum: - 1 - 2 - 3 - 5 - 6 nullable: true lenient_fields: type: array description: >- One workflow field identifier to validate leniently. Valid values: accounts_payable_phone_number, affiliated_businesses_phone_numbers, affiliated_individuals_telephone, bonding_agent_telephone, business_phone_numbers, company_officers_phone_number, guarantor_telephone, insurance_telephone, personal_phone_numbers, personal_telephone, trade_references_business_telephone. example: - personal_phone_numbers items: type: string enum: - accounts_payable_phone_number - affiliated_businesses_phone_numbers - affiliated_individuals_telephone - bonding_agent_telephone - business_phone_numbers - company_officers_phone_number - guarantor_telephone - insurance_telephone - personal_phone_numbers - personal_telephone - trade_references_business_telephone nullable: true brand_name_id: type: string description: >- Client brand name ID to associate with the application. It must belong to the application client. example: 1ccdd4c1-52a9-4249-8d9a-e7ab500a2c1d nullable: true plaid_data: type: object description: '' example: null properties: {} plaid: type: object description: '' example: [] properties: transactions: type: object description: '' example: null properties: {} asset_report: type: object description: '' example: null properties: {} rollback: type: boolean description: >- Whether to move the application to its previous workflow stage. example: true move_to_stage_id: type: string description: >- Workflow stage ID to move to without validating intermediate stages. Must be a valid UUID. example: 3b7d4cb8-84e5-4da4-98a8-d31e01e58a60 nullable: true responses: '200': description: '' content: application/json: schema: type: object example: data: application_id: null client_id: null brand_name_id: null client_tracking_token: null status: null deal_mode: 1 source: null referrer_url: null widget_info: id: null widget_link: null widget_type: null requested_workflow_template_id: null contract_template_id: null consent_template_id: null contract_template: null consent_template: null created_at: null updated_at: null properties: data: type: object properties: application_id: type: string example: null nullable: true client_id: type: string example: null nullable: true brand_name_id: type: string example: null nullable: true client_tracking_token: type: string example: null nullable: true status: type: string example: null nullable: true deal_mode: type: integer example: 1 source: type: string example: null nullable: true referrer_url: type: string example: null nullable: true widget_info: type: object properties: id: type: string example: null nullable: true widget_link: type: string example: null nullable: true widget_type: type: string example: null nullable: true requested_workflow_template_id: type: string example: null nullable: true contract_template_id: type: string example: null nullable: true consent_template_id: type: string example: null nullable: true contract_template: type: string example: null nullable: true consent_template: type: string example: null nullable: true created_at: type: string example: null nullable: true updated_at: type: string example: null nullable: true components: securitySchemes: default: type: http scheme: bearer description: >-
You can register for a new Lendflow API key on our client portal in less than 60 seconds. The Bearer Token needs to be included in all API requests made to the API Service in the following form:
Authorization: Bearer [YOUR_TOKEN]
You must replace [YOUR_TOKEN] with your personal API key.
````