> ## Documentation Index > Fetch the complete documentation index at: https://developers.hubspot.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # List scores > Retrieve a list of lead scores from your HubSpot account. This endpoint allows you to paginate through scores using the 'limit' and 'after' query parameters. It is useful for accessing and managing lead scoring data in a structured manner. It is eventually consistent and may take a few seconds for new scores to show up. > [accordion] Supported products > [accordion] Required Scopes ## OpenAPI ````yaml specs/2027-03-beta/marketing-lead-scoring-v2027-03-beta.json GET /marketing/lead-scoring/2027-03-beta/scores openapi: 3.0.1 info: title: Marketing Lead Scoring description: Basepom for all HubSpot Projects version: 2027-03-beta x-hubspot-product-tier-requirements: marketing: FREE sales: FREE service: FREE cms: FREE commerce: FREE crmHub: FREE dataHub: FREE servers: - url: https://api.hubapi.com security: [] tags: - name: Advanced - name: Basic paths: /marketing/lead-scoring/2027-03-beta/scores: get: tags: - Basic summary: List scores description: >- Retrieve a list of lead scores from your HubSpot account. This endpoint allows you to paginate through scores using the 'limit' and 'after' query parameters. It is useful for accessing and managing lead scoring data in a structured manner. It is eventually consistent and may take a few seconds for new scores to show up. operationId: get-/marketing/lead-scoring/2027-03-beta/scores parameters: - name: after in: query description: >- The paging cursor token of the last successfully read resource will be returned as the `paging.next.after` JSON property of a paged response containing more results. required: false style: form explode: true schema: type: string - name: limit in: query description: The maximum number of results to display per page. Defaults to 10. required: false style: form explode: true schema: type: integer format: int32 default: 10 responses: '200': description: successful operation content: application/json: schema: $ref: >- #/components/schemas/CollectionResponsePublicScoreFragmentForwardPaging default: $ref: '#/components/responses/Error' description: '' security: [] components: schemas: CollectionResponsePublicScoreFragmentForwardPaging: required: - results type: object properties: paging: $ref: '#/components/schemas/ForwardPaging' results: type: array description: >- An array of public score fragments. Each item in the array is a PublicScoreFragment object. items: $ref: '#/components/schemas/PublicScoreFragment' ForwardPaging: type: object properties: next: $ref: '#/components/schemas/NextPage' description: >- Paging information for forward-only pagination. Contains the next page reference when more results are available; omitted or empty on the last page. PublicScoreFragment: required: - id - lastConfigurationChangeTimestamp - name - scoreStatus - scoreType - scoredObjectTypeId type: object properties: createdAt: type: string format: date-time id: type: string description: The unique identifier for this scoring fragment. lastConfigurationChangeTimestamp: type: string description: >- The date and time when the configuration was last changed, in ISO 8601 format. format: date-time name: type: string description: The name assigned to this scoring configuration. publishedAt: type: string format: date-time scoreStatus: type: string scoreType: type: string description: The type of score associated with this configuration. scoredObjectTypeId: type: string description: The identifier of the object type that is being scored. Error: required: - category - correlationId - message type: object properties: category: type: string description: The error category. context: type: object additionalProperties: type: array items: type: string description: Context about the error condition. example: >- {invalidPropertyName=[propertyValue], missingScopes=[scope1, scope2]} correlationId: type: string description: >- A unique identifier for the request. Include this value with any error reports or support tickets. format: uuid example: aeb5f871-7f07-4993-9211-075dc63e7cbf errors: type: array description: Further information about the error. items: $ref: '#/components/schemas/ErrorDetail' links: type: object additionalProperties: type: string description: >- A map of link names to associated URIs containing documentation about the error or recommended remediation steps. message: type: string description: >- A human readable message describing the error along with remediation steps where appropriate. example: An error occurred subCategory: type: string description: >- A specific category that contains more specific detail about the error. description: >- Represents an error response returned by the API when an operation fails. This component is used in various endpoints to provide detailed information about the error encountered. example: message: Invalid input (details will vary based on the error) correlationId: aeb5f871-7f07-4993-9211-075dc63e7cbf category: VALIDATION_ERROR links: knowledge-base: https://www.hubspot.com/products/service/knowledge-base NextPage: required: - after type: object properties: after: type: string description: >- A string token used as a cursor to indicate the position after the last successfully read resource in a paginated response. link: type: string description: A string containing the URL link to access the next page of results. description: >- Specifies the paging information needed to retrieve the next set of results in a paginated API response ErrorDetail: required: - message type: object properties: code: type: string description: >- The status code associated with the error detail. This is a string property. context: type: object additionalProperties: type: array items: type: string description: >- Context about the error condition, represented as an object where each key is a context name and the value is an array of strings providing further details. example: '{missingScopes=[scope1, scope2]}' in: type: string description: >- The name of the field or parameter in which the error was found. This is a string property. message: type: string description: >- A human readable message describing the error along with remediation steps where appropriate. It is a required string property. subCategory: type: string description: >- A specific category that contains more specific detail about the error. This is a string property. description: >- Represents detailed information about an error that occurred in the API. This component is used to provide additional context and specifics about errors, typically as part of an error response. responses: Error: description: An error occurred. content: '*/*': schema: $ref: '#/components/schemas/Error' ````