Ana içeriğe atla

Endpoint

Authentication

Requires a Personal API Access Token.

Request

Headers

Path Parameters

Request Body

The request body includes endpoint identifier and CacheSettings structure. See Update Cache Settings for detailed cache settings field descriptions.

Full JSON Body Example - Basic Cache Configuration

Full JSON Body Example - Custom Cache Key

Request Body Fields

Cache Settings Object Fields

EnumCacheKeyType (cacheKeyType)

  • QUERY_PARAMS - Use query parameters as cache key
  • CUSTOM - Use custom variables as cache key (requires variableList)

EnumCacheStorageType (cacheStorageType)

  • LOCAL - Local cache (per worker instance)
  • DISTRIBUTED - Distributed cache (shared across all workers)

EnumCacheHandlingAction (handlingAction)

  • CONTINUE - Return cached response and continue to backend (for logging/monitoring)
  • STOP - Return cached response and stop (do not call backend)

Response

Success Response (200 OK)

When deploy=true is specified:

Response Fields

Error Response (400 Bad Request)

Common Causes

  • Missing required field handlingAction
  • Invalid enum values
  • Invalid cache configuration
  • Invalid variableList when cacheKeyType=CUSTOM

Error Response (401 Unauthorized)

Error Response (404 Not Found)

or

cURL Example

Example 1: Basic Endpoint Cache Configuration

Example 2: Custom Cache Key with Variables

Example 3: Save and Deploy

Notes and Warnings

  • Endpoint-Level Override:
    • Endpoint cache settings override API Proxy-level cache settings
    • If endpoint cache is disabled, API Proxy-level cache still applies
  • handlingAction:
    • Required field
    • CONTINUE - Returns cached response but still calls backend (useful for logging/monitoring)
    • STOP - Returns cached response without calling backend (better performance)
  • Cache Key:
    • When cacheKeyType=CUSTOM, provide variableList to define cache key components
    • Variables are combined to create unique cache keys
  • Storage Type:
    • LOCAL cache is faster but not shared across workers
    • DISTRIBUTED cache is shared across all workers (recommended for multi-instance deployments)
  • TTL:
    • Cache entries expire after TTL seconds
    • Set appropriate TTL based on data freshness requirements
  • Capacity:
    • Maximum number of cache entries
    • Older entries are evicted when limit is reached (LRU eviction)
  • GET Only:
    • When cacheOnlyHttpGetRequests=true, only GET requests are cached
    • When cacheOnlyHttpGetRequests=false, all HTTP methods can be cached (use with caution)
  • Null Values:
    • When cacheNullValue=false, null/empty responses are not cached
    • When cacheNullValue=true, null/empty responses are cached (may cache error responses)
  • Endpoint Validation:
    • Endpoint must exist in the API Proxy
    • Endpoint is identified by identifierName and identifierHttpMethod combination (not by ID)
  • Deploy: When deploy=true, the API proxy is automatically deployed to the specified environments after saving

Permissions

User must have API_MANAGEMENT + MANAGE permission in the project.