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 Customers API

The Customers API from Laurel — 14 operation(s) for customers.

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

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

This API exposes 20 operations across 14 paths, and defines 24 schemas. It is described by OpenAPI 3.0.0, at version 1.

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

20 operations 14 paths 24 schemas 3 DELETE8 GET3 PATCH5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Laurel Customers 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 20

Across 14 paths, the API surfaces 20 operations — 3 DELETE, 8 GET, 3 PATCH, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Customers 20
POST
/api/v1/customers
CustomerController_create_v1 1 param body → 201
GET
/api/v1/customers
List all customers
CustomerController_getAll_v1 1 param → 200
GET
/api/v1/customers/lookup
CustomerController_lookup_v1 3 params → 200
GET
/api/v1/customers/{customerId}
Get a specific customer
CustomerController_get_v1 1 param → 200
PATCH
/api/v1/customers/{customerId}
Update a specific customer
CustomerController_update_v1 1 param body → 200
GET
/api/v1/customers/{customerId}/tenant
CustomerController_getTenant_v1 1 param → 200
POST
/api/v1/customers/{customerId}/identities
CustomerController_createNewCustomerIdentity_v1 1 param body → 201
POST
/api/v1/customers/{customerId}/connections
CustomerController_createConnection_v1 1 param body → 201
PATCH
/api/v1/customers/{customerId}/connections/{connectionId}
CustomerController_updateConnection_v1 2 params body → 200
DELETE
/api/v1/customers/{customerId}/connections/{connectionId}
CustomerController_deleteConnection_v1 2 params → 200
PATCH
/api/v1/customers/{customerId}/connections/{connectionId}/scim
Enable or disable SCIM provisioning on a connection
CustomerController_updateConnectionScim_v1 2 params body → 200
PUT
/api/v1/customers/{customerId}/connections/{connectionId}/domains
Update the domains (FQDNs) for a connection, propagating to Auth0 HRD
CustomerController_updateConnectionDomains_v1 2 params body → 200
GET
/api/v1/customers/{customerId}/regiondeprecated
CustomerController_getCustomerRegion_v1 1 param → 200
GET
/api/v1/customers/{customerId}/clients
CustomerClientController_getCustomerClients_v1 1 param → 200
POST
/api/v1/customers/{customerId}/clients
creates a new client for the given customer
CustomerClientController_create_v1 1 param → 201
GET
/api/v1/customers/{customerId}/clients/{clientId}
CustomerClientController_getCustomerClientById_v1 2 params → 200
DELETE
/api/v1/customers/{customerId}/clients/{clientId}
CustomerClientController_deleteCustomerClientById_v1 2 params → 200
GET
/api/v1/customers/{customerId}/managed-clients
Lists all customer-managed clients for the given customer
CustomerManagedClientController_getCustomerManagedClients_v1 1 param → 200
POST
/api/v1/customers/{customerId}/managed-clients
Creates a new customer-managed client for the given customer
CustomerManagedClientController_create_v1 1 param body → 201
DELETE
/api/v1/customers/{customerId}/managed-clients/{clientId}
Deletes a customer-managed client by ID
CustomerManagedClientController_deleteCustomerManagedClientById_v1 2 params → 200

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are Customer (14 properties), CreateCustomerDto (10 properties), UpdateCustomerDto (9 properties), CustomerManagedClientResponseDto (9 properties). Each schema is shown below with its type and property counts.

MicrosoftIdentityApi
object
1 property 1 required
TenantDigest
object
3 properties 3 required
UpdateConnectionDto
object
3 properties
UpdateConnectionDomainsDto
object
1 property 1 required
AzureStrategy
object
6 properties 5 required
Connection
object
7 properties 6 required
Customer
object
14 properties 9 required
UpdateCustomerDto
object
9 properties
ConnectionScimSetupResponseDto
object
2 properties
ClientResponseDto
object
4 properties 4 required
UpdateConnectionScimDto
object
1 property 1 required
CustomerVertical
string
if set, updates customer's vertical
DatabaseStrategy
object
1 property 1 required
CustomerSegment
string
if set, updates customer's segment
AzureIdentityApi
object
2 properties 2 required
SamlStrategy
object
8 properties 7 required
AdfsStrategy
object
4 properties 4 required
CustomerRegionResponseDto
object
1 property 1 required
CreateConnectionDto
object
3 properties 2 required
CustomerManagedClientResponseDto
object
9 properties 5 required
Identity
object
3 properties 2 required
CreateCustomerDto
object
10 properties 7 required
CustomerTenantResponse
object
1 property 1 required
CreateCustomerManagedClientDto
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

laurel-customers-api-openapi.yml Raw ↑

Other APIs Laurel publishes across the network.

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

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