# Enroll a customer (deprecated)

This legacy enrollment endpoint is no longer supported. Every call returns 410,
  on all API versions. It no longer enrolls customers or returns the customer object.
The endpoint had already been reduced to a stub in **July 2023**, when the
`confirm_enrollment` status was removed. Once approved by Resolve, customers are either
`enrolled` (if they applied through an application) or `pending_enrollment` (if credit
checked), so there is nothing for this endpoint to do.
Partners recording a Net Terms Agreement acceptance should use
`POST /customers/{customer_id}/net-terms-acceptance` in the
[Partners API](https://api-docs.resolvepay.com/partners-api/openapi), which records the
acceptance and enrolls the customer in one transaction.

Endpoint: POST /customers/{customer_id}/enroll
Version: V5
Security: bearerAuth, basicAuth

## Security:

  - `bearerAuth` (unknown)
    http bearer JWT

  - `basicAuth` (unknown)
    http basic

## Path parameters:

  - `customer_id` (string, required)
    ID of the customer to enroll

## Response 410:

  - `410` (unknown)
    This legacy enrollment endpoint is no longer supported.

## Response 410 fields (application/json):

  - `error` (object)

  - `error.code` (string)
    A short string, identifying the error
    Enum: "INVALID_REQUEST"

  - `error.message` (string)
    A short string, describing error details
    Example: This enrollment endpoint is no longer supported.

  - `error.type` (string)
    A short string, describing error type
    Enum: "invalid_request"