Update profile settings

Deprecated

Deprecated. This endpoint is replaced by /v3/sender-profiles and will be removed in a future release. It still behaves exactly as before, so nothing needs to change today — but new integrations should use /v3/sender-profiles, which models a profile's markets, compliance, brand, campaigns and billing explicitly.

Updates a profile's configuration and settings. Requires admin role in the organization. Only provided fields will be updated (partial update).

Brand Management

Include the optional brand field to create or update the brand associated with this profile. The brand holds KYC and TCR compliance data (legal business info, contact details, messaging vertical). Once a brand has been submitted to TCR it cannot be modified. Setting inherit_tcr_brand: true and providing brand in the same request is not allowed.

Payment Details

When billing_model is "profile" or "profile_and_organization" you may include a payment_details object containing the card number, expiry (MM/YY), CVC, and billing ZIP code. Payment details are never stored on our servers and are forwarded directly to the payment processor. Providing payment_details when billing_model is "organization" is not allowed.

Deprecated fields

sending_phone_number_profile_id and sending_whatsapp_number_profile_id are accepted and ignored. Sender borrowing is gone: a profile cannot send from another profile's number, because two profiles behind one sender makes an inbound reply and a delivery receipt ambiguous about whose they are.

Sending either changes nothing and still returns 200 — they are kept on the contract so an existing integration keeps working. Reads carry both keys too and always answer null, which is how you can confirm the value did not take.

Give the profile a sender of its own instead — POST /v3/channels/sms or POST /v3/channels/whatsapp, sent with the x-profile-id header naming it.

PATCH
/v3/profiles/{profileId}

Path Parameters

profileId*string

Profile ID from route parameter

Formatuuid

Header Parameters

Idempotency-Key?string

Unique key to ensure idempotent request processing. Must be 1-255 alphanumeric characters, hyphens, or underscores. Responses are cached for 24 hours per key per customer.

Match^[a-zA-Z0-9_-]+$
Lengthlength <= 255
x-profile-id?string

Profile UUID to scope the request to a child profile. Only organization API keys can use this header. The profile must belong to the calling organization.

Formatuuid

Request Body

application/json
  1. body

Request to update a profile

sandbox?boolean

Sandbox flag - when true, the operation is simulated without side effects Useful for testing integrations without actual execution

name?|

Profile name (optional)

Length0 <= length <= 100
icon?|

Profile icon URL (optional)

description?|

Profile description (optional)

short_name?|

Profile short name/abbreviation (optional). Must be 3–11 characters, contain only letters, numbers, and spaces, and include at least one letter. Example: "SALES", "Mkt 2", "Support1".

inherit_tcr_brand?|

Whether this profile inherits TCR brand from organization (optional)

inherit_tcr_campaign?|

Whether this profile inherits TCR campaign from organization (optional)

billing_model?|

Billing model: profile, organization, or profile_and_organization (optional).

  • "organization": the organization's billing details are used; no profile-level billing info needed.
  • "profile": the profile is billed independently; billing_contact is required.
  • "profile_and_organization": the profile is billed first with the organization as fallback; billing_contact is required.
billing_contact?|null

Billing contact for this profile. Required when billing_model is "profile" or "profile_and_organization" and no billing contact has been configured yet. Identifies who receives invoices and who is responsible for payment.

sending_phone_number_profile_id?|Deprecated

Deprecated. Accepted and ignored. Sender borrowing is gone: a profile cannot send from another profile's SMS number. Supplying this changes nothing and the request still succeeds.

Bound rather than dropped so the property survives on the wire and in a generated client — an SDK that assigns it keeps compiling, which is the compatibility this exists for. It is deliberately not refused: a 400 here would break an integration that is otherwise working, and the capability it asks for is gone either way.

The trade-off, stated plainly. A caller asking for borrowing is told it succeeded when nothing happened. What makes that survivable is the read: sending_phone_number_profile_id comes back null on every profile, so a caller that checks its own write can see it did not take. Every request that carries one is logged, so we can tell when nobody is sending it any more and the field can go for real.

Give the profile a sender of its own instead: POST /v3/channels/sms with the x-profile-id header naming it.

Formatuuid
sending_whatsapp_number_profile_id?|Deprecated
Formatuuid
allow_contact_sharing?|Deprecated

Deprecated. Accepted and ignored. Contact and template sharing between sender profiles is gone — a profile sees only what it owns, and the organization still sees all of its profiles' contacts and templates through read-time widening. The four columns behind these flags were dropped by M260720120000.

Retired the same way as SendingPhoneNumberProfileId, and for the same reason: the properties stay bound so an SDK that assigns them keeps compiling, and a 400 would break a working integration over a capability that is gone regardless. Every profile reports all four as false, so a caller that checks its own write can see it did not take.

allow_template_sharing?boolean|nullDeprecated
inherit_contacts?boolean|nullDeprecated
inherit_templates?boolean|nullDeprecated
sending_phone_number?|

Direct phone number for SMS sending (optional)

whatsapp_phone_number?|

Direct phone number for WhatsApp sending (optional)

allow_number_change_during_onboarding?|

Whether number changes are allowed during onboarding (optional)

brand?|null

Brand and KYC information for this profile (optional). When provided, creates or updates the brand associated with this profile. Cannot be set when inherit_tcr_brand is true. Once a brand has been submitted to TCR it cannot be modified.

payment_details?|null

Payment card details for this profile (optional). Accepted when billing_model is "profile" or "profile_and_organization". Not persisted on our servers — forwarded to the payment processor.

Response Body

Profile updated successfully

application/json
  1. response

Standard API response envelope for all v3 endpoints

success?boolean

Indicates whether the request was successful

data?|null

The response data (null if error)

error?|null

Error details (null if successful)

meta?

Metadata about the request and response

Example Request
curl -X PATCH 'https://api.sent.dm/v3/profiles/770e8400-e29b-41d4-a716-446655440002' \  -H 'Idempotency-Key: req_abc123_retry1' \  -H 'Content-Type: application/json' \  -d '{  "name": "Sales Team - Updated",  "description": "Updated sales department sender profile",  "short_name": "SALES",  "billing_model": "organization",  "brand": {    "contact": {      "name": "John Smith",      "businessName": "Acme Corp",      "role": "CEO",      "phone": "+12025551234",      "email": "john@acmecorp.com",      "phoneCountryCode": "1"    },    "business": {      "legalName": "Acme Corporation LLC",      "taxId": "12-3456789",      "taxIdType": "us_ein",      "entityType": "PRIVATE_PROFIT",      "street": "123 Main Street",      "city": "New York",      "state": "NY",      "postalCode": "10001",      "country": "US",      "url": "https://acmecorp.com",      "countryOfRegistration": "US"    },    "compliance": {      "vertical": "PROFESSIONAL",      "brandRelationship": "SMALL_ACCOUNT",      "isTcrApplication": true,      "phoneNumberPrefix": "+1",      "destinationCountries": [        {          "id": "US",          "isMain": false        }      ]    }  },  "sandbox": false}'
Example Response
{  "success": true,  "data": {    "id": "770e8400-e29b-41d4-a716-446655440002",    "organization_id": "550e8400-e29b-41d4-a716-446655440000",    "name": "Sales Team - Updated",    "email": "team@acme.com",    "icon": "https://example.com/sales-icon.png",    "description": "Updated sales department sender profile",    "short_name": "SALES",    "status": "approved",    "created_at": "2026-08-12T15:32:26.7082014+00:00",    "updated_at": "2026-11-12T15:32:26.708202+00:00",    "allow_contact_sharing": false,    "allow_template_sharing": false,    "inherit_contacts": false,    "inherit_templates": false,    "inherit_tcr_brand": false,    "inherit_tcr_campaign": false,    "billing_model": "organization",    "sending_phone_number_profile_id": null,    "sending_whatsapp_number_profile_id": null,    "sending_phone_number": null,    "whatsapp_phone_number": null,    "allow_number_change_during_onboarding": null,    "waba_id": null,    "billing_contact": null,    "brand": {      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",      "tcr_brand_id": null,      "status": null,      "identity_status": null,      "universal_ein": null,      "csp_id": null,      "submitted_to_tcr": false,      "submitted_at": null,      "is_inherited": false,      "created_at": "2026-11-12T15:32:26.7082024+00:00",      "updated_at": null,      "contact": {        "name": "John Smith",        "business_name": "Acme Corp",        "role": null,        "phone": null,        "email": "john@acmecorp.com",        "phone_country_code": null      },      "business": {        "legal_name": "Acme Corporation LLC",        "tax_id": null,        "tax_id_type": null,        "entity_type": null,        "street": null,        "city": null,        "state": null,        "postal_code": null,        "country": "US",        "url": null,        "country_of_registration": null      },      "compliance": {        "vertical": "PROFESSIONAL",        "brand_relationship": "SMALL_ACCOUNT",        "is_tcr_application": true,        "phone_number_prefix": null,        "destination_countries": [          {            "id": "US",            "isMain": false          }        ],        "notes": null,        "primary_use_case": null      }    }  },  "error": null,  "meta": {    "request_id": "req_7X9zKp2jDw",    "timestamp": "2026-11-12T15:32:26.7082035+00:00",    "version": "v3"  }}

Create a new profile POST

**Deprecated.** This endpoint is replaced by `/v3/sender-profiles` and will be removed in a future release. It still behaves exactly as before, so nothing needs to change today — but new integrations should use `/v3/sender-profiles`, which models a profile's markets, compliance, brand, campaigns and billing explicitly. Creates a new sender profile within an organization. Profiles represent different brands, departments, or use cases, each with their own messaging configuration and settings. Requires admin role in the organization. ## WhatsApp Business Account Every profile owns its own WhatsApp Business Account — accounts are never shared between profiles or inherited from the organization. Provide a `whatsapp_business_account` object with `waba_id`, `phone_number_id`, and `access_token`. Obtain these from Meta Business Manager by creating a System User with `whatsapp_business_messaging` and `whatsapp_business_management` permissions. Omit the field and the profile is created without WhatsApp, staying incomplete until it has an account of its own. ## Brand Include the optional `brand` field to create the brand for this profile at the same time. Cannot be used when `inherit_tcr_brand` is `true`. ## Payment Details When `billing_model` is `"profile"` or `"profile_and_organization"` you may include a `payment_details` object containing the card number, expiry (MM/YY), CVC, and billing ZIP code. Payment details are **never stored** on our servers and are forwarded directly to the payment processor. Providing `payment_details` when `billing_model` is `"organization"` is not allowed.

Delete a profile DELETE

**Deprecated.** This endpoint is replaced by `/v3/sender-profiles` and will be removed in a future release. It still behaves exactly as before, so nothing needs to change today — but new integrations should use `/v3/sender-profiles`, which models a profile's markets, compliance, brand, campaigns and billing explicitly. Soft deletes a sender profile. The profile will be marked as deleted but data is retained. Anything it still held is released first: phone numbers return to our inventory and can go to whoever asks next, its own WhatsApp account is deregistered, and its routing rules stop being used. Requires admin role in the organization. A number it holds that your WhatsApp Business Account still carries refuses the delete with a `409 CONFLICT_012`, and nothing is deleted: the number would return to our shared inventory while Meta still routes WhatsApp to it, and only you can take it off the account — deregister **and** delete it in WhatsApp Manager, then try again. A `409 CONFLICT_013` means the account could not be read, so we cannot tell.