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 Allow-list / Block-list API

Allow-lists and Block-lists allow you to control who can sign up or sign into your application, by restricting access based on the user's emailaddress or phone number.

Clerk Allow-list / Block-list API is one of 104 APIs that Clerk publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Allow-list / Block-list. 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 6 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2025-11-10.

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

6 operations 4 paths 6 schemas 2 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Clerk Allow-list / Block-list API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (sk__) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Secret key, obtained under "API Keys" in the Clerk Dashboard.

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.

Allow-list / Block-list 6

Allow-lists and Block-lists allow you to control who can sign up or sign in to your application, by restricting access based on the user's email address or phone number.

GET
/allowlist_identifiers
List All Identifiers on the Allow-list
ListAllowlistIdentifiers 3 params → 200401402
POST
/allowlist_identifiers
Add Identifier to the Allow-list
CreateAllowlistIdentifier body → 200400402422
DELETE
/allowlist_identifiers/{identifier_id}
Delete Identifier from Allow-list
DeleteAllowlistIdentifier 1 param → 200402404
GET
/blocklist_identifiers
List All Identifiers on the Block-list
ListBlocklistIdentifiers → 200401402
POST
/blocklist_identifiers
Add Identifier to the Block-list
CreateBlocklistIdentifier body → 200400402422
DELETE
/blocklist_identifiers/{identifier_id}
Delete Identifier from Block-list
DeleteBlocklistIdentifier 1 param → 200402404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are AllowlistIdentifier (8 properties), BlocklistIdentifier (7 properties), DeletedObject (5 properties), ClerkError (4 properties). Each schema is shown below with its type and property counts.

DeletedObject
object
5 properties 2 required
BlocklistIdentifier
object
7 properties
ClerkErrors
object
3 properties 1 required
BlocklistIdentifiers
object
2 properties 2 required
AllowlistIdentifier
object
8 properties
ClerkError
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clerk-com-allow-list-block-list-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 API Keys API
Clerk Application Transfers 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 Allow-list / Block-list 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.