RESTful API for OrbisAPI Marketplace
Budget: $15 – $25 USD
I am ready to publish a new integration on the OrbisAPI marketplace and need a production-ready RESTful API built from scratch. The service will act as a bridge between OrbisAPI and a small set of third-party APIs that I will specify once the project starts. No local database or file system storage is required—every request will simply fetch, transform, and return data coming from those external providers.
Core scope
• Design clean, versioned REST endpoints that follow standard HTTP semantics (GET, POST, PUT/PATCH, DELETE).
• Handle authentication to the external providers using their preferred schemes (mostly Bearer tokens and OAuth2).
• Normalise the responses so OrbisAPI users receive a consistent JSON structure regardless of which upstream service is queried.
• Write concise OpenAPI / Swagger documentation and an onboarding guide that meets the formatting rules in the OrbisAPI marketplace publisher docs.
• Package the code so it can be containerised easily; I am comfortable deploying Docker images, so a Dockerfile and short README are expected.
• Include unit tests that cover the primary success paths and common error states; feel free to use Jest, Mocha, PyTest, or another lightweight framework that suits the language you choose.
Acceptance criteria
The API is considered complete when:
1. All listed endpoints return the expected shape and status codes, verified by automated tests.
2. The OpenAPI spec passes OrbisAPI’s validator with no warnings.
3. A sample consumer script demonstrates end-to-end calls against at least two of the target third-party APIs.
I am language-agnostic—Node.js (Express/Fastify), Python (FastAPI/Flask), or Go are fine as long as the final artefacts meet the above criteria. Once delivered, I will take care of hosting, so please keep any environment variables or secrets configurable via .env files only.
If you have published integrations on marketplaces before—or simply love crafting lean, well-documented REST services—let’s talk.
Core scope
• Design clean, versioned REST endpoints that follow standard HTTP semantics (GET, POST, PUT/PATCH, DELETE).
• Handle authentication to the external providers using their preferred schemes (mostly Bearer tokens and OAuth2).
• Normalise the responses so OrbisAPI users receive a consistent JSON structure regardless of which upstream service is queried.
• Write concise OpenAPI / Swagger documentation and an onboarding guide that meets the formatting rules in the OrbisAPI marketplace publisher docs.
• Package the code so it can be containerised easily; I am comfortable deploying Docker images, so a Dockerfile and short README are expected.
• Include unit tests that cover the primary success paths and common error states; feel free to use Jest, Mocha, PyTest, or another lightweight framework that suits the language you choose.
Acceptance criteria
The API is considered complete when:
1. All listed endpoints return the expected shape and status codes, verified by automated tests.
2. The OpenAPI spec passes OrbisAPI’s validator with no warnings.
3. A sample consumer script demonstrates end-to-end calls against at least two of the target third-party APIs.
I am language-agnostic—Node.js (Express/Fastify), Python (FastAPI/Flask), or Go are fine as long as the final artefacts meet the above criteria. Once delivered, I will take care of hosting, so please keep any environment variables or secrets configurable via .env files only.
If you have published integrations on marketplaces before—or simply love crafting lean, well-documented REST services—let’s talk.