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

Laurel Clients API

The Clients API from Laurel — 10 operation(s) for clients.

Laurel Clients API is one of 38 APIs that Laurel publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 13 operations across 10 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against the base URL https://api.laurel.ai/time/.

13 operations 10 paths 15 schemas 1 DELETE5 GET1 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.laurel.ai/time/
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Laurel Clients API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (ApiBearerAuth). By default, every request must be authenticated.

  • ApiBearerAuth — Enter access token

Paths & Operations 13

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

Clients 13
POST
/api/v1/clients/on-credentials-exchange
Client controller on credentials exchange v1
ClientController_onCredentialsExchange_v1 body → 201
POST
/api/v1/clientsdeprecated
creates a new client
ClientController_create_v1 body → 201
GET
/api/v1/clientsdeprecated
lists all existing clients
ClientController_getAll_v1 → 200
GET
/api/v1/clients/{clientId}deprecated
returns a specific client
ClientController_get_v1 1 param → 200
PATCH
/api/v1/clients/{clientId}
updates an existing client
ClientController_update_v1 1 param body → 200
DELETE
/api/v1/clients/{clientId}deprecated
deletes an existing client
ClientController_delete_v1 1 param → 200
POST
/api/v1/customers/{customerId}/clients/import
Clients controller import client V1 v1
ClientsController_importClientV1_v1 1 param body → 201
POST
/api/v1/customers/{customerId}/clients/batch
Clients controller import client batch V1 v1
ClientsController_importClientBatchV1_v1 2 params body → 201
GET
/api/v1/customers/{customerId}/clients
Customer client controller search v1
CustomerClientController_search_v1 9 params → 200
GET
/api/v1/customers/{customerId}/clients/external-id/{externalId}
Customer client controller get by external id v1
CustomerClientController_getByExternalId_v1 2 params → 200
GET
/api/v1/customers/{customerId}/clients/{clientId}
Customer client controller get client v1
CustomerClientController_getClient_v1 3 params → 200
POST
/api/v1/customers/{customerId}/clients/override-compliance-rules/affected-count
Customer client controller get affected count v1
CustomerClientController_getAffectedCount_v1 1 param body → 200
POST
/api/v1/customers/{customerId}/clients/override-compliance-rules
Customer client controller override compliance rules v1
CustomerClientController_overrideComplianceRules_v1 1 param body → 201

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are Client (19 properties), CreateClientDto (11 properties), Client_2 (11 properties), UpdateClientDto (9 properties). Each schema is shown below with its type and property counts.

PermissionDigest
object
3 properties 3 required
OnCredentialsExchangeResponseDto
object
5 properties 3 required
TenantDigest
object
3 properties 3 required
UpdateClientDto
object
9 properties
Client
object
19 properties 14 required
OnCredentialsExchangeRequestDto
object
3 properties 2 required
CreateClientDto
object
11 properties 8 required
ImportCustomerClientDto
object
6 properties 4 required
ImportCustomerClientsBatchDto
object
1 property 1 required
Object
object
OverrideComplianceRulesDto
object
3 properties 2 required
ImportCustomerClientDto_2
object
6 properties 4 required
ClientDto
object
7 properties 5 required
AffectedCountResponseDto
object
3 properties 3 required
Client_2
object
11 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

laurel-clients-api-openapi.yml Raw ↑

Other APIs Laurel publishes across the network.

Laurel Ably API
Laurel Activities API
Laurel Code Types API
Laurel Codes API
Laurel Customers API
Laurel DailySelectedInitiatives API
Laurel Data Retention Audits API
Laurel Delegators API
Laurel Entries API
Laurel Entry Date Restrictions API
Laurel Exports API
Laurel Health Check API
Where this information came from

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