Elastic Path Logs Time to Live Settings API
You can use the Logs TTL Settings endpoint to retrieve and update settings controlling logs time-to-live (TTL).
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/elastic-path-logs-time-to-live-settings-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Personal Data Introduction Logs Time to Live Settings API
version: '1.0'
description: '
In Commerce, every change to a user’s personal data is logged.
Personal data sets are groups of data items that are related to each other. For example, customer, addresses, and authentication information. The contents of a personal data set is dynamic. Data items are attached to each other automatically as they are created or updated.
The API allows you to fetch these logs, including the list of related data items. In other words, the data items that belong to the same personal data set.
Log entries are kept in the system for a limited time. You can configure the retention period using the Logs Time-to-live (TTL) settings API. The default retention period is 365 days for production store types and 7 days for other store types.
## Personal Data Resource Types
| Entity type | Endpoint | Documentation |
|-------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------|
| customer | `v2/customers/{id}` | [Customers](/docs/customer-management/customer-management-api/customer-management-api-overview) |
| account | `v2/accounts/{id}` | [Accounts](/docs/api/accounts/post-v-2-accounts) |
| account-member | `v2/account-members/{id}` | [Account Members](/docs/api/accounts/account-members) |
| account-membership | `v2/accounts/{accountId}/account-memberships/{id}` | [Account Memberships](/docs/api/accounts/account-membership) |
| address | `v2/customers/{customerId}/addresses/{id}`; `v2/accounts/{accountId}/addresses/{id}` | [Addresses](/docs/api/addresses/addresses-introduction) |
| user-authentication-info | `v2/authentication-realms/{realmId}/user-authentication-info/{id}` | [User Authentication Info](/docs/api/single-sign-on/user-authentication-infos) |
| user-authentication-oidc-profile-info | `v2/authentication-realms/{authenticationRealmId}/user-authentication-info/{userAuthenticationInfoId}/user-authentication-oidc-profile-info/{id}` | [User Authentication OIDC Profile Info](/docs/api/single-sign-on/user-authentication-oidc-profile-infos) |
| user-authentication-password-profile-info | `v2/authentication-realms/{authenticationRealmId}/user-authentication-info/{userAuthenticationInfoId}/user-authentication-password-profile-info/{id}` | [User Authentication Password Profile Info](/docs/api/single-sign-on/user-authentication-password-profile-infos) |
| order | `v2/orders/{id}` | [Orders](/docs/api/carts/orders) |
'
contact:
name: Elastic Path
url: https://www.elasticpath.com
email: support@elasticpath.com
license:
url: https://elasticpath.dev
name: MIT
servers:
- url: https://useast.api.elasticpath.com
description: US East
- url: https://euwest.api.elasticpath.com
description: EU West
security:
- bearerAuth: []
tags:
- name: Logs Time to Live Settings
description: 'You can use the Logs TTL Settings endpoint to retrieve and update settings controlling logs time-to-live (TTL).
'
paths:
/v2/settings/logs-ttl:
get:
tags:
- Logs Time to Live Settings
summary: Get Logs Time-to-Live (TTL) Settings
operationId: get-logs-ttl
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
properties:
data:
type: object
$ref: '#/components/schemas/LogsTtl'
'401':
$ref: '#/components/responses/UnauthorizedError'
default:
$ref: '#/components/responses/InternalServerError'
put:
tags:
- Logs Time to Live Settings
summary: Update Logs Time-to-Live (TTL) Settings
operationId: put-logs-ttl
requestBody:
content:
application/json:
schema:
type: object
required:
- data
properties:
data:
$ref: '#/components/schemas/LogsTtl'
required:
- type
examples:
update-logs-ttl:
summary: Update Logs TTL
value:
data:
days: 10
type: time_to_live
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
properties:
data:
type: object
$ref: '#/components/schemas/LogsTtl'
'400':
$ref: '#/components/responses/BadRequestError'
default:
$ref: '#/components/responses/InternalServerError'
components:
responses:
BadRequestError:
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
bad-request-error:
summary: Required field missing
value: "{\n \"errors\": [\n {\n \"title\": \"Bad Request\",\n \"status\": \"400\",\n \"detail\": \"Validation failed: field 'Type' on the 'ttl-type' tag.\"\n }\n ]\n}\n"
UnauthorizedError:
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
unauthorized-error:
summary: Unauthorized
value: "{\n \"errors\": [\n {\n \"title\": \"Unauthorized\",\n \"status\": \"401\"\n }\n ]\n}\n"
InternalServerError:
description: Internal server error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
examples:
internal-server-error:
summary: Internal server error
value: "{\n \"errors\": [\n {\n \"title\": \"Internal Server Error\",\n \"status\": \"500\",\n \"detail\": \"there was a problem processing your request\"\n }\n ]\n}\n"
schemas:
LogsTtl:
properties:
days:
type: integer
description: The number of days to retain the logs. Allowed values are between 1 and 365.
minimum: 1
maximum: 365
example: 10
type:
type: string
const: time_to_live
description: The type of the object. Always equal to `time_to_live`.
ErrorResponse:
required:
- errors
properties:
errors:
type: array
items:
$ref: '#/components/schemas/Error'
Error:
required:
- status
- title
properties:
title:
type: string
description: A brief summary of the error.
examples:
- Bad Request
status:
type: string
format: string
description: The HTTP response code of the error.
examples:
- '400'
detail:
type: string
description: Optional additional detail about the error.
examples:
- The field 'name' is required
securitySchemes:
bearerAuth:
type: http
scheme: bearer