List asset folders
Every folder of the workspace (at most 1,000), by name, with the folder each is in and how many images and fonts are directly in it: enough to show any folder’s contents and path.
Every folder of the workspace (at most 1,000), by name, with the folder each is in and how many images and fonts are directly in it: enough to show any folder’s contents and path.
apiKey readAuthorizationBearer <token>A workspace API key (pf_…), created under Developers → API keys.
Scope: read
OK
application/json- response
items*array<>curl -X GET 'https://api.postforge.dev/v1/asset-folders'{ "items": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "parentId": "70850378-7d3c-4f45-91b7-942d4dfbbd43", "images": 0, "fonts": 0, "folders": 0, "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z" } ]}Upload an asset’s file PUT
The file’s bytes (`application/octet-stream` with its Content-Length, the size `create` was given). Checks what the file really is and reads an image’s size; the asset is then ready at its URL. Sending them again before that replaces them. 422 `asset_type_mismatch` when the bytes aren’t the type given (or aren’t a file every email client shows, like WebP or SVG); 422 `asset_size_mismatch` when the size differs; 409 `asset_ready` once it’s ready (a new file is a new asset).
Create an asset folder POST
409 `asset_folder_exists` when the folder it’s in has one by that name; 422 `asset_folder_limit` past 1,000 folders or 10 levels.