Request

Response

    Migration Guide

    Migrating from v1 to v2

    Upgrading to Version 2 of the Fusion Operations API brings significant improvements and changes. This guide provides step-by-step instructions to help you update your integrations and ensure a smooth transition. Review each area below before updating your integration.

    Base URL

    The API base endpoints have been updated in Version 2. Please update your integrations to use the new endpoint:

    v1v2
    https://fusionoperations.autodesk.com/api/v1/... https://api.aps.autodesk.com/fusion-operations/v2/...

    Authentication

    v1 used /api/v1/authorization endpoint that returned a token that would be appended to every request as a query parameter:

    GET /api/v1/productions?access_token=<token>
    

    v2 removes that endpoint entirely. All requests must carry a JWT obtained from Autodesk’s OAuth 2.0 service in the Authorization header:

    GET /fusion-operations/v2/production-records
    Authorization: Bearer <jwt>
    

    Refer to the Authentication section for instructions on obtaining a token through Autodesk’s OAuth service.

    Note

    The /api/v1/authorization endpoint no longer exists in v2. Any code that calls it must be replaced with the Autodesk OAuth flow.

    JSON Field Naming

    All JSON request and response fields changed from kebab-case to camelCase:

    v1 field namev2 field name
    start-time startTime
    end-time endTime
    production-order productionOrder
    started-by startedBy

    This applies to every field in every endpoint. Update your serialization/deserialization logic accordingly.

    HTTP Method for Updates

    v1 used PUT for all update operations (full replacement).

    # v1 — full replacement
    PUT v1/productions/{code}
    

    v2 uses PATCH, which performs a partial update — only the fields included in the request body are modified; omitted fields keep their current values.

    # v2 — partial update
    PATCH /fusion-operations/v2/production-records/{id}
    

    Ensure you only send the fields that need to change. Sending a full object is still valid, but be aware that null values will explicitly clear a field.

    Resource Identifiers

    Path parameter identifiers changed from string codes to numeric IDs:

    v1 pathv2 path
    /products/{code} /products/{productId}
    /productions/{code} /production-records/{productionRecordId}
    /downtimes/{code} /downtime-records/{downtimeRecordId}

    Numeric IDs are returned in the id field of every v2 response. Store and use these IDs rather than string codes when building URLs.

    Pagination

    The pagination mechanism has changed from page-based to offset-based:

    v1 — page number query parameter, flat array response:

    GET /api/v1/productions?page=2
    
    [
      { "start-time": "2025-01-01T08:00:00Z", ... },
      { "start-time": "2025-01-01T09:00:00Z", ... }
    ]
    

    v2 — offset query parameter, wrapped response object:

    GET /fusion-operations/v2/production-records?offset=50&limit=50
    
    {
      "results": [
        { "startTime": "2025-01-01T08:00:00Z", ... },
        { "startTime": "2025-01-01T09:00:00Z", ... }
      ],
      "pagination": {
        "offset": 0,
        "limit": 25,
        "nextUrl": null
      }
    }
    
    Show More

    Update any code that iterates through pages to use offset and read results from response.results.

    Filtering

    v1 used custom, per-endpoint query parameters for filtering. v2 introduces a standardised filter[field] syntax across all endpoints.

    v1 example (endpoint-specific params):

    GET /api/v1/productions?start_date=2025-01-01&end_date=2025-01-31
    

    v2 example (standardised syntax):

    GET /fusion-operations/v2/purchase-orders?filter[code]=MyPurchaseOrder
    

    Value filters are expressed as a encoded value after the =. Multiple filters can be combined in a single request by repeating the filter[field] pattern.

    GET /fusion-operations/v2/production-records?filter[startTime]=2025-01-01..2025-01-31
    

    Date ranges are expressed as startDate..endDate.

    GET /fusion-operations/v2/production-records?filter[quantity]=0..10
    

    Decimal ranges are expressed as lowerValer..upperValue.

    Sorting

    V2 adds a sort parameter not present in v1:

    v2 example (standardised syntax):

    GET /products?sort=code asc
    GET /production-records?sort=startTime desc, id asc
    

    The sort parameter accepts a comma-separated list of field names. Add the desc after the field name to sort in descending order; no specification or asc means ascending:

    # Sort by startTime ascending, then by quantity descending
    GET /fusion-operations/v2/production-records?sort=startTime asc, quantity desc
    

    Note

    Not every field is sortable. Refer to the reference documentation for each endpoint to see the list of supported sort fields.

    Endpoint Renames

    Several endpoints have been renamed for consistency:

    v1 pathv2 path
    /productions /production-records
    /downtimes /downtime-records
    /punchclocks /punch-clock-records

    Error Format

    v1 returned ad-hoc error messages that varied by endpoint. v2 uses a consistent error structure for all failure responses.

    Single error (e.g. 400, 404, 422):

    {
      "title": "Resource not found",
      "detail": "No production record exists with id 9999."
    }
    

    Validation errors (multiple field-level issues):

    {
      "title": "Validation failed",
      "errors": [
        { "field": "startTime", "detail": "Must be a valid ISO 8601 datetime." },
        { "field": "quantity",  "detail": "Must be a positive number." }
      ]
    }
    

    Update your error handling to read title and detail (or iterate errors[] for validation responses) instead of relying on endpoint-specific message formats.


    New Response Body Fields

    v2 expands several resource schemas with new fields. The tables below list every addition per resource. Fields not listed here were already present in v1 (subject to the camelCase rename described above).

    Products

    New fieldDescription
    unitCost Standard cost per unit.
    unitPrice Default selling price per unit.
    specsSheetImages Array of image URLs attached to the product spec sheet.
    variableParameters List of configurable parameters for variable products.
    boxQuantity Number of units per box/packaging unit.
    weight Product weight value.
    weightUnitOfMeasurement Unit for the weight field (e.g. "kg", "lb").
    purchaseOrderUnitOfMeasurement Unit of measurement used on purchase orders for this product.
    unitOfMeasurementGroup Group that defines allowed unit conversions for this product.
    materialReceivingCheckList Checklist template applied when receiving this material.
    disabled true if the product is defined as disabled.
    suppliers Array of supplier objects linked to this product.
    maximumInventory Maximum stock level trigger for reorder alerts.
    minimumQuantityToReorder Minimum quantity included in a replenishment order.
    quantityMultiple Orders must be placed in multiples of this quantity.
    scrapAllowance Expected scrap percentage factored into production planning.
    shelfLife Shelf life in days for perishable or time-sensitive products.
    leadTime Expected lead time in days from order to receipt.
    automaticSerialNumber true if serial numbers are auto-generated for this product.

    Production Records

    New fieldDescription
    machine Machine object on which the production took place.
    timeSpent Actual production time in seconds.
    timeEstimated Production estimated time in seconds.
    teamId Identifier of the team that produced this record.
    cost Calculated production cost for this record.
    boxes Array with boxes that were worked on.
    consumptions Array of component consumptions recorded against this production run.
    finishedBy Worker object representing who completed the record.
    training true if this record was created via a training session.

    Sales Orders

    New fieldDescription
    status Current order status (e.g. OPEN, CLOSED, CANCELLED)
    createdBy Worker object representing who created the order.
    carrier Shipping carrier name or object.
    quote Associated quote object or identifier.

    Purchase Orders

    New fieldDescription
    approvalStatus Current order status (e.g. "REVIEW", "APPROVED").
    documentStatus Approval or document workflow status.

    Production Orders

    New fieldDescription
    predictedDuration Estimated production duration in seconds.

    Inventory Movements

    New fieldDescription
    unitOfMeasurement Unit of measurement used for the moved quantity.
    production Associated production record object, if applicable.
    maintenanceOrder Associated maintenance order object, if applicable.
    worker Worker object who performed the movement.

    Punch Clock Records

    New fieldDescription
    combineWithShift true if this record should be merged with an adjacent shift.
    delay delay in seconds between scheduled and actual punch in. Returns 0 for punch out records.

    Clients and Suppliers

    No new fields were added to these resources in v2. Some fields were renamed (following the camelCase convention) or removed. Refer to the reference documentation for the current schema.

    Workers (new in v2)

    Workers is a fully new resource in v2; there is no equivalent v1 endpoint. The response schema includes:

    • id, name, number, shift
    • language, section

    Machines (new in v2)

    Machines is a fully new resource in v2; there is no equivalent v1 endpoint. The response schema includes:

    • id, code, name
    • shift, reasonCodes
    • section

    Removed Endpoints

    The following v1 endpoints do not have a direct v2 equivalent:

    V1 endpointStatusNotes
    GET /api/v1/authorization Removed Replaced by Autodesk OAuth 2.0
    POST /api/v1/authorization Removed Replaced by Autodesk OAuth 2.0
    DELETE /api/v1/authorization Removed Replaced by Autodesk OAuth 2.0
    GET /api/v1/changes/{channel} Removed Changes feed not present in v2
    POST /api/v1/machines/{code}/counter Moved Available under PATCH /production-records/{productionRecordId}
    POST /api/v1/machines/{code}/startstop Moved Available under /downtime-records
    GET /api/v1/stock/{code} Moved Available under /products/{productId}/inventory
    POST /api/v1/production-orders/{id}/activate Moved Available under PATCH /production-orders/{productionOrderId}
    POST /api/v1/production-orders/{id}/notify Removed Not present in v2

    Migration Checklist

    Infrastructure

    • Update base URL to https://api.aps.autodesk.com/fusion-operations/v2
    • Implement Autodesk OAuth 2.0 Client Credentials flow
    • Store and refresh JWT Bearer tokens
    • Add Authorization: Bearer <token> header to all requests
    • Remove ?access_token=xxx from all URLs

    Requests

    • Rename all JSON request fields from kebab-case to camelCase
    • Change PUT calls to PATCH for update operations
    • Update path parameters to use numeric id instead of code
    • Update URL paths: remove /api/v1 prefix
    • Update endpoint name: /productions → /production-records
    • Update endpoint name: /downtimes → /downtime-records
    • Update endpoint name: /punchclocks → /punch-clock-records

    Responses

    • Update response parsing to read from results[] array
    • Update pagination logic: replace page with offset
    • Use pagination.nextUrl to detect next page
    • Update error handling to parse { title, detail } and { title, errors[] } formats
    • Handle status enum (OPEN/CLOSED/ARCHIVED) replacing ended/archived booleans

    Filtering

    • Convert custom filter params to filter[field] syntax
    • Update date filters to use range syntax (start..end)
    • Update status filters to use filter[status]=OPEN,CLOSED,ARCHIVED

    Sorting

    • Use the new sort parameter to define pagination sorting method
    • Use desc or asc keywords after the field name for descending order or ascending order (e.g. sort=startTime desc ``). If not provided, ``asc is the default
    • Combine multiple sort fields as a comma-separated list (e.g. sort=startTime asc quantity desc)

    Testing

    • Verify authentication with Autodesk OAuth
    • Test all CRUD operations for each resource
    • Verify pagination across all list endpoints
    • Confirm error responses are parsed correctly
    • Test rate limiting behavior with Retry-After handling