Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

COR User Leaves API

The User Leaves API from COR — 4 operation(s) for user leaves.

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

Tagged areas include User Leaves. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 8 operations across 4 paths, and defines 8 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.projectcor.com/v1.

8 operations 4 paths 8 schemas 2 DELETE2 GET2 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.projectcor.com/v1
Authentication
HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 2

COR User Leaves API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 8

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

User Leaves 8
GET
/user/leaves
Get User Leaves
3 params → 200
POST
/user/leaves
Create User Leave
body → 200
DELETE
/user/leaves
Delete User Leave
body → 200
PUT
/user/leaves/{licenseId}
Update User Leave
1 param body → 200
GET
/company/leaves-types
Get Leave Types
2 params → 200
POST
/company/leaves-types
Create Leave Type
body → 200
DELETE
/company/leaves-types
Delete Leave Type
body → 200
PUT
/company/leaves-types/{leaveTypeId}
Update Leave Type
1 param body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Leave (11 properties), LeaveType (8 properties), LeaveInput (5 properties), PaginatedLeaveTypesResponse (5 properties). Each schema is shown below with its type and property counts.

LeaveUpdateInput
object
4 properties 4 required
LeaveInput
object
5 properties 4 required
LeaveDeleteInput
object
2 properties 2 required
Leave
object
11 properties
PaginatedLeaveTypesResponse
object
Paginated response for leave types list
5 properties
LeaveType
object
8 properties
LeaveTypeInput
object
1 property 1 required
LeaveTypeDeleteInput
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cor-user-leaves-api-openapi.yml Raw ↑

Other APIs COR publishes across the network.

COR Attachments API
COR Auth API
COR Brands API
COR Clients API
COR Collaborators API
COR Contacts API
COR Contract Positions API
COR Contracts API
COR Contracts Users API
COR Costs API
COR Estimates API
COR Fees API