question

we have a request example here: https://docs.clover.com/docs/create-an-ach-token#request-example

could someone please send a screenshot with all the details, this is still not working

,

That request example also did not work, could someone please send a screenshot on how the ach token is generated, clover is very bad at documentation, please someone help

The error message "400 - Invalid JSON Format" typically indicates that the JSON data being sent in your API request is not properly formatted. This can occur when creating an ACH token or performing any API operation that requires JSON data.

Incredibox Sprunki

The error message "Invalid JSON format" indicates that there's an issue with the JSON payload you're sending. Ensure that all required fields have valid values, especially for fields marked as strings. For example, replace "string" with actual values or valid placeholders. Additionally, check for proper JSON syntax, including correct nesting and punctuation. Validate your JSON using a JSON validator to catch any formatting issues. Visit forums to explore more, and discover additional insights

Some fields might expect specific formats. For instance, "check_type" might require valid values (e.g., personal_check is fine, but check for allowed values in the documentation). Similarly, "customer_id_type" and "customer_id_state" may need specific formats.

The error message "Invalid JSON format" typically indicates an issue with the structure or content of your JSON payload. Based on the payload you provided, here are a few potential issues to check:

1. Quotation marks: Ensure all strings are enclosed in double quotation marks (not single quotes).
2. Data types: Some fields (e.g., bank_account_number, bank_routing_number, customer_id, etc.) expect specific formats (e.g., numbers or valid IDs) and could cause issues if filled with dummy data or incorrect values.
3. Missing required fields: Verify that all required fields are included and correctly formatted according to the API documentation.
4. Check "agreement" object: Ensure the "agreement" object fields are valid and required for the API you're interacting with.

Double-check the payload against the API documentation for correct field types and required values.