Skip to content

feat: add number_of_employees field to Profile API - #314

Draft
Jai Shankar (jaishankar-plivo) wants to merge 1 commit into
masterfrom
feat/add-number-of-employees-to-profile
Draft

Jai Shankar (jaishankar-plivo) wants to merge 1 commit into
masterfrom
feat/add-number-of-employees-to-profile

Conversation

@jaishankar-plivo

Copy link
Copy Markdown

Summary

Adds the optional number_of_employees field to the Profile (10DLC/A2P account profile) create and update APIs, mirroring the backend campaign-service change. Modeled exactly on the recently added doing_business_as (DBA) field.

  • New NumberOfEmployees property ([JsonProperty("number_of_employees")]) on both the Profile and ListProfiles response models, added right after DoingBusinessAs.
  • New optional number_of_employees string parameter on Create, CreateAsync, Update, and UpdateAsync, threaded through each CreateData payload right after doing_business_as.
  • Optional string with NO client-side enum validation (server validates). Allowed values are documented in a comment, not enforced: BETWEEN_1_AND_10, BETWEEN_11_AND_50, BETWEEN_51_AND_200, BETWEEN_201_AND_500, BETWEEN_501_AND_2000, BETWEEN_2001_AND_10000, MORE_THAN_10001.

Tests / fixtures

  • Added number_of_employees to profileGetResponse.json mock and asserted deserialization in TestProfile.cs, mirroring the DBA assertion.

Version

  • Bumped patch 5.52.1 -> 5.52.2 in Plivo.csproj, Plivo.nuspec, and version.json.
  • Added CHANGELOG entry at top (2026-06-10).

🤖 Generated with Claude Code

Add the optional number_of_employees field to the Profile (10DLC/A2P)
create and update APIs, mirroring the recently added doing_business_as
(DBA) field. The field is an optional string with no client-side
enum validation; allowed values are documented in a comment and
validated server-side.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant