Skip to content

Custom API development: your function as an endpoint, or a full backend

Sometimes you need one capability, not a system: a price calculator, a document converter, a data check, a report builder. We write it, run it on our MetaPlatho platform and give you an HTTP endpoint with an API key. When the task is bigger, we build an ordinary backend service in Python or Node.js.

When you need this

  • 1

    You need one function and do not want to build and operate a backend for it

  • 2

    The front end or a no-code tool is ready, and the server-side logic is missing

  • 3

    Two systems have to exchange data and neither has a ready integration

  • 4

    You want to sell a calculation or a conversion to your own clients by usage

  • 5

    Your developers are busy with the product and the backend task keeps waiting

What's included

  • A specification before code

    We write down the input, the output, the errors and the expected volume. You approve the contract of the endpoint before development starts.

  • The function itself

    Code in Python or Node.js with tests on your real examples: a calculation, a file conversion, a lookup in an external source, a generated report.

  • An endpoint on MetaPlatho

    The function is deployed on the platform that runs our own public API. You call it over HTTP with an API key in a header.

  • Metering, limits and billing

    Every call is counted. Quotas, rate limits and payment per usage are already built into the platform and are not developed again for you.

  • Long jobs: queue and webhooks

    If the work takes longer than a request should, it runs as a background job. You poll its status or receive a webhook when it is done.

  • Backend services and integrations

    A separate service with its own database, an integration between your systems, an internal tool — built in your repository and deployed on your infrastructure or ours.

How the work goes

  1. 1

    You describe the function

    What goes in, what comes out, how often it is called. A few real examples are enough.

  2. 2

    Specification and price

    You get the endpoint contract, the development price and the price per call or per unit of work.

  3. 3

    Build and trial

    We build the function and give you a key. You try it against your real data and report what is off.

  4. 4

    Production

    You call the endpoint from your product and pay for usage. Monitoring and updates are on our side.

Questions

  • Python
  • FastAPI
  • Node.js
  • TypeScript
  • PostgreSQL
  • Redis
  • OpenAPI
  • Docker
  • Kubernetes
  • KEDA
  • GitHub Actions

Describe the task — get a plan and a price

Write what you have and what you need. We answer within one business day with questions or a concrete proposal.