API Terms

Publishing API Terms

Effective date: August 07, 2026

These terms supplement the CryptoForumHub Terms of Service.

Access

API access is discretionary and tied to one invited Discourse user. Keys may not be shared, resold, embedded in public client code, or used to impersonate another person/company. The account holder is responsible for employees, scripts, AI agents, and n8n workflows using the key.

Destinations and limits

Automated publishing is allowed only to Topic or Category destinations explicitly granted to that credential. Topic creation requires a Category grant. API use is subject to plan defaults, individual overrides, Discourse safety settings, and moderation.

Administrators may change limits or grants, suspend a key, or require manual posting where automation threatens quality or security.

Content obligations

API users must:

• publish accurate, relevant content;
• identify official/company statements honestly;
• preserve source links and rights;
• label AI-assisted content where appropriate;
• avoid duplicate, mass-generated, keyword-stuffed, or misleading Posts;
• avoid fake user interaction or automated replies presented as independent community sentiment;
• comply with forum, marketplace, bounty, verification, and legal rules.

Credentials

A key is shown once, should be stored securely, and may be rotated. Rotation immediately revokes the old key. Expiry, suspension, plan expiry, or account moderation may block API use without blocking public forum reading.

Availability

No uptime or delivery SLA is included unless separately agreed in writing. CryptoForumHub may change endpoints with reasonable notice, and may reject content that Discourse or policy validation does not accept.

Managed Presence

Managed Presence is performed under CryptoForumHub/admin identities. It does not grant the client control over independent discussion or guarantee positive coverage, volume, traffic, ranking, or commercial outcomes.

Termination

API access may be suspended or terminated for non-payment, expired entitlement, security risk, excessive load, off-topic automation, spam, policy breach, false identity, or legal requirements.