Skip to content
NOStudio (opens in a new tab)
Menu

RestAPI.com · The platform underneath

Everything you ship stands on this.

Model your data once and documented REST endpoints exist the moment you save — with logins, permissions and server-side logic part of the structure rather than bolted on months later. It is what Softeria Studio builds on, available on its own.

The RestAPI.com developer portal’s data model: product, warehouse and manufacturer collections with their typed fields, the links between them and a view built on products
Backend code
0 lines
Between a saved collection and a documented, live endpoint
Yours
100%
Of your data and structure, exportable, always
Plans from
NOK 250
A month, excluding MVA. The free plan is for apps built with Studio for Business
Answered in
< 1 hr
By the people who build the platform, not a queue

In the product

The RestAPI.com developer portal as it is, in a demo workspace: a collection’s fields and types, a request and its response, and the overview of the whole API.

  • The RestAPI.com portal’s collection editor: the product collection with its fields, types and the link to manufacturerThe RestAPI.com portal’s collection editor: the product collection with its fields, types and the link to manufacturer

    Define the data

  • The RestAPI.com REST explorer: a GET request for products and its JSON response, with the linked manufacturer includedThe RestAPI.com REST explorer: a GET request for products and its JSON response, with the linked manufacturer included

    Call the API

  • The RestAPI.com portal overview: counts of collections, views, queries and functions, billing for the period and data storage over timeThe RestAPI.com portal overview: counts of collections, views, queries and functions, billing for the period and data storage over time

    See the whole of it

Nobody compliments the layer underneath. Everything is standing on it anyway.

What it holds up

Databases, endpoints, permissions, logins, hosting, backups. Months of work no customer will ever thank you for, and the first thing that sinks a product when it is done badly. RestAPI.com is that whole layer, run as a managed platform.

  • Controllers, route files and request plumbingGone
  • API documentation that has to be kept in step by handGone
  • A user table, a password reset and a session storeGone
  • Migration scripts run by hand on a Friday afternoonGone
  • A second service just to reach the system you already runGone

Save the table. The API already exists.

Table in, API out

Nothing to generate, nothing to deploy, nothing to keep in sync. This is the whole exchange.

What you define · bookings

customer
relation→ customers
kayak
relation→ kayaks
startsAt
datetime
hours
integer
status
stringheld · paid · out · returned
totalNok
decimal

id · created · createdBy · modified · modifiedBy — set by the platform, never by you.

What you get, immediately

  • GET /api/bookings
  • GET /api/bookings/{id}
  • POST /api/bookings
  • PATCH /api/bookings/{id}
  • DELETE /api/bookings/{id}
  • GET /api/_openapi

GET /api/bookings?filter=status eq 'paid'&sortBy=startsAt-&pageSize=50

And the rules on top of it

  • staff may read every booking at their own location
  • a customer may only ever read their own bookings
  • nobody outside the company sees a single row

Filtering, sorting, searching, paging and field selection are query parameters, not endpoints somebody has to write. The OpenAPI document is generated from the same definition, so your frontend can be typed against the API rather than hoping it matches.

Three things that keep it honest as it grows.

And then it stays right

  • Typed, not guessed

    Generate TypeScript types straight from the live API, so a renamed field becomes a build error in your editor instead of a bug your customer finds.

  • Documented on the way out

    Every collection publishes an OpenAPI description automatically. The documentation cannot fall behind the implementation, because it is generated from it.

  • Safe to change

    Schema changes that would break existing data or existing callers are flagged before they run, rather than discovered afterwards in production.