Skip to main content
By default, fal stores the inputs and outputs of your API requests so you can retrieve them later through the platform. This page explains how long that data is kept and the controls you have over it. If your application handles sensitive data or you simply don’t need request payloads persisted, you can delete them after the fact or prevent storage entirely by setting a single request header.

​
Deleting IO Payloads

You can delete a request’s payloads and the CDN files found in the output of the request using the Platform API. This is useful for removing generated images, files, or other media from the platform.
Note:The CDN files found in the input of the request are not deleted, as they may be used by other requests.

Delete Request Payloads API

See the Platform API reference for the delete endpoint, authentication requirements, and response format.

​
Preventing IO Storage

You can prevent a request’s payloads from being stored at all by including the X-Fal-Store-IO: 0 header in your request. This is useful when you want to avoid storing sensitive data or when you don’t need the payloads to be accessible later.
Caution:If files were uploaded to the CDN during the processing, these will still be accessible. This header just avoids storage of the payloads in the platform itself.

​
Example

curl --location --request POST 'https://queue.fal.run/fal-ai/fast-sdxl' \
--header "Authorization: Key $FAL_KEY" \
--header 'X-Fal-Store-IO: 0' \
--header 'Content-Type: application/json' \
--data '{
  "prompt": "A beautiful landscape"
}'