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

Clear Street Screener API

Search instruments and manage saved screeners.

Clear Street Screener API is one of 23 APIs that Clear Street publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 3 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 2025-10-31.

Requests are made against 3 base URLs: https://api.clearstreet.com, https://api-dev.clearstreet.com, http://localhost:5001.

6 operations 3 paths 27 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2025-10-31
Base URL
https://api.clearstreet.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Clear Street Screener API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 6

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

Screener 6

Search instruments and manage saved screeners.

GET
/v1/saved-screeners
Get Screeners
get_screeners → 200500
POST
/v1/saved-screeners
Create Screener
create_screener body → 200400500
GET
/v1/saved-screeners/{screener_id}
Get Screener By ID
get_screener_by_id 1 param → 200400404500
PUT
/v1/saved-screeners/{screener_id}
Replace Screener
replace_screener 1 param body → 200400404500
DELETE
/v1/saved-screeners/{screener_id}
Delete Screener
delete_screener 1 param → 200404500
POST
/v1/screener
Search Screener
search_screener body → 200400422500

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are ScreenerEntry (7 properties), ResponseMetadata (6 properties), FieldRef (4 properties), CreateScreenerRequest (4 properties). Each schema is shown below with its type and property counts.

OperatorArg
string
Argument that modifies operator behavior.
ScreenerColumn
object
A single column in the screener search response.
4 properties 3 required
Pagination
string
Base64URL-encoded pagination token
Modifier
object
Arithmetic modifier applied to a variable value.
2 properties 2 required
ErrorDetails
array
ScreenerEntryList
array
ScreenerRow
array
A single row of screener columns for one instrument.
SearchFilter
object
A single filter condition. When op and right are both absent, the filter is "unenabled": it persists a left field reference without applying any predicate. Une…
3 properties 1 required
ModifierOp
string
Modifier operation applied to a variable.
FilterOpSpec
object
Operator specification with optional behavioral arguments.
2 properties 1 required
ResponseMetadata
object
Metadata for the response. This will always contain a request ID which can be used to identify the request to Clear Street for tracing, and optionally may incl…
6 properties 1 required
ScreenerSearchRequest
Request body for POST /screener.
SortDirection
string
Sort direction sorted results
Variable
object
A variable reference (field or built-in like today).
4 properties 1 required
FieldPeriod
string
Reporting period for financial data fields.
FieldLookback
string
Historical lookback window for price/change fields.
CreateScreenerRequest
object
Request body for creating or updating a saved screener configuration
4 properties
ApiError
object
A direct mapping of tonic::Status, for use in HTTP responses.
3 properties 2 required
FilterValue
object
A filter value: either a literal or a variable reference.
2 properties
PaginationParams
object
Pagination parameters for list endpoints Important: pagetoken contains both limit and offset. When pagetoken is provided, pagesize is ignored. Only use pagesiz…
2 properties
ScreenerRowList
array
ScreenerEntry
object
A saved screener configuration entry
7 properties 5 required
FilterOperator
string
Filter operators supported by the screener. Abbreviated and lowercase forms are accepted as serde aliases for backward compatibility with earlier API revisions…
FieldType
string
The data type of a screener field value.
SortSpec
object
A sort specification pairing a field with a direction.
2 properties 1 required
FieldRef
object
A reference to a screener field.
4 properties 1 required
BaseResponse
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

clear-street-screener-api-openapi.yml Raw ↑

Other APIs Clear Street publishes across the network.

Clear Street MCP Server
Clear Street API (Trades and Uploads)
Clear Street Accounts API
Clear Street API version API
Clear Street Calendar API
Clear Street Entities API
Clear Street Holdings API
Clear Street Instrument Data API
Clear Street Instruments API
Clear Street Inventories API
Clear Street Locates API
Clear Street Margin API
Where this information came from

This is an independent, third-party profile of Clear Street Screener 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.