Create Prints · Authentication Profile

Create Prints Authentication

Authentication

Create Prints secures its APIs with apiKey, http, and oauth2 across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyAI ArtGenerative AIArt PrintsPrint on DemandE-CommerceInterior DesignMCP
Methods: apiKey, http, oauth2 Schemes: 3 OAuth flows: authorizationCode API key in: header

Security Schemes

agentApiKey apiKey
· in: header (X-API-Key)
agentBearer http
scheme: bearer
oauth2 oauth2
· flows: authorizationCode

Source

Authentication Profile

Raw ↑
generated: '2026-11-04'
method: searched
source: https://www.createprints.ai/auth.md
summary:
  types:
  - apiKey
  - http
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
schemes:
- name: agentApiKey
  type: apiKey
  in: header
  parameter: X-API-Key
  description: Create Prints account API key beginning with `cp_`. Required scopes vary by operation.
  sources:
  - openapi/createprints-ai-openapi.yml
- name: agentBearer
  type: http
  scheme: bearer
  description: Account API key (`cp_…`) or MCP OAuth token (`cp_mcp_access_…`) in Authorization.
  sources:
  - openapi/createprints-ai-openapi.yml
- name: oauth2
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.createprints.ai/api/oauth/authorize
    tokenUrl: https://api.createprints.ai/api/oauth/token
    scopes: 6
  description: Create Prints OAuth 2.0 authorization-code flow with PKCE for MCP and agent clients.
  sources:
  - openapi/createprints-ai-openapi.yml
docs: https://www.createprints.ai/auth.md
oauth2_details:
  grant_types_supported:
  - authorization_code
  - refresh_token
  pkce: S256 only
  token_endpoint_auth_methods_supported:
  - none
  client_registration: OAuth 2.0 Dynamic Client Registration (RFC 7591) at https://api.createprints.ai/api/oauth/register;
    no manual sign-up or API key required
  authorization_server_metadata: 'https://api.createprints.ai/.well-known/oauth-authorization-server (RFC 8414;
    includes an agent_auth block declaring identity_types_supported: ["service_auth"])'
  protected_resource_metadata: https://mcp.createprints.ai/.well-known/oauth-protected-resource/mcp (RFC 9728),
    advertised via WWW-Authenticate on a 401 from the MCP endpoint
  revocation_endpoint: https://api.createprints.ai/api/mcp/revoke
  resource_indicator: resource parameter sent on the authorize request
api_keys:
  prefix: cp_
  oauth_token_prefix: cp_mcp_access_
  issued_from: self-service agent API key from the signed-in account page (per the developers page)
  headers:
  - X-API-Key
  - 'Authorization: Bearer'
note: Docs-read only; no auth, token, registration or revocation endpoint was called.
docs_also:
- https://www.createprints.ai/developers

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/createprints-ai-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.

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