Skip to Content
Messaging APIUser Settings

User Settings

Manage individual user profile and communication preferences.

This endpoint manages settings for individual users connected via a connect link — not API key owners themselves.

Endpoint

GET and POST https://api.warmai.uk/functions/v1/api-user-settings

Headers:

HeaderRequiredDescription
x-access-keyYesYour API access key
x-user-idYesThe user’s ID

Get User Settings

Retrieve the current settings for a connected user.

Method: GET

Example Request:

curl -X GET "https://api.warmai.uk/functions/v1/api-user-settings" \ -H "x-access-key: your_access_key" \ -H "x-user-id: usr_abc123"

Response:

{ "user_id": "usr_abc123", "first_name": "Jane", "last_name": "Doe", "calendar_link": "https://calendly.com/janedoe/30min", "cta_preference": "meeting", "custom_cta": null, "connection_request_with_note": true, "communication_style": "professional", "message_length": "moderate", "signature_style": "Best, Jane" }

Update User Settings

Update one or more settings for a connected user. Only include the fields you want to change.

Method: POST

Example Request:

curl -X POST "https://api.warmai.uk/functions/v1/api-user-settings" \ -H "x-access-key: your_access_key" \ -H "x-user-id: usr_abc123" \ -H "Content-Type: application/json" \ -d '{ "cta_preference": "call", "message_length": "brief" }'

Response:

{ "success": true, "updated_fields": ["cta_preference", "message_length"] }

Available Fields

FieldTypeDescription
first_namestringUser’s first name
last_namestringUser’s last name
calendar_linkstringURL to the user’s scheduling page
cta_preferencestringCall-to-action type: meeting, call, email, website, soft, or custom
custom_ctastringCustom CTA text (used when cta_preference is custom)
connection_request_with_notebooleanWhether to include a note with LinkedIn connection requests
communication_stylestringTone of outreach messages: professional, casual, or consultative
message_lengthstringMessage length preference: brief, moderate, detailed, short, medium, or long
signature_stylestringSign-off text appended to messages

Error Responses

StatusCodeDescription
400Bad RequestInvalid fields provided in the request body
400Bad RequestEmpty request body on POST
401UnauthorisedMissing x-access-key header
401UnauthorisedInvalid or expired access key
403ForbiddenUser is not linked to this access key
403ForbiddenUser is not in an active state
Last updated on