Portbase

Portbase Organisation Data API

Api defining the operations a terminal/barge operator can do to retrieve organisation configuration. Basically these operations retrieve configuration data such as bollards, fixedwindows etc.

Documentation GitHub OpenAPI

Operations 1

POST /bollards Get bollards #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/portbase:portbase-organisation-data-api-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Portbase Organisation Data API
  version: '2.0'
  contact:
    name: Portbase hinterland team
    url: https://hcn.pcs.portbase.com
    email: hinterland@portbase.com
  x-logo:
    url: Portbase_WB_RGB.png
    altText: Portbase logo
  description: 'Operations tagged Organisation Data API across 2 of this provider''s published API definitions: portbase-hinterland-container-notification-v2.json, portbase-hinterland-container-notification-openapi.yml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.portbase.com/hcn
  description: Production server
- url: https://api.kt.portbase.com/hcn
  description: Test server
tags:
- name: Organisation Data API
  description: Api defining the operations a terminal/barge operator can do to retrieve organisation configuration. Basically these operations retrieve configuration data such as bollards, fixedwindows etc.
paths:
  /bollards:
    post:
      tags:
      - Organisation Data API
      summary: Get bollards
      description: '''Terminal only''. Endpoint used to get bollards for a terminal. Only bollards for your organisation are returned!'
      operationId: _01_getBollards
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/GetBollards'
      responses:
        '200':
          description: successful operation
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Bollard'
    servers:
    - url: https://api.portbase.com/hcn
      description: Production server
    - url: https://api.kt.portbase.com/hcn
      description: Test server
components:
  schemas:
    Coordinates:
      required:
      - latitude
      - longitude
      type: object
      properties:
        latitude:
          maximum: 90
          minimum: -90
          type: number
          description: The decimal degrees from the equator
        longitude:
          maximum: 180
          minimum: -180
          type: number
          description: The decimal degrees from the Prime Meridian (Greenwich)
      description: The geographical position of the bollard.
      readOnly: true
      deprecated: true
    Bollard:
      required:
      - bicsCode
      - metersToNextBollard
      - number
      type: object
      properties:
        bicsCode:
          type: string
          description: The Binnenvaart Informatie- en Communicatie Systeem (BICS) code for the Terminal.
        number:
          type: string
          description: Distinct bollard description, unique per quay. Can be just the bollard number or a text prefix with the bollard number.
          example: DDE-59
        coordinates:
          title: ''
          type:
          - ''
          - 'null'
          description: The geographical position of the bollard.
          readOnly: true
          deprecated: true
          allOf:
          - $ref: '#/components/schemas/Coordinates'
        metersToNextBollard:
          type: number
          description: The number of meters to the next bollard in the sequence.
          readOnly: true
        mooringSide:
          type:
          - string
          - 'null'
          description: A ship’s mooring side for mooring near this bollard.
          readOnly: true
          enum:
          - port
          - starboard
      description: '`Integral planning` Physical location on the quay.'
    GetBollards:
      type: object
      description: Retrieve the bollards for your organisation.
externalDocs:
  description: The connection instructions, use cases per mode of transport, and changelog can be found here.
  url: linkmenu.html
x-refined-from:
- portbase-hinterland-container-notification-v2.json
- portbase-hinterland-container-notification-openapi.yml