Skip to content

feat: add number_of_employees field to Profile API#266

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#266
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 & update API. 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 added in exactly the same places and style as the recently added doing_business_as (DBA) field.

Details

  • No client-side enum validation — the server validates the value (matching doing_business_as / business_contact_email).
  • 7 allowed values are documented (not enforced) in a comment on the resource: 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.
  • Version bumped 4.63.2 -> 4.63.3.
  • CHANGELOG entry added.

Files changed

  • lib/plivo/resources/profile.rb — documented field in update options comment
  • spec/resource_profile_spec.rb — added field to create & update test payloads + compare_requests data
  • spec/mocks/profileGetResponse.json — added field to mock response
  • lib/plivo/version.rb — 4.63.3
  • CHANGELOG.md — new entry

🤖 Generated with Claude Code

Adds an optional number_of_employees string field to the Profile
(10DLC/A2P) create & update API, mirroring the existing
doing_business_as field. No client-side enum validation is performed;
the server validates the value. Allowed values are documented in a
comment on the resource.

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