incomingEvents.list

The Team's incoming events (url masked); event keeps one event name.

Prerequisites

A Curviate API key, passed as apiKey when you construct the client. Quickstart shows how to create one.

Signature

list(params?: IncomingEventListParams): Pageable<IncomingEventPage>

Example

import { Curviate } from "@curviate/sdk";
 
const curviate = new Curviate({
  apiKey: "cvt_live_...",
  baseUrl: "https://api.curviate.com",
});
 
const page = await curviate.incomingEvents.list();
for (const item of page.items ?? []) {
  console.log(item.id);
}
// `page.cursor` is the opaque cursor for the next page (null when exhausted).

Parameters

Name	Type	Required	Description
`event`	`string`	No	Only incoming events for this event name.
`cursor`	`string`	No	Opaque pagination cursor from a previous response; pass it back verbatim
`limit`	`number`	No	Max items per page (1-100, default 50)

Returns

Resolves to Pageable<IncomingEventPage>. Top-level fields: object, items, cursor.

Error codes

Code	What it means, and what to do
`UNAUTHORIZED`	The API key is missing, malformed, or revoked. Check the key you passed to the client.
`INVALID_REQUEST`	A parameter failed validation. The message names the offending field; fix the request rather than retrying it.
`RATE_LIMIT_ACCOUNT`	This account's own quota is exhausted. Wait for the window in the `Retry-After` header, then retry.
`RATE_LIMIT_TENANT`	The tenant-wide quota is exhausted across all accounts. Slow the whole workload, not just this call.
`PLATFORM_RATE_LIMIT`	LinkedIn is throttling this account. Back off well beyond the hinted delay; sustained pressure risks the account.
`PLATFORM_ERROR`	An upstream failure, usually transient: retry once with backoff before treating it as a real error. Check the response first, though. When it carries `retry_likely_to_succeed: false` and `retry_hint: {kind: "never"}`, retrying cannot help and backing off only delays the real answer.
`TEAM_REQUIRED`	See the error codes reference.

Every code above is a stable CurviateError.code you can branch on. The full list, the response envelope, and retry semantics are in the Error codes reference.

Next steps

incomingEvents.get: One incoming event, url masked; shape is the captured sample as paths and types only.
incomingEvents.arrivals: The last 20 posts and what each did (outcome; accept values you do not know), kept 30 days.
incomingEvents.capture: The next post replaces the sample (paths and types only) and, when switched on, still moves Enrollments.
SDK Quick Start: installation, the client, account scoping, and pagination.