Request for report type 1118 is not allowed at this time

Official status

Amazon documentation lists Report type 1118 / GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 as in-scope for this migration. Use the official source before code freeze because deadlines and replacement details can change.

Amazon settlement report removal changelog Amazon SP-API deprecation schedule

Production Settlement validation plan

Settlement migration is a finance parser rebuild. The production gate is not simply requesting the new report type; it is proving that amount rows, currencies, descriptions and totals reconcile under realistic sample files.

Quick answer

Request for report type 1118 is not allowed at this time usually means the API rejected a request for report type 1118, which is commonly tied to the Flat File V2 settlement report request path. The fastest check is: Search logs and source for report type 1118 and GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2.

Amazon settlement report removal changelog GitHub issue with request type 1118 GitHub discussion on report type 1118 Run free scan

Why this happens

This troubleshooting page is tied to Report type 1118 / GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2, not a generic SP-API failure.

How to detect it in your code

Search the source, scheduled jobs, generated clients, report configuration and sample fixtures before assuming the issue is only live data.

if (error.message.includes('Request for report type 1118 is not allowed at this time')) {
  capture({ reportType, marketplaceIds, endpoint: '/reports/2021-06-30/reports' });
}

Fix checklist

• Preserve the exact Amazon error and request evidence.
• Map report type 1118 to GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 in the ticket.
• Confirm whether the code path is createReport, getReport or getReportDocument.
• Verify role access and report availability before retrying.
• Validate the downloaded Flat File V2 sample against accounting totals.
• Run API Migration Guard and close AMZ-SET-CREATE-001 findings.

Migration risk

This exact error is high intent: the user is blocked now, and the wrong fix can leave Settlement migration untested.

How API Migration Guard checks it

API Migration Guard scans for exact operation names, report type constants, endpoint strings, query parameters, parser assumptions and token/window loops. Paid reports add file-level findings, remediation notes, sample validation steps, CSV/JSON/SARIF exports and an evidence package.

View sample report Compare pricing Run free scan

Removed resource and replacement

What breaks

Before/after example

The example is intentionally small so the migration shape is visible in a code review.

Before:
if (error.message.includes('Request for report type 1118 is not allowed at this time')) {
  capture({ reportType, marketplaceIds, endpoint: '/reports/2021-06-30/reports' });
}

After:
// Fix path: Retrieve the correct settlement report and validate Flat File V2 parsing
// Validate with API Migration Guard, sample evidence and a re-scan.

Scanner detection

Migration checklist

• Preserve the exact Amazon error and request evidence.
• Map report type 1118 to GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2 in the ticket.
• Confirm whether the code path is createReport, getReport or getReportDocument.
• Verify role access and report availability before retrying.
• Validate the downloaded Flat File V2 sample against accounting totals.
• Run API Migration Guard and close AMZ-SET-CREATE-001 findings.

Common mistakes

• Treating Request for report type 1118 is not allowed at this time as a transient Amazon outage before checking the request shape.
• Changing code without preserving a sample request, response and report evidence.
• Closing the ticket without re-scanning source and validating the affected sample.