# Effective Date

**Effective date in ISO format (YYYY-MM-DD)**

# Tier Schedule Response

## 200 OK

- **tier_name**: Name of a tier contained in the credit product. Mutually exclusive with `tier_rates`
- **effective_date**: Required. Date the tier should be effective in YYYY-MM-DD format
- **tier_rates**: Custom rates per category. Mutually exclusive with `tier_name` (Has additional fields)
- **penalty_rates**: Custom rates per category for penalties (Has additional fields)
- **credit_product_token**: Required. Globally unique identifier for a credit product

## Error Responses

### 400
- A parameter in the query given in the request does not match the valid queries for the endpoint.

### 401
| Error | Description |
|---|---|
| User has not been authenticated | Invalid or missing API key |
| API key is not active | The API key used is no longer active |
| Could not find API key | The API key provided is not associated with any user |
| Please provide API key in Authorization header | The Authorization header is not in the request |
| Please provide API key in the form Authorization: [api-key] | The Authorization header is not formatted properly |
| Insufficient privileges. Issuing API key required | Write access requires an Issuing API key. Reach out at [lithic.com/contact](/content/contact/index.html) |
| Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege |

### 404
- The specified resource was not found.

### 422
- Unprocessable entity.

### 429
- Client has exceeded the number of allowed requests in a given time period.

| Error | Description |
|---|---|
| Rate limited, too many requests per second | User has exceeded their per second rate limit |
| Rate limited, reached daily limit | User has exceeded their daily rate limit |
| Rate limited, too many keys tried | One IP has queried too many different API keys |

# Sample cURL Request

```shell
curl --request GET \
     --url https://sandbox.lithic.com/v1/financial_accounts/financial_account_token/interest_tier_schedule/effective_date \
     --header 'accept: application/json'
```

# Sample JSON Response

```json
{
  "tier_name": "string",
  "effective_date": "2026-07-18",
  "tier_rates": {},
  "penalty_rates": {},
  "credit_product_token": "string"
}
```