Physical Product REST API Setup
Budget: £10 – £20 GBP
I need a clean, well-documented REST API that lets third-party sellers submit, update, and delete physical product records in our catalogue. Each request must be secured with an API-key header; no other auth method is required.
The core flow is straightforward:
• POST /products – create a new physical product with its SKU, pricing, inventory count, and basic metadata.
• PUT /products/{id} – update any of the above fields.
• DELETE /products/{id} – permanently remove a record.
I’m happy with any modern stack—Node/Express, FastAPI, Laravel, Spring Boot, etc.—provided you follow standard REST conventions and return JSON responses.
Deliverables
1. Source code in a Git repo.
2. A short README covering environment setup, build/run commands, and example curl requests that include the required api_key header.
3. Endpoint reference generated via Swagger/OpenAPI.
4. Postman collection for quick testing.
5. Brief hand-off call or video walkthrough (optional but appreciated).
Acceptance criteria
• All three endpoints perform as described and return appropriate HTTP status codes.
• Requests without a valid api_key are rejected with 401.
• Basic input validation prevents empty fields and obviously bad data.
• Code is lint-clean and runnable with a single command (docker-compose is fine).
If you’ve built similar submission pipelines before, especially for physical products, let me see a quick demo or snippets in your bid.
The core flow is straightforward:
• POST /products – create a new physical product with its SKU, pricing, inventory count, and basic metadata.
• PUT /products/{id} – update any of the above fields.
• DELETE /products/{id} – permanently remove a record.
I’m happy with any modern stack—Node/Express, FastAPI, Laravel, Spring Boot, etc.—provided you follow standard REST conventions and return JSON responses.
Deliverables
1. Source code in a Git repo.
2. A short README covering environment setup, build/run commands, and example curl requests that include the required api_key header.
3. Endpoint reference generated via Swagger/OpenAPI.
4. Postman collection for quick testing.
5. Brief hand-off call or video walkthrough (optional but appreciated).
Acceptance criteria
• All three endpoints perform as described and return appropriate HTTP status codes.
• Requests without a valid api_key are rejected with 401.
• Basic input validation prevents empty fields and obviously bad data.
• Code is lint-clean and runnable with a single command (docker-compose is fine).
If you’ve built similar submission pipelines before, especially for physical products, let me see a quick demo or snippets in your bid.
Related categories:
PHP
Business, Accounting, Human Resources & Legal
MySQL
Node.js
RESTful
API Development
FastAPI
REST API