Upload an ad image

Mirrors Meta's POST /{accountId}/adimages.

Body carries Meta's own ad-image-upload fields — a bytes base64-encoded field — and is forwarded verbatim. Returns the image hash used by object_story_spec.link_data.image_hash on creative create.

  • Write — changes a live ad account immediately; needs a write-scoped token.

Uploading a file. As well as the JSON body above, this route accepts multipart/form-data with a file part (other parts ride along as platform fields), or file_base64 inside the JSON body — raw base64 or a data: URI, plus optional file_name/file_type. file_base64 is the only way an MCP caller can send bytes. JPEG, PNG, GIF or WebP, up to 10MB. The bytes are base64-encoded in place and sent to Meta as bytes — nothing is staged in object storage, because adimages has no URL parameter. A rejected type or size is 400 FILE_UPLOAD_INVALID.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Meta ad account id, act_ form.

Query Params
uuid
required

The Analify organization whose connected account to use.

Body Params
string

Raw base64 or a data: URI carrying the file bytes. Alternative to the multipart transport; the only one available to MCP callers.

string
string

MIME type; optional when file_base64 is a data: URI.

Headers
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses
200

OK

Language
Credentials
Bearer
anlfy_...
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json