Approval flow route APIs now support PurchaseRequest and updated response schemas

Changes

• Usages in approval flow route responses now includes the enum value PurchaseRequest
• definition_system, description, first_step_id, name, usages, and user_id became required fields in approval flow route responses
• request_form_ids in route list responses and steps in single route responses became required fields
• The approver user ID property name in steps changed from user_ids to users_ids in single route responses
• The format of query parameters request_form_id and company_id, and path parameter id changed to int64

Affected areas

GET /api/1/approval_flow_routesGET /api/1/approval_flow_routes/{id}