How to generate delivery ticket details

Requesting delivery ticket generation

To request delivery ticket generation for a task, use the generateLegacyTaskTicketDetails mutation. You have to provide the legacyTaskId of the task you want to generate it for. You can also provide an optional crawlId - if missing, the latest Crawl from the task trend will be used for the generation.

Mutation

mutation generateLegacyTaskTicketDetails(
  $input: GenerateLegacyTaskTicketDetailsInput!
) {
  generateLegacyTaskTicketDetails(input: $input) {
    legacyTask {
      id
      ticketGenerationRequestedAt
      ticketGenerationFinishedAt
      ticketDetails
    }
  }
}

Variables

{
  "input": {
    "legacyTaskId": "TjAxMExlZ2FjeVRhc2szNTU0MA"
  }
}

Response

{
  "data": {
    "generateLegacyTaskTicketDetails": {
      "legacyTask": {
        "id": "TjAxMExlZ2FjeVRhc2szNTU0MA",
        "ticketGenerationRequestedAt": "2025-03-19T09:17:25.000Z",
        "ticketGenerationFinishedAt": null,
        "ticketDetails": null
      }
    }
  }
}

cURL

curl -X POST -H "Content-Type: application/json" -H "apollographql-client-name: docs-example-client" -H "apollographql-client-version: 1.0.0" -H "x-auth-token: YOUR_API_SESSION_TOKEN" --data '{"query":"mutation generateLegacyTaskTicketDetails( $input: GenerateLegacyTaskTicketDetailsInput! ) { generateLegacyTaskTicketDetails(input: $input) { legacyTask { id ticketGenerationRequestedAt ticketGenerationFinishedAt ticketDetails } } }","variables":{"input":{"legacyTaskId":"TjAxMExlZ2FjeVRhc2szNTU0MA"}}}' https://api.lumar.io/graphql

Try in explorer

Retrieving delivery ticket details

After generation request is made, wait a moment for it to complete. To retrieve the delivery ticket details, use the getLegacyTask query and the id of the task you requested the generation for.

Query

query getLegacyTask($id: ObjectID!) {
  getLegacyTask(id: $id) {
    id
    ticketGenerationRequestedAt
    ticketGenerationFinishedAt
    ticketDetails
  }
}

Variables

{
  "id": "TjAxMExlZ2FjeVRhc2szNTU0MA" 
}

Response

{
  "data": {
    "getLegacyTask": {
      "id": "TjAxMExlZ2FjeVRhc2szNTU0MA",
      "ticketGenerationRequestedAt": "2025-03-19T09:17:25.000Z",
      "ticketGenerationFinishedAt": "2025-03-19T09:17:55.000Z",
      "ticketDetails": {
        "title": "Optimize Cumulative Layout Shift (CLS) on Key Website Pages",
        "userStory": "As a high-performing website, I want to minimize Cumulative Layout Shift (CLS) on my pages so that I can provide a better user experience, improve Core Web Vitals metrics, and potentially boost search engine rankings.",
        "description": "Several key pages on the Lumar.io website have Cumulative Layout Shift (CLS) scores that could be improved. While most pages have acceptable CLS scores (below 0.1), some important pages like the Platform page (0.107) and Technical SEO Metrics page (0.115) exceed the \"good\" threshold of 0.1 recommended by Google.\n\nHigh CLS scores indicate visual instability during page loading, which can lead to:\n- Poor user experience as page elements shift unexpectedly\n- Potential negative impact on Core Web Vitals metrics, which are a ranking factor for Google\n- Increased bounce rates as users may accidentally click wrong elements due to shifts\n- Reduced conversion rates due to frustration with the user interface\n\nThe Lumar All Pages report shows 10 URLs with varying CLS scores, with the homepage (0.117) and the Platform page (0.107) having the highest values.",
        "howToReplicate": "1. Visit the affected URLs using Chrome DevTools\n2. Open the Performance tab\n3. Record a page load\n4. Look for the \"Layout Shift\" sections in the recording\n5. Identify elements that are shifting during page load\n\nKey pages to check:\n- https://www.lumar.io/ (CLS: 0.117)\n- https://www.lumar.io/platform/ (CLS: 0.107)\n- https://www.lumar.io/platform/technical-seo-metrics/ (CLS: 0.115)\n\nYou can also use Lumar's Site Speed Metrics report to identify these issues at scale across the website.",
        "acceptanceCriteria": "1. All pages should have a CLS score below 0.1 (the \"good\" threshold according to Google's Core Web Vitals)\n\n2. Specific improvements required:\n   - Homepage (https://www.lumar.io/): CLS reduced from 0.117 to below 0.1\n   - Platform page (https://www.lumar.io/platform/): CLS reduced from 0.107 to below 0.1\n   - Technical SEO Metrics page (https://www.lumar.io/platform/technical-seo-metrics/): CLS reduced from 0.115 to below 0.1\n\n3. No regression in other performance metrics:\n   - Largest Contentful Paint (LCP) should remain under 2.5 seconds\n   - First Input Delay (FID) should remain under 100ms\n\n4. Verification method:\n   - Lumar Site Speed Metrics report should show improved CLS scores\n   - Google PageSpeed Insights should confirm improvements\n   - Real User Monitoring data should show consistent improvements across different devices and connection types",
        "requirementsAndHowToFix": "To fix the CLS issues, implement the following changes:\n\n1. Reserve space for dynamic content:\n   - Add explicit width and height attributes to all images and video elements\n   - Use CSS aspect-ratio property where appropriate\n   - Create placeholder containers for ads and embedded content\n\n2. Avoid inserting content above existing content:\n   - Place new UI elements below the fold when possible\n   - Use transform animations instead of animations that change height/width\n   - Implement proper loading strategies for banners and notifications\n\n3. Optimize web fonts:\n   - Use font-display: optional or font-display: swap\n   - Preload critical fonts\n   - Consider using system fonts or variable fonts\n\n4. Optimize third-party scripts:\n   - Defer non-critical third-party scripts\n   - Use proper async/defer attributes\n   - Consider using Web Workers for heavy processing\n\n5. Implement proper loading strategies:\n   - Use content-visibility: auto for off-screen content\n   - Implement lazy loading for below-the-fold images\n   - Consider skeleton screens for content that takes time to load"
      }
    }
  }
}

cURL

curl -X POST -H "Content-Type: application/json" -H "apollographql-client-name: docs-example-client" -H "apollographql-client-version: 1.0.0" -H "x-auth-token: YOUR_API_SESSION_TOKEN" --data '{"query":"query getLegacyTask($id: ObjectID!) { getLegacyTask(id: $id) { id ticketGenerationRequestedAt ticketGenerationFinishedAt ticketDetails } }","variables":{"id":"TjAxMExlZ2FjeVRhc2szNTU0MA"}}' https://api.lumar.io/graphql

Try in explorer