Updated the spec after revision:

• range spec now only contains start_number and end_number; no caller_id_name or shared options supported for range, as it’s unlikely it would make sense to set those options to the same value in bulk

Since we now want an idempotent transactional API, we could use

Or

Also need to add trunks field to input now( )

After discussion we decided that the API should behave idempotently with respect to duplicates. i.e. elements of the range that already exist identically(same shared value and non-null caller_id_name specified by the range) will be silently skipped, allowing only missing entries to be created.
This should imply a response format that can provide links to all phone number objects matching all entries in the range, with information to know which were newly created.

However, if fields like shared , caller_id_name , trunks differs from existing entries(defined but different), we must abort with an error as we don’t want the user to mistakenly overwrite large number of entries