--- title: "Changes to Check hosted messaging eligibility" method: POST path: "/messaging_hosted_number_orders/eligibility_numbers_check" --- # Changes to Check hosted messaging eligibility `POST /messaging_hosted_number_orders/eligibility_numbers_check` > Every recorded change to this operation, newest first. > 501 revisions in range; 1 not diffed. ## Timeline Changed in 59 of 501 revisions. - **2026-02-20** `5d53041d4ddd`: 2 breaking, 1 info - **2026-02-04** `a3a64a14ed68`: 2 info - **2026-02-03** `6a9394d3d3bb`: 2 info - **2025-12-15** `15a388e2af97`: 2 info - **2025-08-15** `c57f4613ea87`: 2 breaking - **2025-08-11** `0606a8c47df7`: 2 breaking - **2025-08-11** `5e703a375518`: 2 breaking - **2025-08-11** `45a854866005`: 2 breaking - **2025-08-08** `2e72aa01a5a1`: 2 breaking - **2025-08-08** `7952080be8f8`: 2 breaking - **2025-08-08** `144abaf03f62`: 2 breaking - **2025-08-08** `10aa5bc09ecc`: 2 breaking - **2025-08-07** `d7484a0a7768`: 2 breaking - **2025-08-07** `8e5f0d46ddd6`: 2 breaking - **2025-08-07** `676a368c011d`: 2 breaking - **2025-08-05** `f618a1006b1a`: 2 breaking - **2025-08-05** `51b123d64141`: 2 breaking - **2025-08-04** `5ea2f9679014`: 2 breaking - **2025-08-04** `b027d7073c5b`: 2 breaking - **2025-08-04** `44161174fc15`: 2 breaking - **2025-08-04** `d0bb8be24d5a`: 2 breaking - **2025-08-04** `f60b6a1dffb2`: 2 breaking - **2025-08-04** `441e11d27bba`: 4 breaking - **2025-08-04** `ddc1a62684d2`: 2 breaking - **2025-08-04** `ae0258dceac3`: 4 breaking - **2025-08-04** `9092c0625f49`: 2 breaking - **2025-08-04** `b9a59c2da231`: 6 breaking - **2025-08-01** `9922dcb29641`: 4 breaking - **2025-08-01** `f87271113641`: 4 breaking - **2025-08-01** `61d945742de3`: 4 breaking - **2025-08-01** `99020e181f1c`: 4 breaking - **2025-08-01** `3614a68dc607`: 4 breaking - **2025-07-31** `47ead24182c8`: 4 breaking - **2025-07-30** `13eaae046af7`: 4 breaking - **2025-07-25** `b7607afaef95`: 4 breaking - **2025-07-25** `dd0dfcd94701`: 4 breaking - **2025-07-24** `6ad7361a2335`: 4 breaking - **2025-07-24** `253d9a1bba97`: 4 breaking - **2025-07-23** `1083e5c24d8f`: 4 breaking - **2025-07-16** `b5433e9b6e42`: 4 breaking - **2025-07-15** `34fed4d6b28d`: 4 breaking - **2025-07-15** `67c9fa18d5ef`: 4 breaking - **2025-07-15** `99b0d0af53c6`: 4 breaking - **2025-07-10** `98029c9ccdd5`: 4 breaking - **2025-07-08** `1059b083160b`: 4 breaking - **2025-07-08** `d49a13e1ec17`: 4 breaking - **2025-07-07** `657402475201`: 4 breaking - **2025-07-07** `d671264e7ab5`: 4 breaking - **2025-07-03** `18c5992ca257`: 4 breaking - **2025-07-02** `b443330a00cd`: 4 breaking - **2025-06-23** `0119581e33a2`: 4 breaking - **2025-06-18** `7226f437ab8f`: 4 breaking - **2025-06-16** `8b1f140752a8`: 4 breaking - **2025-06-13** `aa349b5e4339`: 4 breaking - **2025-06-11** `ddadf923b6ba`: 4 breaking - **2025-06-11** `aa66f7810563`: 4 breaking - **2025-06-10** `62260d173b5c`: 4 breaking - **2025-06-06** `9b438170c3e3`: 4 breaking - **2025-06-05** `fec78497a29c`: 1 info ## Changes - **2026-02-20** `5d53041d4ddd`: 2 breaking, 1 info - the `code` response's property format changed from `integer` to no format for status `400` - the `code` response's property format changed from `integer` to no format for status `401` - the `phone_numbers/items/` request property format was generalized from `+E.164` to no format - **2026-02-04** `a3a64a14ed68`: 2 info - api tag `Hosted Numbers` added - api tag `Messaging Hosted Number` removed - **2026-02-03** `6a9394d3d3bb`: 2 info - api tag `Messaging Hosted Number` added - api tag `Hosted Numbers` removed - **2025-12-15** `15a388e2af97`: 2 info - api tag `Hosted Numbers` added - api tag `Messaging Hosted Number` removed - **2025-08-15** `c57f4613ea87`: 2 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - **2025-08-11** `0606a8c47df7`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-11** `5e703a375518`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-11** `45a854866005`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-08** `2e72aa01a5a1`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-08** `7952080be8f8`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-08** `144abaf03f62`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-08** `10aa5bc09ecc`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-07** `d7484a0a7768`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-07** `8e5f0d46ddd6`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-07** `676a368c011d`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-05** `f618a1006b1a`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-05** `51b123d64141`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-04** `5ea2f9679014`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-04** `b027d7073c5b`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-04** `44161174fc15`: 2 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - **2025-08-04** `d0bb8be24d5a`: 2 breaking - the `source/pointer` response's property format changed from `json-pointer` to no format for status `400` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `401` - **2025-08-04** `f60b6a1dffb2`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-04** `441e11d27bba`: 4 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `400` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `401` - **2025-08-04** `ddc1a62684d2`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-04** `ae0258dceac3`: 4 breaking - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to no format for status `401` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `400` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `401` - **2025-08-04** `9092c0625f49`: 2 breaking - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from no format to `int32` for status `401` - **2025-08-04** `b9a59c2da231`: 6 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property format changed from `int` to no format for status `400` - the `code` response's property format changed from `int` to no format for status `401` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `400` - the `source/pointer` response's property format changed from `json-pointer` to no format for status `401` - **2025-08-01** `9922dcb29641`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-08-01** `f87271113641`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-08-01** `61d945742de3`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-08-01** `99020e181f1c`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-08-01** `3614a68dc607`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-31** `47ead24182c8`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-30** `13eaae046af7`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-25** `b7607afaef95`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-25** `dd0dfcd94701`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-24** `6ad7361a2335`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-24** `253d9a1bba97`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-23** `1083e5c24d8f`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-16** `b5433e9b6e42`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-15** `34fed4d6b28d`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-15** `67c9fa18d5ef`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-15** `99b0d0af53c6`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-10** `98029c9ccdd5`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-08** `1059b083160b`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-08** `d49a13e1ec17`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-07** `657402475201`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-07** `d671264e7ab5`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - **2025-07-03** `18c5992ca257`: 4 breaking - the response's body type changed from no type to `object` for status `400` - the response's body type changed from no type to `object` for status `401` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `400` - the `code` response's property type changed from `string` to `integer`, and format from `int` to `int32` for status `401` - **2025-07-02** `b443330a00cd`: 4 breaking - the response's body type changed from `object` to no type for status `400` - the response's body type changed from `object` to no type for status `401` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `400` - the `code` response's property type changed from `integer` to `string`, and format from `int32` to `int` for status `401` - …earlier changes are on the page: https://skmtc.dev/team-telnyx/apis/telnyx-api-2/changes/messaging_hosted_number_orders/eligibility_numbers_check/post --- [Operation](https://skmtc.dev/team-telnyx/apis/telnyx-api-2/docs/messaging_hosted_number_orders/eligibility_numbers_check/post.md) - [API](https://skmtc.dev/team-telnyx/apis/telnyx-api-2.md) - [Page](https://skmtc.dev/team-telnyx/apis/telnyx-api-2/changes/messaging_hosted_number_orders/eligibility_numbers_check/post)