Skip to main content
Use the @bijection/connectors/kintone entrypoint to declare Kintone resources.

​
Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

​
Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

​
App records

​
changes: Records changed since the last pass, with revision-conditioned updates

The following example matches configuration standard.

​
Configuration: standard

Case: kintone/records/changes/standard. Connection and resource configuration are declared by this exact case. Credential kind: kintone. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Configuration: writable

Case: kintone/records/changes/writable. Connection and resource configuration are declared by this exact case. Credential kind: kintone. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: records
Commands
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

​
Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection’s base URL is the Kintone domain; appId names the app. An API token (X-Cybozu-API-Token, an api_key header envelope) authorizes. records.changes reads the records changed since the last pass, ordered by the UPDATED_TIME field (Updated_datetime by default, updatedField otherwise) and then by $id, 100 a page, asking for each next page with (Updated_datetime > "T" or (Updated_datetime = "T" and $id > K)). It never uses offset (capped at 10,000), so a record edited during the pass moves later in the walk instead of shifting another past a page. A finished pass carries the latest UPDATED_TIME it read; the next pass starts five minutes before it, because UPDATED_TIME is minute-precise and a record saved again in the same minute must be read again. The first pass reads the whole app. Kintone answers each record’s id and revision as the members $id and $revision; the response contract renames them to record_id and revision before anything reads the body. The key is $id and the version is $revision. Each requested field is published as its received value JSON text beside recordId, revision and updatedAt. Field codes must be ASCII identifiers and cannot be record_id or revision. With governingRule, update takes { record } in Kintone’s record format (field codes to { value }) and sends PUT /k/v1/record.json with the revision the record was last read at, so a record saved by someone else since is refused rather than overwritten. Fields left out keep their values; a table sent replaces the rows it omits. A 200 confirms; 400, 403, 404 and 409 refuse. That a revision mismatch answers 409 (GAIA_CO02) comes from client libraries, not Kintone’s reference. A lost answer stays unknown: re-reading the record cannot prove this request applied it. Deletions are not observable; Kintone lists no deleted records. Built from the provider’s published API documentation; nothing here has run against Kintone or been qualified.

​
Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

​
Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.