> ## 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. # Upload-URL für einen Nachweis anfordern > Step 1 of uploading an evidence document (e.g. a legal or origin document) to a supplier article: get a presigned URL, then `PUT` the file bytes to `uploadUrl` with the same `Content-Type` within 10 minutes. Pass the returned `s3Key` as `uploadedS3Key` to `POST /api/v1/evidence`. Accepts the files the in-app evidence upload accepts, at most 10 MB — a wrong type or a larger `fileSize` is a `400`. `fileSize` is signed into `uploadUrl`: a `PUT` of any other length is refused by storage. Requires `evidence:write`. ## OpenAPI ````yaml POST /api/v1/evidence/upload-url 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/evidence/upload-url: post: tags: - Evidence summary: Create Evidence Upload URL description: >- Step 1 of uploading an evidence document (e.g. a legal or origin document) to a supplier article: get a presigned URL, then `PUT` the file bytes to `uploadUrl` with the same `Content-Type` within 10 minutes. Pass the returned `s3Key` as `uploadedS3Key` to `POST /api/v1/evidence`. Accepts the files the in-app evidence upload accepts, at most 10 MB — a wrong type or a larger `fileSize` is a `400`. `fileSize` is signed into `uploadUrl`: a `PUT` of any other length is refused by storage. Requires `evidence:write`. operationId: createEvidenceUploadUrl requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/EvidenceUploadUrlInput' example: fileName: harvest-licence-2025.pdf contentType: application/pdf fileSize: 482113 responses: '200': description: Presigned upload URL content: application/json: schema: $ref: '#/components/schemas/EvidenceUploadUrl' example: uploadUrl: >- https://example-bucket.s3.eu-central-1.amazonaws.com/pending/operator/3f6c2a8e-5b1d-4c7e-9a2f-6d8b1e4c0a17/6a0e4c8f-2b57-4d93-8b1f-0e6c4a2d9f85-harvest-licence-2025.pdf?X-Amz-… s3Key: >- pending/operator/3f6c2a8e-5b1d-4c7e-9a2f-6d8b1e4c0a17/6a0e4c8f-2b57-4d93-8b1f-0e6c4a2d9f85-harvest-licence-2025.pdf '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '429': $ref: '#/components/responses/TooManyRequests' '500': $ref: '#/components/responses/InternalError' components: schemas: EvidenceUploadUrlInput: type: object properties: fileName: type: string minLength: 1 description: Name of the file to upload, including its extension. contentType: type: string minLength: 1 description: >- MIME type of the file (e.g. `application/pdf`). Send the same value as `Content-Type` when uploading to `uploadUrl`. fileSize: type: integer exclusiveMinimum: 0 description: >- Size of the file in bytes. It is signed into `uploadUrl`: the `PUT` must send exactly this many bytes. required: - fileName - contentType - fileSize description: 'The file to upload: name, MIME type and size in bytes.' EvidenceUploadUrl: type: object properties: uploadUrl: type: string description: >- Presigned S3 PUT URL, valid for 10 minutes. Send the file bytes with the same `Content-Type`. s3Key: type: string description: >- The staging key — pass it as `uploadedS3Key` to `POST /api/v1/evidence`. required: - uploadUrl - s3Key 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`. 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 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. 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 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.