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

Bokio customers API

Operations for managing customer data

Bokio customers API is one of 16 APIs that Bokio publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customers. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against a single base URL, https://api.bokio.se/v1.

5 operations 2 paths 4 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.bokio.se/v1
Authentication
HTTP Bearer, OAuth 2.0, HTTP Basic
Contact
Terms of Service
Resource Areas
1

Authentication & Security 3

Bokio customers API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (tokenAuth). It supports OAuth 2.0 (access_token) using the clientCredentials and authorizationCode flows, exposing 24 scopes. It accepts HTTP basic authentication (client_auth). By default, every request must be authenticated.

Paths & Operations 5

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

customers 5

Operations for managing customer data

POST
/companies/{companyId}/customers
Create a customer
post-customer 1 param body → 200400
GET
/companies/{companyId}/customers
Get customers
get-customer 4 params → 200
GET
/companies/{companyId}/customers/{customerId}
Get a customer
get-customers-customerId 2 params → 200404
PUT
/companies/{companyId}/customers/{customerId}
Update a customer
put-customer 2 params body → 200400
DELETE
/companies/{companyId}/customers/{customerId}
Delete a customer
delete-customer 2 params → 204

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are customer (10 properties), addressWithCountrySubdivision (6 properties), apiError (4 properties), pagedResponse (3 properties). Each schema is shown below with its type and property counts.

customer
object
10 properties 2 required
pagedResponse
object
3 properties
addressWithCountrySubdivision
object
6 properties 4 required
apiError
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bokio-customers-api-openapi.yml Raw ↑

Other APIs Bokio publishes across the network.

Bokio authorization API
Bokio bank-payments API
Bokio chart-of-accounts API
Bokio company-information API
Bokio connections API
Bokio credit-notes API
Bokio fiscal-years API
Bokio invoices API
Bokio items API
Bokio journal-entries API
Bokio sie-files API
Bokio supplier-invoices API
Where this information came from

This is an independent, third-party profile of Bokio customers 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.