> ## Documentation Index > Fetch the complete documentation index at: https://docs.corbado.com/llms.txt > Use this file to discover all available pages before exploring further. # Get connectrulesetsmetadata > Retrieves a list of ruleSets Metadata for a Connect project ## OpenAPI ````yaml https://backendapi.cloud.corbado.io/v2/openapi.yaml get /connect/rulesetsMetadata openapi: 3.0.3 info: version: 2.0.0 title: Corbado Backend API description: > # Introduction This documentation gives an overview of all Corbado Backend API calls to implement passwordless authentication with Passkeys. contact: name: Corbado team email: support@corbado.com url: https://www.corbado.com servers: - url: https://backendapi.corbado.io/v2 security: - basicAuth: [] - bearerAuth: [] tags: - name: Users description: All API calls to manage users - name: Sessions description: All API calls to manage sessions - name: Challenges description: All API calls to manage challenges - name: Identifiers description: All API calls to manage login identifiers - name: Passkeys description: All API calls for passkey flows - name: SSO description: All API calls for SSO flows - name: AuthEvents description: All API calls to manage authentication events - name: PasskeyEvents description: All API calls to manage passkey events - name: ProjectConfig description: All API calls to manage project configurations - name: ConnectTokens description: All API calls to manage connectTokens - name: PasskeyChallenges description: All API calls to manage passkey challenges - name: WebhookEndpoints description: All API calls to manage webhook endpoints - name: PasswordManagers description: All API calls to manage password managers - name: ClientEnvs description: All API calls to manage client environments - name: Devices description: All API calls to manage devices - name: Exports description: All API calls to manage project export files paths: /connect/rulesetsMetadata: get: tags: - ConnectRollout description: Retrieves a list of ruleSets Metadata for a Connect project operationId: ConnectRulesetsList parameters: - name: filter[] in: query description: > Filter results by specific fields and conditions. Format: `::`. Supported operators include: - `eq`: equals (e\.g\. `email:eq:mail@example\.com` matches items where email equals mail@example\.com) - `gt`: greater than (e\.g\. `created:gt:2021-01-01T00:00:00` matches items created after Jan 1, 2021) - `lt`: less than (e\.g\. `created:lt:2021-01-01T00:00:00` matches items created before Jan 1, 2021) required: false style: form explode: true schema: type: array items: type: string examples: filterEmail: summary: Filter by email address value: - identifierType:eq:email - identifierValue:eq:mail@example.com filterTimepoint: summary: Filter by date after July 20, 2021 value: - timePoint:gt:2021-07-20T00:00:00 - name: sort in: query description: > Field and direction to sort results. Use the format `fieldName:asc` or `fieldName:desc`. required: false schema: type: string example: createdAt:desc - name: page in: query description: | The page number to retrieve for paginated results. required: false schema: type: integer default: 1 example: 1 - name: pageSize in: query description: | The number of items to return per page. Useful for pagination. required: false schema: type: integer default: 10 example: 20 responses: '200': description: List of project rulesets content: application/json: schema: $ref: >- #/components/schemas/ConnectManagementConnectRulesetMetadataListRsp default: description: Error content: application/json: schema: allOf: - type: object required: - httpStatusCode - message - requestData - runtime properties: httpStatusCode: description: HTTP status code of operation type: integer format: int32 message: type: string example: OK requestData: description: >- Data about the request itself, can be used for debugging type: object required: - requestID properties: requestID: description: >- Unique ID of request, you can provide your own while making the request, if not the ID will be randomly generated on server side type: string example: req-557...663 link: description: Link to dashboard with details about request type: string example: >- https://my.corbado.com/requests/req-xxxxxxxxxxxxxxxxxxx runtime: description: Runtime in seconds for this request type: number format: float example: 0.06167686 - type: object required: - error properties: data: type: object error: type: object required: - type properties: type: description: Type of error type: string details: description: Details of error type: string validation: description: Validation errors per field type: array items: type: object required: - field - message properties: field: type: string message: type: string links: description: Additional links to help understand the error type: array items: type: string security: - basicAuth: [] - bearerAuth: [] components: schemas: ConnectManagementConnectRulesetMetadataListRsp: type: object required: - items - paging properties: items: type: array items: $ref: '#/components/schemas/ConnectManagementConnectRulesetMetadata' paging: type: object required: - page - totalPages - totalItems properties: page: description: current page returned in response type: integer default: 1 totalPages: description: total number of pages available type: integer totalItems: description: total number of items available type: integer ConnectManagementConnectRulesetMetadata: type: object required: - name - isActive - rulesetID - type - version - createdMs properties: name: type: string isActive: type: boolean rulesetID: type: string version: type: integer type: type: string createdMs: type: integer format: int64 securitySchemes: basicAuth: type: http scheme: basic description: > Basic authentication is used to authenticate requests to the Backend API. The username is the project ID and the password is the API secret. The project ID and API secret can be found in the [Developer Panel](https://app.corbado.com/settings/api-secrets). bearerAuth: type: http scheme: bearer description: >- Use a raw versioned API key (corbado1_v2__), or the legacy base64 encoding of projectID:API-secret. Stored keys require the permission assigned to the endpoint in BAPI and must satisfy their expiry and IP restrictions. Project-derived internal credentials additionally require an allowed source IP. ````