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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/sevdesk-order-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.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: sevdesk CheckAccount Order API
description: 'The sevdesk API is a RESTful interface to the sevdesk cloud accounting and invoicing platform. Every function and every piece of data available in the sevdesk web application can also be driven through this API - contacts, invoices, orders, credit notes, vouchers (receipts), bank check accounts and transactions, parts (inventory), and tags. All requests are authenticated with a per-administrator API token, passed as the value of an `Authorization` header. Nested resources can be pulled in with the `embed` query parameter.
This OpenAPI document is a grounded, representative subset authored by API Evangelist from sevdesk''s official OpenAPI specification (openapi 3.0.0, reported API version 2.0.0, served at https://my.sevdesk.de/api/v1). The paths, HTTP methods, operationIds, and the apiKey security scheme are taken directly from the official specification; request and response schemas here are simplified representations of the far richer official models. See review.yml for confirmed-vs-modeled detail.'
version: '1.0'
contact:
name: sevdesk
url: https://api.sevdesk.de/
servers:
- url: https://my.sevdesk.de/api/v1
description: sevdesk main application instance
security:
- api_key: []
tags:
- name: Order
description: Orders, quotations, and packing lists.
paths:
/Order:
get:
operationId: getOrders
tags:
- Order
summary: Retrieve orders
description: Retrieves a list of orders (quotations, order confirmations).
parameters:
- $ref: '#/components/parameters/Limit'
- $ref: '#/components/parameters/Offset'
- $ref: '#/components/parameters/Embed'
responses:
'200':
description: A list of orders.
content:
application/json:
schema:
$ref: '#/components/schemas/ObjectList'
'401':
$ref: '#/components/responses/Unauthorized'
/Order/Factory/saveOrder:
post:
operationId: createOrder
tags:
- Order
summary: Create a new order
description: Creates a new order together with its positions.
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: true
responses:
'201':
description: The created order.
content:
application/json:
schema:
$ref: '#/components/schemas/ObjectResponse'
'401':
$ref: '#/components/responses/Unauthorized'
/Order/{orderId}:
parameters:
- $ref: '#/components/parameters/OrderId'
get:
operationId: getOrderById
tags:
- Order
summary: Find order by ID
description: Retrieves a single order by its ID.
responses:
'200':
description: The requested order.
content:
application/json:
schema:
$ref: '#/components/schemas/ObjectResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
put:
operationId: updateOrder
tags:
- Order
summary: Update an existing order
description: Updates an existing order.
requestBody:
required: true
content:
application/json:
schema:
type: object
additionalProperties: true
responses:
'200':
description: The updated order.
content:
application/json:
schema:
$ref: '#/components/schemas/ObjectResponse'
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
delete:
operationId: deleteOrder
tags:
- Order
summary: Deletes an order
description: Deletes an order.
responses:
'200':
description: Deletion confirmation.
'401':
$ref: '#/components/responses/Unauthorized'
'404':
$ref: '#/components/responses/NotFound'
components:
responses:
Unauthorized:
description: Missing or invalid API token.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
NotFound:
description: The requested resource was not found.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
parameters:
Limit:
name: limit
in: query
required: false
description: Limits the number of entries returned.
schema:
type: integer
Embed:
name: embed
in: query
required: false
description: Comma-separated list of nested resources to embed fully in the response instead of returning only their id and objectName.
schema:
type: string
OrderId:
name: orderId
in: path
required: true
description: The ID of the order.
schema:
type: integer
Offset:
name: offset
in: query
required: false
description: Number of entries to skip for pagination.
schema:
type: integer
schemas:
Error:
type: object
properties:
error:
type: object
properties:
message:
type: string
code:
type: integer
ObjectList:
type: object
description: Standard sevdesk list envelope. The objects array carries the requested resources.
properties:
objects:
type: array
items:
type: object
additionalProperties: true
ObjectResponse:
type: object
description: Standard sevdesk single-object envelope.
properties:
objects:
type: object
additionalProperties: true
securitySchemes:
api_key:
type: apiKey
name: Authorization
in: header
description: Per-administrator sevdesk API token - a 32-character hexadecimal string found in the sevdesk web app under user settings. Passed as the raw value of the `Authorization` header (no `Bearer` prefix). Tokens have an infinite lifetime.