Skip to content

feat: add number_of_employees field to Profile API - #388

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

feat: add number_of_employees field to Profile API#388
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 a new optional number_of_employees string field to the Profile (10DLC/A2P account profile) create and update APIs. This mirrors a backend change in campaign-service where number_of_employees was added to the Profile create & update request as an optional string.

The field is implemented exactly like the recently-added doing_business_as (DBA) field — same files, positions (right after DBA), and style.

Details

  • No client-side enum validation; the server validates the value.
  • The 7 allowed values are documented (not enforced) in JSDoc and .d.ts comments: 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.

Changes

  • lib/resources/profile.js — added number_of_employees create param + JSDoc (create & update).
  • types/resources/profile.d.ts — added optional number_of_employees to create signature and update params type.
  • test/profile.js — assertion on get-profile fixture + positional arg in create test.
  • lib/rest/request-test.js — added number_of_employees to the GET profile fixture.
  • package.json — version bump 4.77.1 -> 4.77.2.
  • CHANGELOG.md — new top entry.

🤖 Generated with Claude Code

Add an optional number_of_employees string field to the Profile (10DLC/A2P)
create and update APIs, mirroring the existing doing_business_as field.
The field is not validated client-side (the server validates the allowed
values); the 7 allowed values are documented in JSDoc/type-def comments.

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