Association Open API Integration Guide

Problem Solved

The Association Open API guide fits conversational bots that translate user requests like 'create a declaration form,' 'bind this form to a questionnaire,' 'push an article,' or 'review to-dos' into stable HTTP calls. Its focus is not generic API wrapping, but a working integration contract for forms, questionnaires, project declarations, articles, and process to-dos.

How It Works

• Forms: Render the proposed addForm structure for user confirmation first. On success, take formId from data; if the form name already exists, use the existing formId from errmsg rather than renaming and retrying.
• Questionnaires / declarations: Questionnaire binding needs id + formId; declaration binding needs decTitle + formId. Do not mix the two, and formId must come from the form API.
• Articles: Fetch categories first, then call pushArticle with complete content. Use updateArticle with the article id returned by a successful push.
• Process to-dos: Use applySubject for short titles and formAnswer / extra for details; audit is irreversible and requires explicit confirmation.
  Treat errno === 0 as success and surface errmsg on failure.

Boundaries

Best for bots with conversational context. Avoid echoing full appKey values, keep scraping and document parsing within authorization, and do not approve by default.