Skip to main content
GET
Derive what one destination record type can do

Authorizations

Authorization
string
header
required

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

Query Parameters

integration_id
string<uuid>
required
record_type
string
required

Response

Successful Response

What one destination record type can actually do, fully derived.

actions
enum<string>[]
required

The write actions this record type supports, including composite upsert.

What one export cell does at the destination.

Its own vocabulary, not a copy of the integration stratum's WriteBehavior: the members and their values differ, and table_export_integration translates between the two at the seam (_WRITE_BEHAVIOR_TO_EXPORT_ACTION). Mirroring has no member here because it deletes and recreates the whole destination object, which is a whole-object concern rather than a per-row one.

Available options:
create,
update,
upsert
bulk_actions
string[]
required

Action values with a synchronous bulk write method — the ones a batched export can actually use.

can_match
boolean
required

Whether an existing record can be found by field value — the precondition for replay-safe creates. False means only blind creates are possible and the editor must say so.

identity_fields_by_action
Identity Fields By Action · object
required

Selectable match/identity fields per action value. An EMPTY list means the destination resolves identity dynamically (a database: any column), and the picker falls back to the discovered fields.

suggested_batch_size
integer | null
required

The destination's own recommended batch size, or None.

supports_bulk
boolean
required

Whether records can be written in batches.

update_modes
string[]
required

Supported write modes — replace, patch, set_once — for update/upsert.