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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Clerk

Clerk Allowlist & Blocklist API

Identifiers permitted or denied from signing up.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Allowlist & Blocklist. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2026-05-12.

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

6 operations 4 paths 2 schemas 2 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-05-12
Base URL
https://api.clerk.com/v1
Authentication
HTTP Bearer
Contact
Clerk
License
Clerk Documentation
Resource Areas
1

Authentication & Security 1

Clerk Allowlist & Blocklist API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Your Clerk instance Secret Key (starts with sktest or sklive) passed as Authorization: Bearer YOURSECRETKEY.

Paths & Operations 6

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

Allowlist & Blocklist 6

Identifiers permitted or denied from signing up.

GET
/allowlist_identifiers
List all allowlist identifiers
listAllowlistIdentifiers → 200
POST
/allowlist_identifiers
Add an allowlist identifier
createAllowlistIdentifier body → 200
DELETE
/allowlist_identifiers/{identifier_id}
Delete an allowlist identifier
deleteAllowlistIdentifier 1 param → 200
GET
/blocklist_identifiers
List all blocklist identifiers
listBlocklistIdentifiers → 200
POST
/blocklist_identifiers
Add a blocklist identifier
createBlocklistIdentifier body → 200
DELETE
/blocklist_identifiers/{identifier_id}
Delete a blocklist identifier
deleteBlocklistIdentifier 1 param → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Identifier (5 properties), DeletedObject (3 properties). Each schema is shown below with its type and property counts.

DeletedObject
object
3 properties
Identifier
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clerk-dev-allowlist-blocklist-api-openapi.yml Raw ↑

Other APIs Clerk publishes across the network.

Clerk Account Portal API
AE Profile APIs.io
Clerk Active Sessions API
AE Profile APIs.io
Clerk Actor Tokens API
AE Profile APIs.io
Clerk Agent Tasks API
AE Profile APIs.io
Clerk Allow-list / Block-list API
AE Profile APIs.io
Clerk API Keys API
AE Profile APIs.io
Clerk Application Transfers API
AE Profile APIs.io
Clerk Applications API
AE Profile APIs.io
Clerk Backup Codes API
AE Profile APIs.io
Clerk Beta Features API
AE Profile APIs.io
Clerk Billing API
AE Profile APIs.io
Clerk Checkouts API
AE Profile APIs.io
#Allowlist & Blocklist
← Back to C APIs
API Details
ID
clerk-com:clerk-dev-allowlist-blocklist-api
Base URL
https://api.clerk.com/v1
Docs
https://clerk.com/docs/reference/backend-api/tag/Users
Provider
Clerk
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=clerk-dev-allowlist-blocklist-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/clerk-dev-allowlist-blocklist-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Clerk Allowlist & Blocklist 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.