I wire custom admin screens to your existing REST API, webhooks, or Postgres. Packages include a capped number of connections; a new backend is quoted separately.
- REST, webhooks, or Postgres
- Secrets stay off the client
- Connection cap in the package
Admin API integration: wire staff screens to the APIs you already have
Admin API integration is the work of connecting an internal admin to REST APIs, webhooks, or a database that already holds your product data. The value is not another hosted CMS. It is lists and forms that call list, get, create, and update on your backend — with errors, pagination, and auth handled correctly. Viewport Solutions scopes API connections as first-class items in internal admin packages.
Teams search for admin API, internal API admin, or “admin panel for existing API” when the public app is live but staff still cannot operate it. If your API already returns JSON for leads and users, a custom admin is usually faster than rebuilding a backend. Package tiers include one, two, or three API or webhook connections; more is custom.
Good admin API integration includes timeouts, empty states when the API is down, and no secrets in the browser. Server routes or your existing BFF patterns keep keys off the client. Viewport Solutions follows whatever you already use.
Webhooks are connections too: inbound events that should show up as rows or status changes. If a connection is really “build us an API,” that is a different quote. The landing copy is explicit so Ads traffic does not buy the wrong product.
What counts as a connection
Reading or writing a system you already run: a REST API, a webhook receiver, or Postgres. OpenAPI or a Postman collection speeds the quote. If the API is undocumented, scoping includes time to map endpoints — say so in the brief.
Auth against your API — session cookie, bearer token, API key on the server — is part of wiring, not a surprise. Role checks in the admin still need matching checks on the API. If the API has no authorization, that risk is called out in scope.
Third-party APIs (Stripe, a form tool, a CRM) count as connections when the admin must read or write them. Rate limits and sandbox keys belong in the written scope.
Spreadsheets are not an API. They can be a one-time import or a staging data source; ongoing sheet sync is specified if you truly need it.
Packages, custom, and honesty about backends
Starter includes one API or database connection. Standard two. Plus three. That is enough for many products: your app API plus a webhook. A new domain model from zero is custom admin API / backend work.
Viewport Solutions will not pretend a €1,400 package includes designing a public API, webhooks, and an admin. The FAQ and packages page exist to filter that.
You still get the portal, written scope, and 50/50 payment after approval. Integration work is visible as progress updates — “leads table is reading the API; edit form next.”
English replies. Stripe, PayPal, or bank after scope.
Send the API, get a written admin quote
The fastest brief is: staging URL, how staff log in today, endpoints or DB tables, and the screens you need. Optional: OpenAPI file.
You receive a quote that lists connections and screens. Approve, pay the starting 50%, and track the build.
Related pages: CRUD admin, internal admin development, Rails or Nuxt developer if the API itself needs work.
Nothing is due today.
When to hire for admin API integration
The API exists; the admin does not
Partners or the customer app already consume JSON. Staff still use SQL or sheets.
You have webhooks with no UI
Events land in logs. You need them as rows with status and retry context.
Multiple systems, one staff screen
A lead in your DB plus a payment in Stripe should appear in one admin. That is two connections.
You want a fixed connection cap
Packages price one to three connections so the quote is not an open integration retainer.
Frequently asked questions
Do you build APIs as well as admins?
Small wiring to an existing API is in the packages. Designing and building a new backend is custom and quoted separately.
What if we only have Postgres?
A database can be the connection. Say so in the brief.
GraphQL or REST?
Either, if you already have it. The quote follows your API, not a preferred fashion.
Can you work from OpenAPI?
Yes. A spec makes estimates faster and more accurate.
Are webhooks included?
They count toward the connection cap in the package. Extra webhooks are custom lines.
How do I start?
Send screens plus how data is accessed today. Written quote in 1–2 business days, €0 until you approve.