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

Buk Leaves API

The Leaves API from Buk — 4 operation(s) for leaves.

Buk Leaves API is one of 66 APIs that Buk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Leaves. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 7 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://demo.buk.cl/api/v1/chile.

7 operations 4 paths 10 schemas 2 DELETE4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://demo.buk.cl/api/v1/chile
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Buk Leaves API declares 1 security scheme for authenticating requests. An API key is passed in the header as auth_token (auth_token).

Paths & Operations 7

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

Leaves 7
GET
/absences/licence/types
Listar tipos de leaves
2 params → 200
GET
/absences/licence/types/{id}
Ver un tipo de licencia
1 param → 200404400
GET
/absences/licence
List leaves
4 params → 200400
POST
/absences/licence
Create a leave
1 param → 201400
DELETE
/absences/licence
Delete leaves
3 params → 200404400
GET
/absences/licence/{id}
View leave
1 param → 200404400
DELETE
/absences/licence/{id}
Delete a leave
1 param → 200404400

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Absence::Response (14 properties), LicenceType::Response (11 properties), Absence::Request (10 properties), Pagination (4 properties). Each schema is shown below with its type and property counts.

LicenceType::Response
object
11 properties
LicenceType
object
1 property
MedicIdentifier
object
1 property
Absences::Licence::Response
Absences::Licence::Request
bad_request
object
1 property
Absence::Response
object
14 properties 2 required
LicenceBase
object
3 properties 2 required
Pagination
object
4 properties
Absence::Request
object
10 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

buk-leaves-api-openapi.yml Raw ↑

Other APIs Buk publishes across the network.

Buk Absences requests API
Buk Accounting Structures API
Buk Applicant API
Buk Application API
Buk Benefits API
Buk Capacitaciones API
Buk Cargos API
Buk Centralized accounting API
Buk Centro de costo API
Buk Clockings API
Buk Colaboradores API
Buk Créditos API
Where this information came from

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