Mobile Dashboard OData & API Scientist
Budget: $2 – $8 AUD
We are extending a suite of mobile dashboards delivered as a Progressive Web App, and the next milestone is all about rock-solid data connectivity. The work centres on designing and implementing OData endpoints plus complementary REST APIs that feed real-time visualisations inside the PWA across both iOS and Android browsers.
What needs doing
— Expose clean, performant OData services that surface data from multiple back-ends: traditional SQL stores, a handful of NoSQL collections, and several third-party SaaS platforms we already use.
— Build (or refactor) REST endpoints where OData is not the best fit, keeping the contract consistent and well-documented in OpenAPI/Swagger.
— Secure every call with an API-key scheme; key generation, rotation and basic usage analytics are part of scope.
— Optimise queries for low-latency rendering on mobile networks, then hand over concise technical notes that let our front-end team plug in quickly.
Tech context
The current stack leans on .NET Core, Entity Framework, and Azure Functions, but we’re open to equivalent tools if you can justify the gain. Familiarity with Swagger, Postman, and CI/CD (GitHub Actions) will smooth collaboration.
Acceptance criteria
• All specified data sources reachable through OData v4 or REST, returning the exact schema provided in the spec.
• Endpoints authenticated exclusively via API key and resistant to common abuse patterns (rate limits, basic throttling).
• Postman collection and Swagger doc updated and tested.
• A short hand-off video walkthrough (~10 min) covering setup and typical calls.
The sooner we can wire these data pipes, the faster our UI team can ship the next dashboard modules, so availability for quick feedback loops is appreciated.
Start proposal with the word ODATA
What needs doing
— Expose clean, performant OData services that surface data from multiple back-ends: traditional SQL stores, a handful of NoSQL collections, and several third-party SaaS platforms we already use.
— Build (or refactor) REST endpoints where OData is not the best fit, keeping the contract consistent and well-documented in OpenAPI/Swagger.
— Secure every call with an API-key scheme; key generation, rotation and basic usage analytics are part of scope.
— Optimise queries for low-latency rendering on mobile networks, then hand over concise technical notes that let our front-end team plug in quickly.
Tech context
The current stack leans on .NET Core, Entity Framework, and Azure Functions, but we’re open to equivalent tools if you can justify the gain. Familiarity with Swagger, Postman, and CI/CD (GitHub Actions) will smooth collaboration.
Acceptance criteria
• All specified data sources reachable through OData v4 or REST, returning the exact schema provided in the spec.
• Endpoints authenticated exclusively via API key and resistant to common abuse patterns (rate limits, basic throttling).
• Postman collection and Swagger doc updated and tested.
• A short hand-off video walkthrough (~10 min) covering setup and typical calls.
The sooner we can wire these data pipes, the faster our UI team can ship the next dashboard modules, so availability for quick feedback loops is appreciated.
Start proposal with the word ODATA