@bijection/connectors/surveymonkey entrypoint to declare SurveyMonkey 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.
Survey responses
changes: Responses bulk by start_modified_at
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:surveymonkey/responses/changes/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: surveymonkey. 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
Compiled declaration examples and configuration details are published in the connector reference. The connection names one survey (surveyId); a Bearer token with responses_read_detail authorizes.
responses.changes reads GET /v3/surveys/{id}/responses/bulk?start_modified_at=<T>&sort_by=date_modified&sort_order=ASC&per_page=25 as a keyset over date_modified. Each bound is asked one second early, since “modified after” may be exclusive, and is sent without its +00:00 offset (the spelling the /surveys filters document; for responses it is unconfirmed). Answers are published as the received pages JSON. Deleted responses are invisible, so nothing is withdrawn. Basic plans answer 402 after 25 responses. Nothing is written.
Built from the provider’s published API documentation; nothing here has run against SurveyMonkey 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.