creator-api-com Media API
The Media API from creator-api-com — 7 operation(s) for media.
The Media API from creator-api-com — 7 operation(s) for media.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/creator-api-com:creator-api-com-media-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Creator Api Com Media API
version: '1.0'
description: 'Operations tagged Media across 2 of this provider''s published API definitions: creator-api-com-openapi.json, creator-api-com-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Media
paths:
/v1/{account}/media/upload:
post:
summary: Media Upload
description: 'Upload a photo or video to a connected account and get back what you attach to a
post. Send it as multipart form-data with a single `file` field. Works for Fansly,
OnlyFans and 4based. Fansly returns {media_id, account_media_id, mime, size} (put
account_media_id in a post''s attachments). OnlyFans returns {platform, media_type,
mime, size, md5, media_file} (put `media_file` as one item of the post''s
`mediaFiles`; it is single-use, post it promptly). Billed as a write.
4based is different: there is no separate upload-then-attach step, the upload
itself publishes the post immediately and this returns the created post object
directly. Optional extra multipart fields: `categories` (comma-separated, default
media/image or media/video by mime type), `description`, `price` (0 or 300+, a
standalone PPV price — ignored if `is_subscription_item` is also set, 4based never
prices subscription-included content separately), `is_subscription_item`
(true/false), `tag` (comma-separated), `private` (true/false), `to_be_posted_at`
(ISO 8601, schedules instead of publishing now). Set `reel=true` for a free
4based video up to 120 seconds; incompatible price/privacy/schedule fields are rejected.'
operationId: media_upload_v1__account__media_upload_post
parameters:
- name: account
in: path
required: true
schema:
type: string
title: Account
- name: x-api-key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Api-Key
- name: authorization
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Authorization
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Media
/v1/{account}/media/reels:
post:
summary: Fourbased Reel Upload
description: 'Publish a free 4based video eligible for Reels (multipart file, max 120 seconds).
Optional description and comma-separated tag. Returns the original created post;
4based handles processing and Reel inclusion. Requires a full key, costs 2 credits.
This publishes content immediately; it is not a preview or a vault-only upload.'
operationId: fourbased_reel_upload_v1__account__media_reels_post
parameters:
- name: account
in: path
required: true
schema:
type: string
title: Account
- name: x-api-key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Api-Key
- name: authorization
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Authorization
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Media
/v1/{account}/media/vault:
post:
summary: Media Vault Upload
description: 'Upload a photo or video and get back a PERSISTENT numeric vault media id (unlike
POST /media/upload, whose descriptor is single-use and must be attached to a post or
message immediately). OnlyFans only for now -- Fansly''s vault model differs, follow-up.
Send either multipart form-data with a `file` field, OR a JSON body with a `file_url`
(we fetch it server-side) -- exactly one of the two. Optional multipart field / JSON
key `async`: `true` always returns 202 immediately with a polling URL; left unset, the
upload runs inline and returns 200 with the result if it finishes within ~20s (typical
for a photo), otherwise falls back to the same 202 + polling response as `async: true`
-- videos regularly need longer than that to transcode. Poll with
GET /v1/{account}/media/vault/upload-status/{job_id} for pending/processing/completed/failed.
Billed as a write (charged on job creation, refunded automatically if the job fails).'
operationId: media_vault_upload_v1__account__media_vault_post
parameters:
- name: account
in: path
required: true
schema:
type: string
title: Account
- name: x-api-key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Api-Key
- name: authorization
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Authorization
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Media
/v1/{account}/media/vault/upload-status/{job_id}:
get:
summary: Media Vault Status
description: 'Poll a media/vault upload job. Status: pending -> processing -> completed | failed.
Free (not billed) -- only the original upload is charged.'
operationId: media_vault_status_v1__account__media_vault_upload_status__job_id__get
parameters:
- name: account
in: path
required: true
schema:
type: string
title: Account
- name: job_id
in: path
required: true
schema:
type: string
title: Job Id
- name: x-api-key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Api-Key
- name: authorization
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Authorization
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Media
/v1/{account}/media/mirror:
post:
summary: Media Mirror Create
description: 'Re-host an OnlyFans CDN media URL (e.g. the "url" field inside a post/vault/story
response) under a stable CreatorAPI link that does not expire -- OF''s own signed URLs
do. Body: {"source_url": "https://cdn2.onlyfans.com/..."}. Only onlyfans.com media
hosts are accepted. Returns {id, status, download_url, download_expires} once done
(download_expires is refreshed on every GET of the job, so an active integration''s link
never actually goes stale). Billed as a write.'
operationId: media_mirror_create_v1__account__media_mirror_post
parameters:
- name: account
in: path
required: true
schema:
type: string
title: Account
- name: x-api-key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Api-Key
- name: authorization
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Authorization
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Media
/v1/{account}/media/mirror/{job_id}:
get:
summary: Media Mirror Status
description: Fetch a mirror job (and refresh its download link if completed). Free.
operationId: media_mirror_status_v1__account__media_mirror__job_id__get
parameters:
- name: account
in: path
required: true
schema:
type: string
title: Account
- name: job_id
in: path
required: true
schema:
type: string
title: Job Id
- name: x-api-key
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: X-Api-Key
- name: authorization
in: header
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Authorization
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Media
/v1/media/mirror/{job_id}/download:
get:
summary: Media Mirror Download
description: 'Serve a completed mirror''s bytes. Token in the query string (from download_url) is
the intended path -- no API key needed, safe to embed/share the link itself. Falls back
to key auth if no token is given, same pattern as the exports download route.'
operationId: media_mirror_download_v1_media_mirror__job_id__download_get
parameters:
- name: job_id
in: path
required: true
schema:
type: string
title: Job Id
- name: token
in: query
required: false
schema:
anyOf:
- type: string
- type: 'null'
title: Token
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Media
components:
schemas:
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
type: object
required:
- loc
- msg
- type
title: ValidationError
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
x-refined-from:
- creator-api-com-openapi.json
- creator-api-com-openapi.json