> ## Documentation Index > Fetch the complete documentation index at: https://help.polygon-one.com/llms.txt > Use this file to discover all available pages before exploring further. # Request Supplier Origin Confirmation > Call this after uploading all current buyer-provided plots for the selected lines of one order. The supplier is asked to attest the current origin data; previous-order data is not copied and buyer authorship is preserved. Every `supplierArticleId` must be a live, EUDR-relevant link for an article line of this exact order and its supplier, and every target must already have a live plot. Validation is all-or-nothing. Requires `orders:write` and the tenant's per-order origin-confirmation automation to be enabled. Before queueing, the endpoint durably fences the selected targets against any previous-order copy. A successful `202` means queued; request publication and email delivery are asynchronous. An enqueue failure is a `500`, never a misleading `202`; the durable fence remains safe for an idempotent retry. Repeating the same finalization merges into the active supplier request and does not send another creation email. ## OpenAPI ````yaml POST /api/v1/orders/{id}/origin-confirmation openapi: 3.1.0 info: title: Polygon One Compliance API description: >- REST API for connecting ERP and other business systems to Polygon One. It covers both compliance modules: **EUDR** (EU Deforestation Regulation) — articles, suppliers, plots, evidence, orders and Due Diligence Statements — and **PPWR** (EU Packaging and Packaging Waste Regulation) — packaging components and units, documents, Declarations of Conformity, the SKU quantity feed and volume reports. Authenticate every request with an API key created in Settings → API Keys, sent as `Authorization: Bearer `. Each key carries scopes (e.g. `articles:read`, `packaging:write`) that limit what it may read and write. Versioning: `v1` changes only additively — new endpoints, new optional request fields and new response fields may appear, nothing documented is removed or changed in meaning. Ignore response fields you do not know. Guides and walkthroughs: https://help.polygon-one.com/api-reference/introduction version: 1.0.0 contact: name: Polygon One Support email: help@polygon-one.eu servers: - url: https://app.polygon-one.com description: Production Server security: - bearerAuth: [] tags: - name: Articles description: >- EUDR articles: your products and purchased goods, their HS code, EUDR relevance and supplier links. - name: Suppliers description: EUDR suppliers and their links to articles. - name: Plots description: >- EUDR plots of land (geolocations): create, validate, link to supplier articles, read the geo analysis and its report. - name: Evidence description: >- EUDR evidence documents attached to a supplier article (legal compliance documents, questionnaires). - name: Orders description: >- Purchase and sale orders and their lines; the read-back of the DDS references linked to each order. - name: Import Jobs description: >- Status and result of an asynchronous batch import (articles, suppliers, orders, PPWR quantities). - name: Readiness description: Action-scoped readiness snapshots for owned EUDR and PPWR resources. - name: DDS Statements description: >- EUDR Due Diligence Statements: create, read, update the TRACES numbers, delete. - name: PPWR Packaging Data description: >- PPWR master data: packaging components, packaging units, their sizes, bills of materials and article links. - name: PPWR Documents description: >- Upload supporting documents (test reports, declarations, technical documentation) to a packaging unit or component. - name: PPWR Declarations of Conformity description: Read Declarations of Conformity and download their files. - name: PPWR Quantities & Volume Reports description: >- The SKU quantity feed, aggregate material tonnage and the generated volume reports (Mengenmeldung). paths: /api/v1/orders/{id}/origin-confirmation: post: tags: - Orders summary: Request Supplier Origin Confirmation description: >- Call this after uploading all current buyer-provided plots for the selected lines of one order. The supplier is asked to attest the current origin data; previous-order data is not copied and buyer authorship is preserved. Every `supplierArticleId` must be a live, EUDR-relevant link for an article line of this exact order and its supplier, and every target must already have a live plot. Validation is all-or-nothing. Requires `orders:write` and the tenant's per-order origin-confirmation automation to be enabled. Before queueing, the endpoint durably fences the selected targets against any previous-order copy. A successful `202` means queued; request publication and email delivery are asynchronous. An enqueue failure is a `500`, never a misleading `202`; the durable fence remains safe for an idempotent retry. Repeating the same finalization merges into the active supplier request and does not send another creation email. operationId: requestOrderOriginConfirmation parameters: - schema: type: string format: uuid required: true name: id in: path requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/OriginConfirmationInput' example: supplierArticleIds: - 2e8f6a3c-9d17-4b52-8c4a-7f1e3d9b0a65 responses: '202': description: Origin confirmation queued content: application/json: schema: $ref: '#/components/schemas/OriginConfirmationAccepted' example: status: queued orderId: 1b7f3e9d-4a26-4c85-b9e1-5d0a8c3f7e42 supplierArticleCount: 1 '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '409': description: >- `origin_confirmation_disabled` when the tenant is not configured for per-order EUDR origin confirmation; `origin_confirmation_plots_missing` when any target has no live plot; `origin_confirmation_processing` when a supplier answer is already being processed. Nothing is queued. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Every supplier article must have at least one live plot code: origin_confirmation_plots_missing '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/InternalError' components: schemas: OriginConfirmationInput: type: object properties: supplierArticleIds: type: array items: type: string format: uuid description: >- Live supplier-article links on this exact order whose current buyer-provided origin data is complete. required: - supplierArticleIds OriginConfirmationAccepted: type: object properties: status: type: string enum: - queued description: The confirmation request was accepted for asynchronous processing. orderId: type: string format: uuid description: >- The exact order whose current origin data will be presented to the supplier. supplierArticleCount: type: integer exclusiveMinimum: 0 description: Number of distinct supplier-article targets queued. required: - status - orderId - supplierArticleCount ErrorResponse: type: object properties: error: type: string description: >- Human-readable message, or a stable machine key (e.g. `batchTooLarge`, `overwriteRequired`, `duplicate`) on the batch, PPWR and upload endpoints. code: type: string description: >- Stable machine code on some `400` and `409` answers, e.g. `plot_geometry_invalid` or `FORK_HAS_ORDER`. Match on it rather than on `error`. Further flat keys may accompany it (e.g. `precisionDigits`, `field`). details: type: array items: $ref: '#/components/schemas/ValidationIssue' description: The validation issues on a `400` validation error. warnings: type: array items: type: object properties: type: type: string enum: - duplicateName - duplicateEan description: >- `duplicateName`: a live article of your company already has this name. `duplicateEan`: a live article already has this EAN. existingInternalArticleNr: type: string description: >- `duplicateName` only: internal article number of the existing article. existingArticleName: type: string description: '`duplicateEan` only: name of the existing article.' required: - type description: >- `POST /articles` `409` only: soft duplicate warnings. Resend with `acknowledgeWarnings: true` to create the article anyway. required: - error additionalProperties: {} description: >- Error body of every endpoint except the `429` the edge answers. Some errors add flat machine-readable keys next to `error`, e.g. `maxBatchSize` on `413 batchTooLarge` or `confirmUpdateCount` on `409 overwriteRequired`. ValidationIssue: type: object properties: code: type: string description: >- Machine code of the issue, e.g. `invalid_type`, `too_small`, `custom`. path: type: array items: anyOf: - type: string - type: number description: >- Location of the offending value in the request: object keys and 0-based array positions. message: type: string description: >- Human-readable English explanation. The wording may change; match on `code` and `path`. required: - code - path - message additionalProperties: {} description: >- One validation issue. Issue-specific keys (e.g. `expected`, `minimum`) may accompany the three listed. RateLimitedResponse: type: object properties: error: type: object properties: code: type: string enum: - rate_limited description: Always `rate_limited`. message: type: string description: Human-readable explanation. required: - code - message description: Unlike every other error body, `error` is an object here. required: - error responses: BadRequest: description: Invalid request data content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Validation failed details: - origin: string code: too_small minimum: 1 inclusive: true path: - address - street message: Address is required. Unauthorized: description: Invalid or expired API key, or the key's user account is not active. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Invalid or expired API key Forbidden: description: Insufficient permissions for this resource content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Forbidden NotFound: description: Resource not found content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Resource not found TooManyRequests: description: >- Rate limit exceeded: currently 1000 requests per 60 seconds per client IP across all `/api` paths. Issued by the edge before the application runs, so the JSON body differs from every other error: `error` is an object. A `429` with an HTML body instead of JSON means the request carried no API key. content: application/json: schema: $ref: '#/components/schemas/RateLimitedResponse' example: error: code: rate_limited message: … InternalError: description: Internal server error content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: Internal server error securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Key description: >- API key generated in Settings > API Keys. Include as `Authorization: Bearer `. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.