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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Laurel

Laurel Users API

The Users API from Laurel — 28 operation(s) for users.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 35 operations across 28 paths, and defines 38 schemas. It is described by OpenAPI 3.0.0, at version 1.

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

35 operations 28 paths 38 schemas 2 DELETE12 GET5 PATCH15 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 Users 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 35

Across 28 paths, the API surfaces 35 operations — 2 DELETE, 12 GET, 5 PATCH, 15 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 35
GET
/api/v1/customers/{customerId}/users
returns all users for a customer, filtered by optional search parameter
CustomerUserController_search_v1 3 params → 200
GET
/api/v2/customers/{customerId}/users
CustomerUserController_searchV2_v2 6 params → 200
GET
/api/v1/customers/{customerId}/users-lite
CustomerUserController_searchLite_v1 3 params → 200
GET
/api/v1/customers/{customerId}/users/by-ids
Get multiple users by their IDs
CustomerUserController_getUsersByIds_v1 2 params → 200
GET
/api/v1/customers/{customerId}/users/lookup
CustomerUserController_lookupUser_v1 1 param → 200
POST
/api/v1/customers/{customerId}/users/batch/lookup
Look up multiple users by identities
CustomerUserController_lookupUsersBatch_v1 1 param body → 200
POST
/api/v1/customers/{customerId}/users/translate-timekeeper-ids
Translate timekeeper IDs to user IDs
CustomerUserController_translateTimekeeperIdsToUserIds_v1 1 param body → 201
POST
/api/v1/customers/{customerId}/users/lookup/identitydeprecated
CustomerUserController_lookupUserIdentityType_v1 1 param body → 200
GET
/api/v2/customers/{customerId}/users/lookup/identity
CustomerUserController_lookupUserByIdentity_v2 3 params → 200
GET
/api/v1/customers/{customerId}/users/{userId}/identities
CustomerUserController_lookupUserIdentity_v1 2 params → 200
POST
/api/v1/customers/{customerId}/users/{userId}/identities
CustomerUserController_createNewUserIdentity_v1 2 params body → 201
PUT
/api/v1/customers/{customerId}/users/{userId}/identities
CustomerUserController_updateUserIdentity_v1 2 params body → 200
PATCH
/api/v1/customers/{customerId}/users/{userId}/super-delegate
CustomerUserController_setUserSuperDelegateStatus_v1 2 params body → 200
GET
/api/v1/customers/{customerId}/users/{userId}
returns a user by its id
CustomerUserController_get_v1 2 params → 200
PATCH
/api/v1/customers/{customerId}/users/{userId}
updates a user
CustomerUserController_update_v1 2 params body → 200
DELETE
/api/v1/customers/{customerId}/users/{userId}
deletes a user
CustomerUserController_delete_v1 6 params → 200
PATCH
/api/v2/customers/{customerId}/users/{userId}
CustomerUserController_updateV2_v2 2 params body → 200
PATCH
/api/v1/customers/{customerId}/users/{userId}/status
CustomerUserController_updateStatus_v1 2 params body → 200
POST
/api/v1/customers/{customerId}/users/{userId}/identities/bulk
Add multiple identities to a user
CustomerUserController_createBulkUserIdentities_v1 2 params body → 200
POST
/api/v1/customers/{customerId}/users/{userId}/email-aliases
Add email aliases
CustomerUserController_createEmailAliases_v1 2 params body → 201
DELETE
/api/v1/customers/{customerId}/users/{userId}/email-aliases
Remove an email alias
CustomerUserController_deleteEmailAlias_v1 3 params → 200
GET
/api/v1/customers/{customerId}/users/{userId}/email-aliases
Get email aliases
CustomerUserController_getEmailAliases_v1 2 params → 200
POST
/api/v1/customers/{customerId}/users/importdeprecated
CustomerUserController_deprecatedImport_v1 1 param body → 201
POST
/api/v2/customers/{customerId}/users/import
CustomerUserController_importV2_v2 1 param body → 201
POST
/api/v1/customers/{customerId}/users/batch/importdeprecated
CustomerUserController_postUserData_v1 1 param body → 201
POST
/api/v2/customers/{customerId}/users/batch/importdeprecated
CustomerUserController_postUserDataV2_v2 1 param body → 201
POST
/api/v1/users
creates a user for a given customer
UserController_create_v1 1 param body → 201
GET
/api/v1/users/lookupdeprecated
looks a user up by their external identity
UserController_lookup_v1 3 params → 200
POST
/api/v1/users/on-auth
called by auth0 when tokens are generated
UserController_onAuth_v1 body → 200
POST
/api/v1/users/on-broker-auth
called by the auth0 token-exchange action during broker-based login
UserController_onBrokerAuth_v1 body → 200
GET
/api/v1/users/current
returns the current user
UserController_findCurrentUser_v1 → 200
PATCH
/api/v1/users/current
update current user's name, nickname or phone number
UserController_updateCurrent_v1 body → 200
GET
/api/v1/users/{userId}
UserController_get_v1 1 param → 200
POST
/api/v1/customers/{customerId}/users/delegates
Create an async job that will update user delegates
UsersController_updateUserDelegates_v1 1 param body → 201
POST
/api/v1/customers/{customerId}/users/delegates/batch
Create an async job that will update delegates for a batch of users.
UsersController_updateUserDelegatesBatch_v1 2 params body → 201

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are UserResponseDto (25 properties), User (24 properties), UpdateUserDto (13 properties), UpdateUserV2Dto (13 properties). Each schema is shown below with its type and property counts.

DelegatePermissionDto
object
1 property 1 required
UpdateUserDelegatesBatchDto
object
1 property 1 required
CreateUserV1Dto
object
8 properties 2 required
SearchUsersResponseDto
object
4 properties 3 required
ImportManyUserDto
object
1 property 1 required
SetSuperDelegateDto
object
2 properties 1 required
TenantDigest
object
3 properties 3 required
UpdateUserDelegatesDto
object
2 properties 2 required
LookupUsersBatchRequestDto
object
1 property 1 required
UpdateUserDto
object
13 properties
OnAuthResponseDto
object
10 properties 10 required
UserResponseDto
object
25 properties 13 required
CustomerDigest
object
5 properties 3 required
ImportOneUserDto
object
7 properties 1 required
UserLite
object
6 properties 5 required
UpdateUserStatusDto
object
1 property 1 required
DelegateUserDigest
object
4 properties 3 required
UserIntegrationProjection
object
4 properties 3 required
TranslateTimekeeperIdsRequestDto
object
1 property 1 required
AddEmailAliasesRequestDto
object
1 property 1 required
ImportUserV2Dto
object
6 properties 3 required
DelegatorUserDigest
object
4 properties 3 required
OnBrokerAuthRequestDto
object
4 properties 4 required
AddUserIdentitiesBulkDto
object
1 property 1 required
RoleDigest
object
3 properties 3 required
UserDelegateDto
object
2 properties 2 required
User
object
24 properties 13 required
UpdateCurrentUserDto
object
12 properties
UserDelegateInfoDto
object
2 properties 2 required
PermissionDigest
object
3 properties 3 required
IdentityDto
object
2 properties 2 required
EmailAliasesResponseDto
object
1 property 1 required
TranslateTimekeeperIdsResponseDto
object
1 property 1 required
Identity
object
3 properties 2 required
OnAuthRequestDto
object
10 properties 10 required
AddUserIdentityDto
object
2 properties 2 required
IdentityLookupParamDto
object
2 properties 2 required
UpdateUserV2Dto
object
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

laurel-users-api-openapi.yml Raw ↑

Other APIs Laurel publishes across the network.

Laurel Ably API
AE Profile APIs.io
Laurel Activities API
AE Profile APIs.io
Laurel Clients API
AE Profile APIs.io
Laurel Code Types API
AE Profile APIs.io
Laurel Codes API
AE Profile APIs.io
Laurel CodeTypes API
AE Profile APIs.io
Laurel Customers API
AE Profile APIs.io
Laurel DailySelectedInitiatives API
AE Profile APIs.io
Laurel Data Retention Audits API
AE Profile APIs.io
Laurel Delegators API
AE Profile APIs.io
Laurel Entries API
AE Profile APIs.io
Laurel Entry Date Restrictions API
AE Profile APIs.io
#User
← Back to L APIs
API Details
ID
laurel:laurel-users-api
Base URL
https://api.laurel.ai/time/
Docs
https://developer.laurel.ai/services/time
Provider
Laurel
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=laurel-users-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/laurel-users-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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