Hello Edge Impulse Community,
I am writing to report a persistent HTTP 403 Forbidden error when trying to upload files to a dataset via the Ingestion API. I am using a Free (Developer) plan , and I have already taken several steps to rule out common configuration issues.
Problem Summary:
When sending a POST request to https://ingestion.edgeimpulse.com/api/training/files with a multipart/form-data payload, the server consistently returns 403 Forbidden with a generic HTML body. This happens with multiple files (e.g., background3.jpg ).
Environment & Configuration:
- Plan: Free (Developer)
-
Endpoint:
POST https://ingestion.edgeimpulse.com/api/training/files -
Authentication:
x-api-keyheader containing an API key that starts withei_... -
Key Role:
Ingestion(orIngestion + deployment) -
Key Status: The key is marked as a Development Key . I have attempted to create this key both through the GUI (where the combination of
Ingestion+Developmentis not selectable) and programmatically via thePOST /api/{projectId}/apikeysendpoint withisDevelopmentKey: true, as per the documentation.
What I Have Already Tried:
- Verified that the key is an API Key (not an HMAC key).
- Confirmed the key is scoped to the correct project.
- Tested the same request using both Python (
requestslibrary) and an equivalent PowerShellInvoke-WebRequestscript to rule out a client-side issue. - Ensured the
Content-Typeheader is being set correctly by the client library (no manual override that could break themultipart/form-databoundary). - Checked that the files are within the documented limits (e.g., under 100 MB, batch size under 1000).
Question:
Given that the key appears to have the correct permissions (Ingestion ) and status (Development ), what could be causing the 403 Forbidden on the Ingestion API? Is there a known issue with 403 errors for keys created on the free plan, or a specific requirement for the key format/headers that I might be missing?
Any guidance would be greatly appreciated. I can provide the specific key ID (not the key itself) and project ID if needed for further investigation.
Thank you!