nextavailableip and PTR

[#1]

Hello, I am using the following API call to grab and reserve the next available IP for a network... Works great; however, I notice it does not create the PTR even though I use "record:host". Any idea why? 

{
	curl -k -u user:pw\
-H "Content-Type: application/json" \
-X POST "https://infoblox.company.com/wapi/v2.7.1/record:host" \
-d '{
                  "name": "'$SERVER'",
                  "ipv4addrs": [
                    {
                                  "ipv4addr": "func:nextavailableip:1.1.1.1/24"
                                }
                  ]
                }'

[#2]

A host record that has DNS enabled automatically functions as both an A record and as a PTR record, assuming the parent zone exists for each record.

It won't show up as a PTR in the database.

Hope that helps?

[#3]

Ok.. so I would have to create a separate API call to create the PTR? Or maybe I should be going about this another way entirely vs nextavailableip?