Building your own technical gateway

Have a custom API built for your software or platform

A custom API makes your software connectable: customers, partners or your own app can read data or perform actions within rules you set. OmniTechs designs the endpoints, access rights, validation and documentation and builds them as part of your software. Need two existing systems to talk? Then API integration is the right page.

By Sina Esfahani · Practice page by OmniTechs in Groningen; amounts follow the current price contract · Reviewed .

What does custom API development cost?

A custom API is tailored to your existing software, so the price follows from the number of endpoints, the permission model and the data exposed. We start with a Solution Sprint of €1,250 excl. VAT that fixes endpoints, rights and documentation and gives you a fixed build price. Larger programmes run through the COMPANY annual plan.

If you only need data to move between two systems, an integration is cheaper and faster than a new API. The comparison table below helps you choose.

  • Design and fixed price: Solution Sprint €1,250 excl. VAT
  • Build: fixed quote per set of endpoints, documentation and tests included
  • Operation: versioning and monitoring via a Care plan
  • Only moving data? Choose an API integration

What is a custom API?

A custom API is a technical gateway your own application offers so a website, app, internal system or external partner can read data or perform actions in a controlled way. Besides endpoints, that includes a contract for authentication, validation, error handling, documentation and future change.

Custom API development is worth investigating when

  • your software, platform or process has no controlled technical gateway that other software needs
  • several consumers — your own app, a portal, a partner — must use the same data or action in a controlled way
  • it is clear who owns endpoints, rights and changes after delivery
  • the underlying data and business rules are stable enough to fix as a contract

Choose another route first when

  • the technical gateways on both sides already exist and only the connection between them is missing — that is an API integration
  • one fixed, known consumer is served by a one-off export, import or direct database access inside the same application
  • the process or data definition still changes continuously
  • nobody can own operations, changes and incidents after delivery

Custom API, integration or something simpler?

Build an API, integrate existing ones, or try something smaller first?

Not every need for data exchange requires a new API. Who already offers the data and who needs it determines the smallest responsible form.

Decision aid for a custom API, an integration or a simpler alternative
SituationResponsible first stepWhat must be clear first
Two existing systems with their own APIs must exchange dataFocused API integration between existing gatewaysSee the separate API integration page
Your software has no technical gateway yet and a web or mobile app must reach it safelyA custom API as part of that web or mobile appEndpoints, data model, authentication and error handling
An external partner needs a limited, fixed selection of your business dataA bounded partner API with its own rights and limitsWhat is and is not visible, and who revokes access
Several of your apps — web, mobile, internal dashboard — must share the same data and rulesOne underlying API those apps call togetherOwnership of the data model and versioning across apps
One internal app uses the data directly and nobody else needs itNo separate API — direct access inside that application is enoughReassess as soon as a second consumer appears

Relevant offer at a glance

Solution Sprint

Paid scope work

€1,250 excl. VAT

An organisation with a non-standard process or product problem that first needs to investigate users, dependencies, risks and scope.

Independent project work that clarifies the problem, users, dependencies, risks and scope before an implementation price is provided.

  • A 60–90-minute problem and process workshop
  • Current-state workflow map
  • User and stakeholder definition

Implementation not included

Our own implementation

One customer workspace, the same API for your own tools

Our customer workspace uses a versioned API for print applications and Smart Links. The browser sends the same validated requests that your own automation can send. A public STL/3MF calculator provides file geometry and an estimate; an authenticated application adds your address, quality, quantity, note and pictures. The workshop still reviews the request before accepting production.

You can inspect the OpenAPI contract, create a token with read or write permissions, and revoke it in the panel. A token for one Smart Link lets your AI read and edit that draft through MCP. Revision checks prevent an older edit from overwriting a newer one; you review and publish the result yourself. This is our own product engineering, not an attributed customer case.

  • Inspect requests, fields, permissions and error responses in the API guide
  • Paid generation requires configured providers and funded acceptance; check availability in the panel
  • Website platform drafts can be saved; self-service provisioning is not available yet

First check whether the needed gateway already exists

If an existing API already offers the needed data and rights, a small read test can verify that. If that contract is missing, you must develop it and agree it with the consumer. A successful call to an existing API is therefore not proof that a custom API is required.

When is a custom API worth investigating?

The question usually appears when software you already have or are having built — a web app, mobile app or internal system — must expose data or actions to something else. Without an API that often happens through direct database access, a shared file or manual retyping: workable for one consumer, fragile once a second appears or the underlying data changes.

An API adds a fixed layer between data and consumers: who may read or change what, in which shape, and what happens on error. That is design work, not an automatic benefit. For one stable internal application without a second consumer, direct access is often still responsible.

Illustrative examples of a custom API

A customer portal can call your backend API after login to return only orders, documents or status that customer may see. A mobile app can use the same API to read and sync when connectivity returns. An internal scanner can post a stock change that is validated before it is stored. An external partner can use a separate, limited API for exactly the agreed slice of your data.

These are illustrative patterns, not client cases or a list of supported platforms. Which form of custom API fits depends on existing software, the data model, users and the parties that will consume it.

  • Web app or portal: your backend exposes data to the browser application
  • Mobile app: the same or a derived API for read, write and sync
  • Internal system: a scanner, till or other device posts a controlled event
  • External partner: a bounded, separately secured API for an agreed data slice

An API is a contract, not a loose endpoint

One working call does not prove a usable API. A durable contract states which endpoints exist, which fields are required or optional, what a valid response is and what a caller sees on error. Without those agreements the first change breaks every consumer at once, without warning.

As more consumers appear — a second app, a partner, a new internal tool — that contract matters more than the first implementation. Versioning, backward compatibility and a planned deprecation path belong from the start, even with one consumer.

Frequently asked questions about custom API development

What is the difference between a custom API and an API integration?

A custom API is a gateway your software offers. An API integration connects gateways that already exist on both sides. If both APIs already exist, start with integration.

Do you publish a fixed price for custom API development?

No. Price depends on endpoints, data model, authentication, consumers and operations. OmniTechs first bounds one usable API route, then quotes separately.

Can every system expose an API?

No. It depends on the software you own or control, data quality, security constraints and who will operate the contract after delivery.

What is the difference between API development and API integration?

A custom API is a gateway on your software that others connect to. An API integration uses the existing APIs of two systems to exchange data. If you offer something yourself you need an API; if you only need to connect, you need an integration.

How long does building an API take?

A first version with a limited set of endpoints, authentication and documentation is usually ready four to six weeks after the Sprint. Every extension afterwards is a scoped assignment.

Start from the consumer that needs the gateway.

Bring which system must call what, who owns the data after delivery, and whether an API already exists on either side. That is enough for a free first assessment.