Skip to content
NAVICORE ONE
Menu

NAVICORE ONE company operating system · Part 31 · Developers & extensions

API & developer platform

Connect NAVICORE ONE to your own systems with a documented, permissioned API and webhooks.

In build

What this page describes is the intended scope from the product specification. The status label shows how far along this area is.

API & developer platform

Illustrative layout, not a live screenshot.

What it is

A REST API with authentication, API keys, API permissions, rate limiting and versioning. Webhooks with retries and logs, OpenAPI and developer documentation, and OAuth applications. A plugin SDK is planned for the future.

The problem

A business system that cannot talk to anything else ends up with data typed in twice.

What NAVICORE ONE does

NAVICORE ONE offers a versioned REST API with keys, permissions and rate limits, and webhooks that retry and keep logs.

The result

Your systems can read and react to NAVICORE ONE, within limits you control.

Who uses it, and when

Developers
When building their own connections to NAVICORE ONE
Admins
When creating API keys and deciding what each key may do
Security reviewers
When checking which API keys and webhooks exist

How it works, step by step

Connecting a system

Sequence assembled from this part's listed functions, in plain language.
  1. 1

    Create an API key

  2. 2

    Set its permissions

  3. 3

    Call the REST API

    Versioned, with rate limits

  4. 4

    Webhooks notify your system

    Retries and logs included

Key functions

  • REST API

    A standard way for software to talk to NAVICORE ONE.

  • Authentication & API keys

    Prove who is calling.

  • API permissions

    Limit what each key can do.

  • Rate limiting

    Protect the service from overuse.

  • API versioning

    Change the API without breaking existing connections.

  • Webhooks, retries & logs

    Be told when something happens, with a record of delivery.

  • OpenAPI & developer documentation

    Machine-readable and human-readable descriptions of the API.

  • OAuth applications

    Let other apps ask for access on a person's behalf.

  • Plugin SDK

    Planned for the future.

Full scope from the product specification (13 items)
  • REST API
  • Authentication
  • API keys
  • API permissions
  • Rate limiting
  • API versioning
  • Webhooks
  • Webhook retries
  • Webhook logs
  • OpenAPI
  • Developer documentation
  • OAuth applications
  • Future plugin SDK

How it connects to other parts

See it in action

Ask for a demo, or tell us how you would like to partner.