Kombo Custom Endpoints API is one of 8 APIs that Kombo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Custom Endpoints. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.
This API exposes
18 operations
across 18 paths,
and defines 37 schemas.
It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against 2 base URLs: https://api.kombo.dev/v1, https://api.us.kombo.dev/v1.
18 operations18 paths37 schemas1 DELETE7 GET8 POST2 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.kombo.dev
Authentication
HTTP Bearer
Resource Areas
1
Authentication & Security 1
Kombo Custom Endpoints API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (ApiKey).
By default, every request must be authenticated.
ApiKey — Create an API key on the [Secrets](https://app.kombo.dev/secrets) page in the Kombo dashboard.
Paths & Operations 18
Across 18 paths, the API surfaces 18 operations — 1 DELETE, 7 GET, 8 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are PostCustomDatevPassthroughRequestBody (5 properties), PostCustomSilaeEmployeesEmployeeIdPayrollSupplementsRequestBody (4 properties), PutCustomDatevEmployeesEmployeeIdPreparePayrollRequestBody (4 properties), PostCustomDatevPushDataPayrollPositiveResponse (3 properties). Each schema is shown below with its type and property counts.
ID of the employee that should be updated. You can use their Kombo id or their ID in the remote system by prefixing it with remote: (e.g., remote:12312)
ID of the employee that should be updated. You can use their Kombo id or their ID in the remote system by prefixing it with remote: (e.g., remote:12312)
ID of the employee that should be updated. You can use their Kombo id or their ID in the remote system by prefixing it with remote: (e.g., remote:12312)
ID of the employee that should be updated. You can use their Kombo id or their ID in the remote system by prefixing it with remote: (e.g., remote:12312)
