How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Clerk Application Transfers API

An object representing a transfer request for an application between workspaces.The high-level flow for application transfer:1. The initial workspace can create an application transfer. A single-use `code` will be generated which may be distributed to any end-user of Clerk.2. The code must be claimed through the clerk dashboard: https://dashboard.clerk.com/apps/transfer?code=Note that once a transfer is claimed, the original workspace will no longer have access to the application.

Clerk Application Transfers API is one of 104 APIs that Clerk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Application Transfers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 4 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version BETA.

Requests are made against a single base URL, https://api.clerk.com/v1.

4 operations 3 paths 4 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
BETA
Base URL
https://api.clerk.com/v1
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Clerk Application Transfers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (platform_api_access_token). By default, every request must be authenticated.

  • platform_api_access_token — Platform API access token.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Application Transfers 4

An object representing a transfer request for an application between workspaces. The high-level flow for application transfer: 1. The initial workspace can create an application t…

GET
/platform/application_transfers
List Application Transfers
PlatformListApplicationTransfers 4 params → 200401403422
POST
/platform/applications/{applicationID}/transfers
Create an Application Transfer
PlatformCreateApplicationTransfer 1 param → 201401403409
GET
/platform/applications/{applicationID}/transfers/{transferID}
Get an Application Transfer
PlatformGetApplicationTransfer 2 params → 200401403404
DELETE
/platform/applications/{applicationID}/transfers/{transferID}
Cancel an Application Transfer
PlatformCancelApplicationTransfer 2 params → 200401403404409

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are PlatformApplicationTransferResponse (9 properties), ClerkError (4 properties), ClerkErrors (3 properties), PlatformListApplicationTransfersResponse (2 properties). Each schema is shown below with its type and property counts.

ClerkError
object
4 properties 3 required
ClerkErrors
object
3 properties 1 required
PlatformListApplicationTransfersResponse
object
A paginated list of application transfers.
2 properties 2 required
PlatformApplicationTransferResponse
object
Represents an application transfer request. Application transfers allow transferring ownership of an application from one organization to another.
9 properties 9 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clerk-com-application-transfers-api-openapi.yml Raw ↑

Other APIs Clerk publishes across the network.

Clerk Account Portal API
Clerk Active Sessions API
Clerk Actor Tokens API
Clerk Agent Tasks API
Clerk Allow-list / Block-list API
Clerk API Keys API
Clerk Applications API
Clerk Backup Codes API
Clerk Beta Features API
Clerk Billing API
Clerk Checkouts API
Clerk Clear Site Data API
Where this information came from

This is an independent, third-party profile of Clerk Application Transfers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.