@bijection/connectors/reckon-one entrypoint to declare Reckon One 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.
Book list
observed: Keyset walk by (lastModifiedDateTime, id) in ticks, read-only
The following example matches configurationinvoices.
Inferred record types
Inferred record types
Configuration: invoices
Case:reckon-one/resource/observed/invoices.
Connection and resource configuration are declared by this exact case.
Credential kind: reckon_one. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Configuration: customers
Case:reckon-one/resource/observed/customers.
Connection and resource configuration are declared by this exact case.
Credential kind: reckon_one. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
reckonOne.resource.observed({ resource, columns, pageSize?, lag?, every? })
reads one list of a Reckon One book through the Reckon One API v2:
GET <baseUrl>{bookId}/{resource}, answered { "list": [...] }. The binding’s
setup names the baseUrl and the bookId (GET books lists the books a user
may read).
Every book entity Reckon’s OpenAPI document lists with lastModifiedDateTime
(invoices, bills, credit notes, contacts, customers, suppliers, items, journals,
payments, receipts, purchase and sales orders, projects and others) can be
walked. Each request asks page one, perPage pageSize (100), for rows
strictly after the last (lastModifiedDateTime, id) read, ordered
lastModifiedDateTime,id:
lastModifiedDateTime gt "T" or (lastModifiedDateTime eq "T" and id gt "G").
Reckon writes the time in .NET ticks and drops trailing zeros
(2022-01-20T01:26:19.6389806Z); the walk keeps all seven digits and writes the
bound back as Reckon wrote it. id is a GUID compared by Reckon’s own ordering,
the same ordering the request sorts by. A finished pass carries the last pair
and the next re-reads from lag seconds (300) before it, deduplicating by
lastModifiedDateTime, the version.
Limits: a row with a null lastModifiedDateTime is never listed by the filter.
Amounts are JSON numbers, so columns are string, integer, number or
boolean, never exact. No deletion listing or webhook is documented, so a
deleted row stays published; no command is declared. Unconfirmed: the quoted
date-time literal (Reckon’s example quotes a date, invoicedate le "2020-03-31")
and how gt orders GUIDs.
Host: Reckon’s OpenAPI document names https://api-v2.reckonone.com, while its
help centre’s examples use https://api.reckon.com/r1/v2/ behind the API
gateway that checks the subscription key. Use the gateway address Reckon gives
with the subscription key.
Bind a reckon_one credential: an oauth_refresh envelope for
https://identity.reckon.com/connect/token (client id and secret as Basic,
scopes read write offline_access; access tokens last 180 minutes, refresh
tokens 45 days unused), with the subscription key as a private resource header
ocp-apim-subscription-key (Reckon also accepts it as the subscription-key
query parameter; a missing key is a 401). No Reckon book has been reached.
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.