How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Fortnox Suppliers API

Supplier register.

Fortnox Suppliers API is one of 12 APIs that Fortnox publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Suppliers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 3.0.

Requests are made against a single base URL, https://api.fortnox.se/3.

4 operations 2 paths 3 schemas 2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0
Base URL
https://api.fortnox.se/3
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Fortnox Suppliers API declares 2 security schemes for authenticating requests. An API key is passed in the header as Access-Token (accessToken). An API key is passed in the header as Client-Secret (clientSecret). By default, every request must be authenticated.

  • accessToken — OAuth2 Access-Token (Bearer JWT, valid 1 hour) obtained via the Authorization Code Flow from https://apps.fortnox.se/oauth-v1/token. Sent in the Access-Token h…
  • clientSecret — The Client-Secret issued to your registered Fortnox developer application. Sent in the Client-Secret header alongside the Access-Token on every request.

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Suppliers 4

Supplier register.

GET
/suppliers
List suppliers
listSuppliers 2 params → 200
POST
/suppliers
Create a supplier
createSupplier body → 201
GET
/suppliers/{SupplierNumber}
Retrieve a supplier
getSupplier 1 param → 200404
PUT
/suppliers/{SupplierNumber}
Update a supplier
updateSupplier 1 param body → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Supplier (12 properties), MetaInformation (3 properties), ErrorResponse (1 property). Each schema is shown below with its type and property counts.

MetaInformation
object
Pagination metadata returned on list endpoints.
3 properties
Supplier
object
A supplier in the supplier register.
12 properties 1 required
ErrorResponse
object
Fortnox error envelope.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fortnox-suppliers-api-openapi.yml Raw ↑

Other APIs Fortnox publishes across the network.

Fortnox Topics WebSocket API
Fortnox Accounts API
Fortnox Articles API
Fortnox Customers API
Fortnox Financial Years API
Fortnox Invoices API
Fortnox Offers API
Fortnox Orders API
Fortnox Projects API
Fortnox Supplier Invoices API
Fortnox Vouchers API
Where this information came from

This is an independent, third-party profile of Fortnox Suppliers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.