Rate Limiting and Idempotency
Rate limiting is applied at the organization level (100 requests per minute per organization, per internal documentation). For high-cost operations, rule-level idempotency ensures the same rule is processed only once within a five-minute window; retries are allowed within that window if the initial request fails.
Constraints and Validation Rules
- When using data from LiveRamp Clean Room, all tables in a segment must come from the same dataset.
- When using data from a Snowflake Embedded Identity dataset, all tables in a segment must come from the same dataset.
- Conditions within a rule group cannot come from multiple tables
- Each rule group can contain only one logical operator
- Rule nesting depth cannot exceed three levels
- If an exclude operation is used, it must appear at the end of the call
- Field types and operators must be compatible
- You cannot mix different warehouse types across clean room and warehouse sources
Required Headers
All requests require these headers:
| Header | Required | Description |
|---|---|---|
Authorization | Yes | Bearer token for a LiveRamp API service account |
LR-Org-ID | Yes | The LiveRamp organization ID the request is coming from. |
Content-Type | Yes, for POST requests | application/json |
Example:
-H "Authorization: Bearer {access_token}"
-H "LR-Org-ID: {org_id}"
-H "Content-Type: application/json"Supported Operations
| Operation | Endpoint | Description |
|---|---|---|
| Create asset | POST /v1/assets | Creates a single asset from a rule definition |
| Bulk create assets | POST /v1/assets/actions/bulk-create | Creates multiple assets in one request |
| Calculate size | POST /v1/sizes/actions/calculate | Starts an asynchronous size calculation for the asset defined in the call |
| Get size result | GET /v1/sizes/{id} | Returns the status and result (if available) of a previously requested size calculation |
Error Response Format
Every non-2xx response (and every failed item in a batch response) uses the same error envelope:
| Field | Type | Description |
|---|---|---|
httpStatus | integer | The HTTP status code associated with this error |
errorCode | string | A stable, machine-readable code identifying the failure class (for example, INVALID_REQUEST) |
message | string | A human-readable explanation suitable for logs or UI |