This reference explains how application fees, coupons, and Awards payment settings work through the API when they go beyond the Console forms. You can save a fee before you choose its award, send many fee or coupon changes in one request, and understand why you cannot test a batch against its rules without saving it.
Saving a Fee Without an Award
In the Console, you must choose the award before you can save a fee. Through the API, an import, or a bulk write, you can save an application fee without choosing an award. That fee exists, but it does not appear on any award’s fee list or become available to anyone until you set its award.
Sending Many Changes in One Request
You can use one batch request to create, change, or delete many application fees or coupons at the same time. Rhythm checks each operation against the same rules used for a single save, so one item failing its own validation does not automatically stop the rest of the batch. Awards payment settings do not support batch requests; batch operations apply only to fees and coupons.
Every Request Stays in Your Own Account
Rhythm checks every fee, coupon, and settings request against the Rhythm account tied to your session. If a request names a different account, Rhythm refuses it.
Checking a Batch Without Saving
Rhythm can check a batch of fee, coupon, or settings records against their validation rules without saving them, but that check is only for Rhythm’s own internal tools. It has no public API route, so a customer integration cannot call it directly. To confirm whether a batch will succeed before you commit it, send the batch and review the result for each operation.