Finding Client
API endpoint for finding existing clients based on various criteria via an API key.
Endpoint
Finds exisitng clients associated with the user linked to the API key.
Usage
This endpoint can be used to fetch fully client information, including their ID. If you have existing clients in your service and in Logis, and you need to link them together, this endpoint is perfect for you.
Note: This endpoint provides more control/options than the Auto-Match Clients process during a Job creation — this endpoint provides you with all matches and allows you to choose a specific match, instead of imposing one.
Authentification
This endpoint requires authentification via a custom API key header.
The API key used must have the "Allow Client Interaction" permission enabled in the Logis settings.
Request Parameters
This endpoint accepts query parameters in the URL. You must provide at least one of the following parameters: client_id
, phone_number
or email
.
Parameter | Type | Required | Description |
---|---|---|---|
client_id | string | Optional (UUID) | The UUID of a specific EndClient to find. If provided, other parameters are ignored for initial lookup. |
phone_number | string | Optional | Used for searching clients if client_id is not provided or not found. Format: +1 XXX-XXX-XXXX . |
email | string | Optional | Used for searching clients if client_id is not provided or not found. |
first_name | string | Optional | Used for searching clients alongside phone_number or email if client_id is not provided/found. |
last_name | string | Optional | Used for searching clients alongside phone_number or email if client_id is not provided/found. |
Example URLs
- Find by specific ID:
GET /api/apikeys/find_client?client_id=YOUR_CLIENT_UUID
- Find by phone number:
GET /api/apikeys/find_client?phone_number=+1 555-123-4567
- Find by email:
GET /api/apikeys/find_client?email=john.doe@example.com
- Find by email and last name:
GET /api/apikeys/find_client?email=john.doe@example.com&last_name=Doe
Success Response
The endpoint returns a 200 OK
status code. The response body depends on whether a specific client_id
was used for lookup or if other parameters were used for matching.
Response for client_id
lookup
Response for match
Error Responses
Status Code | Error Code / Reason | Description |
---|---|---|
400 Bad Request | Missing Parameters (phone_number or email) | Neither phone_number nor email was provided when client_id was also missing or not found. |
401 Unauthorized | Missing LOGIS-API-KEY header | The required API key header was not included. |
403 Forbidden | Invalid/Inactive LOGIS-API-KEY | The provided API key is not valid or is inactive. |
403 Forbidden | Permission Denied (allow_client) | The API key used does not have permission for client interaction. |
404 Not Found | Client ID Not Found (client_id lookup) | A specific client_id was provided, but no client exists with that ID for the associated user. |