The discussion is about understanding and resolving issues with the API's "taxable" field always returning as "false" for products, even when set to "true."

API Q&A
, ,
1

I am currently using the Keap API to retrieve product details and have encountered an issue with the “taxable” field. Despite setting the “taxable” field to true for my products, the API consistently returns it as false.

Has anyone else encountered this behavior? Could there be a configuration issue, or is this possibly a limitation of the API? If it’s a bug, is there an existing workaround or solution? I would greatly appreciate any insights or guidance on how to resolve this.

3

If you’re using the v2 API, when you create a product with POST /products and send "taxable": true, or update an existing product with PATCH /products/{id} and set "taxable": true, the API correctly returns "taxable": true when you fetch the product with GET /products/{id} or when listing all products with GET /products.

4

Using Postman and making the request directly to the REST V1 API, the taxable property is not returned.

Using Postman and making the request directly to the REST V2 API I can get the correct taxable status as true or false.

Using the Legacy XMLRPC API using the dsLoad() method I can get the taxable status correctly as 1 or 0.

Using the deprecated Infusionsoft PHP SDK requesting w/ data()->load(‘Product’, $id, [‘Taxable‘]) I can get the taxable status correctly as 1 or 0.

I wasn’t able to use the new Keap PHP SDK because the ProductAPI class wasn’t loaded by composer.
Using the new Keap PHP SDK I was able to get the correct taxable value returned as 1 or 0.