Attachment limit for Inbound Integration with base64 encodingIssue REST API returns an error similar to the following: Response: {"error":{"message":"Exception while reading request","detail":"Rejected large REST payload with content-length = 15105102 bytes. Max allowed: 10485760 bytes."},"status":"failure" Localhost logs will also indicate messages similar to the following in the stack trace. Caused by: com.glide.rest.domain.UserException: Rejected large REST payload with content-length = 13012943 bytes. Max allowed: 10485760 bytes.CauseThis seems to depend on the glide.rest.max_content_length property which is defaulted at 10MB, min is 1MB, max is 25MB on the target instance. The size includes the size of the attachment after the value is base64 encoded.ResolutionUsers must ensure that the size of the attachment including the encoding is within the value specified in this property. If this property is not present on the instance, it can be created as - In filter navigator, type sys_properties.list to open the properties tableClick on NewIn the Name field - Enter glide.rest.max_content_lengthIn the type select IntegerIn Value enter 25, if you want to set the max value. This value is in MB. There are two other properties mentioned on the product documentation page, please refer to the following page for additional reference: Controlling Max Request SizeRelated LinksAs mentioned in the following reference article, when the text of size 'n' is base encoded its size will increase by ceil(n / 3) * 4, Base64: What is the worst possible increase in space usage? [Stackoverflow]. By a rough approximation, the size of data would be increased to 4/3 of the original.