[ENDPOINT]: Consistently use non_taxable or is_taxable, but not both

[foxfriends]

Is there an existing issue for this?

• [X] I have searched the existing tickets

Current Endpoint Design

When I get a listing, it comes with a field non_taxable.

When I need to update a listing, it requires the field is_taxable.

Does that mean to update a listing, I have to flip a boolean? This is very strange.

Proposed Endpoint Design Change

Use is_taxable in both situations.

Why are you proposing this change?

This is causing confusion and unnecessary bug-proneness to the API.