Creavily · Authentication Profile

Creavily Authentication

Authentication

Creavily secures its APIs with apiKey and http across 5 declared security schemes, as derived from its OpenAPI definitions.

Social MediaE-CommercePublishingAutomation

Methods: apiKey, http Schemes: 5 OAuth flows: API key in: cookie, header

Security Schemes

publicBearer http

scheme: bearer

dashboardSessionCookie apiKey

· in: cookie (creavily_dashboard_session)

internalServiceToken apiKey

· in: header (x-creavily-internal-token)

servicePrincipalToken apiKey

· in: header (x-creavily-service-principal-token)

browserSessionExchangeCookie apiKey

· in: cookie (creavily_browser_session_exchange)

Source

Authentication Profile

generated: '2026-11-02'
method: derived
source: openapi/creavily-openapi.json
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - cookie
  - header
schemes:
- name: publicBearer
  type: http
  scheme: bearer
  description: Use a Creavily API key or OAuth access token. Public endpoints are scoped to
    the authenticated principal organization.
  sources:
  - openapi/creavily-openapi.json
- name: dashboardSessionCookie
  type: apiKey
  in: cookie
  parameter: creavily_dashboard_session
  description: Host-only HttpOnly Dashboard session cookie issued after the one-time browser-session
    exchange. Browser clients rely on credentialed requests and an approved Origin; JavaScript
    does not read this value.
  sources:
  - openapi/creavily-openapi.json
- name: internalServiceToken
  type: apiKey
  in: header
  parameter: x-creavily-internal-token
  description: Internal service credential for non-public operational routes. It is never exposed
    to browser or third-party clients.
  sources:
  - openapi/creavily-openapi.json
- name: servicePrincipalToken
  type: apiKey
  in: header
  parameter: x-creavily-service-principal-token
  description: Server-side service-principal credential accepted by policy-gated admin routes.
    It is never exposed to browser or third-party clients.
  sources:
  - openapi/creavily-openapi.json
- name: browserSessionExchangeCookie
  type: apiKey
  in: cookie
  parameter: creavily_browser_session_exchange
  description: Short-lived HttpOnly temporary cookie used only with POST /v1/auth/browser-session/exchange.
    It is cleared after a successful exchange or logout.
  sources:
  - openapi/creavily-openapi.json

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
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.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/creavily-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.