Export composition entry items

Streams up to 50,000 matching rows in batches of 1,000. Tables without cursor paging export at most one batch; when more rows exist the response sets X-Widgetic-Export-Truncated: true. Rate limit 20 requests per minute.

GET /compositions/{id}/entries/{table}/export

Export composition entry items

cURL

curl --request GET \
  --url https://api.widgetic.com/v1/compositions/{id}/entries/{table}/export \
  --header 'Authorization: Bearer <token>'

200

<string>

Authorizations

Authorization · string · header · required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

X-Managed-User-Id · string<uuid>

The id Widgetic gave the managed user (POST /managed-users). Makes this call for one of your managed users, so that a mistake in your own code cannot reach another customer's work. Send this header, or the other one, never both. Left out, the call works on your whole account, as it always has. With it, the call reaches only that user's compositions and workflows: a list shows only theirs, a composition or a workflow the call makes is filed under them, and one of another user, or one that does not exist, answers 404 (the same answer, so the call cannot be used to find out what another customer has). A managed user that is not yours answers 404 with MANAGED_USER_NOT_FOUND. An empty, repeated or malformed header is 400 with MANAGED_USER_SCOPE_INVALID; an empty header is never read as no header. A call that is about the whole account, such as the list of your managed users, is refused with 403 and MANAGED_USER_SCOPE_ROUTE_NOT_AVAILABLE: send it without the header. Only your API key can send it. The header is a limit the call asks for: whoever holds the key can leave it out, so for a credential that a customer's browser holds, use an editor session. An Idempotency-Key is kept apart for each managed user.

Example:

"3f2b8c1e-7a4d-4e0b-9c55-2d1a6b7e8f90"

X-Managed-User-External-Id · string

Your own id for the managed user (its externalId), when you do not keep Widgetic's. Makes this call for one of your managed users, so that a mistake in your own code cannot reach another customer's work. Send this header, or the other one, never both. Left out, the call works on your whole account, as it always has. With it, the call reaches only that user's compositions and workflows: a list shows only theirs, a composition or a workflow the call makes is filed under them, and one of another user, or one that does not exist, answers 404 (the same answer, so the call cannot be used to find out what another customer has). A managed user that is not yours answers 404 with MANAGED_USER_NOT_FOUND. An empty, repeated or malformed header is 400 with MANAGED_USER_SCOPE_INVALID; an empty header is never read as no header. A call that is about the whole account, such as the list of your managed users, is refused with 403 and MANAGED_USER_SCOPE_ROUTE_NOT_AVAILABLE: send it without the header. Only your API key can send it. The header is a limit the call asks for: whoever holds the key can leave it out, so for a credential that a customer's browser holds, use an editor session. An Idempotency-Key is kept apart for each managed user.

Required string length: 1 - 255

Example:

"customer-1042"

Path Parameters

id · string<uuid> · required

table · string · required

Maximum string length: 63

Query Parameters

format · enum<string> · default: csv

Available options: csv, json

order · enum<string> · default: desc

desc (the default) lists the newest entry first, asc the oldest. Entries are sorted by their time, then by their id (compared as text, byte by byte) in the same direction, so the order of two entries made at the same instant is always the same; an entry with no time counts as the oldest. A table with no time column is sorted by its id. The managed-user feed sorts by time, then by composition id, table and id.

Available options: asc, desc

since · string<date-time>

Only entries made at this time or later: since is INCLUSIVE (an entry made at exactly since is returned). A date and time with an offset, such as 2026-10-01T00:00:00Z; anything else answers 400 INVALID_SINCE. An entry with no time never matches, and a table with no time column answers 400 ENTRY_TABLE_HAS_NO_TIME.

until · string<date-time>

Only entries made before this time: until is EXCLUSIVE (an entry made at exactly until is NOT returned), so since=A&until=B followed by since=B&until=C counts every entry once. Same form and same refusals as since (400 INVALID_UNTIL).

context · object

Host context filters as context[key]=value (max 5 keys, counting dotted context.key too). Use column.<name>=value for columns whose names collide with reserved parameters.

Show child attributes

filter · object

Column filters as filter[columnName]=value (same meaning as bare columnName=value or column.columnName=value; max 10 column filters counting all spellings). A plain filter=value still filters a column named filter.

Show child attributes

Response

200

text/csv

Exported CSV or JSON stream

The response is of type string.