Max payload size recommendations

Last updated: June 17, 2026

Overview

Merge does not currently enforce a max payload size in our API responses. If you are concerned that your API calls may be returning excessively large payloads, there are several steps you can take to slim down those responses.

How can I reduce payload sizes?

  1. Use encoding — Merge supports gzip, deflate, and br compression.

  2. Decrease your page size — the default page size is 30, with a max of 100.

  3. Limit use of the expand parameterexpand will increase payload size on most Merge objects, especially when expanding on multiple sub-objects.

  4. Avoid include_remote_data=true in queriesremote_data returns the original raw response from the third-party API and can increase payload sizes significantly.

Note: include_remote_data=true is the single largest contributor to oversized payloads, because it returns the unfiltered third-party response in addition to Merge's Common Model fields.

Who should I contact for help?

If you have concerns about payload size, please reach out to us at [email protected] to discuss your use case.