Noticed that API responses started sending encrypted_content today without “include” parameter. Was this intentional change?
Hi and welcome to the community!
In general, this is intentional for stateless requests and when an organization is covered by a Zero Data Retention agreement, but I am also seeing it happen when using store: true.
For stateless requests when store: false is used, the API returns encrypted_content automatically. The old include parameter still works, but it is no longer required in this case. Link to the docs.
For stateful requests:
The docs imply that encrypted content is generally returned by default, but they do not clearly document that a non-ZDR request with store: true will return encrypted_content when include is omitted. They also do not document any way to suppress it.
Is this the change you are seeing? That part is not entirely clear from your question.
Thank you for the response. After taking a closer look, I realized that there was no change in the behavior. Something else in our system caused issues because encrypted_content was included, and that brought my attention.