Bug fixes

Error messages

Based on testing and user feedback, we saw the need to to provide clearer, action-oriented error responses. We have updated the following error responses:

Method not allowed

When you send an Indirect Tax API request, if you use an incorrect HTTPS method (e.g., GET instead of POST), you will now see the "Method not Allowed" error message instead of a 404 error code with an ambiguous message.

Health check endpoint

When you enter an unsupported country code, this endpoint now returns a more concise error message instead of an error code and message associated with 400.

Tax ID checks

When you call this endpoint without proper configuration, it now returns "403 Forbidden" instead of a 400 error code.

Branch configuration

When you omit mandatory information during branch configuration, you will now see a more meaningful error message.

OAuth endpoint

When you execute the OAuth endpoint with invalid grant_type parameters, you will now see a more meaningful error message instead of "Invalid Credentials".

Other fixed issues

You can now:

• Retrieve an archived invoice by using custom properties without generating an error.

• Retrieve notifications for Argentinian Export documents without generating a 401 error.