Open API Terms of Use

Effective: April 25, 2026 | Last Updated: April 25, 2026

These terms govern the use of the Open API provided by Feedmate ("Service"). By using the Open API, you agree to be bound by these terms. For matters not covered herein, please refer to the Terms of Service.

Article 1 (Definitions)

1. "Open API" refers to the programming interface provided by the Service that allows users to access Service features from external applications.
2. "API Key" refers to a unique key issued to identify and authenticate users when using the Open API.
3. "Rate Limit" refers to the maximum number of API calls permitted within a given time period to prevent API abuse.

Article 2 (API Key Management Responsibility)

1. Users are solely responsible for the security of their issued API Keys. API Keys must be managed with the same level of care as passwords.
2. If an API Key is compromised or suspected of being compromised, the user must immediately revoke the key and issue a new one.
3. Users are responsible for all API calls made with their API Key and any resulting credit consumption, including those caused by unauthorized access due to key leakage.
4. API Keys must not be exposed in source code, public repositories, client-side code, or any other location accessible to third parties.

Article 3 (Usage Limits)

1. Rate Limit: Each API Key is allowed 10 requests per minute. Requests exceeding the Rate Limit will be rejected with an HTTP 429 (Too Many Requests) response.
2. Credit-Based Usage Limits: Each API function call consumes credits. API calls will be restricted when credits are depleted. For details on credit policies, please refer to the Payment & Subscription Terms.
3. The Service may temporarily tighten Rate Limits without prior notice to protect system stability.

Article 4 (Prohibited Activities)

Users must not engage in the following activities through the Open API:

1. Spam Publishing: Repeatedly publishing identical or similar content in violation of SNS platform policies or causing harm to other users.
2. Automated Mass Publishing: Publishing large volumes of content through automated means beyond the normal scope of Service usage, constituting Service abuse.
3. API Key Sharing and Resale: Sharing issued API Keys with third parties, or transferring or reselling them, whether for compensation or free of charge.
4. Threatening the security of the Service or causing excessive load on Service infrastructure.
5. Reverse engineering, decompiling, or attempting to extract the Service's source code.
6. Any activity that violates applicable laws, external SNS platform terms of service, or these terms.

Article 5 (Service Change Notices)

1. The Service may modify the Open API's features, endpoints, request/response formats, and other specifications.
2. For breaking changes (modifications that break backward compatibility), users will be notified at least 30 days in advance via email or in-service announcements.
3. In urgent cases such as security vulnerability fixes or legal compliance requirements, changes may be made immediately without prior notice. In such cases, post-change notification will be provided as soon as reasonably possible.
4. Non-breaking changes (modifications that maintain backward compatibility) may be applied without separate prior notice.

Article 6 (Disclaimer)

1. The Service is not liable for content publishing failures caused by API changes, outages, or policy changes of external SNS platforms (Meta, LinkedIn, etc.).
2. Some Open API features may be temporarily limited due to API changes on external SNS platforms. The Service will make reasonable efforts to address such changes within a reasonable timeframe.
3. The Service is not responsible for service disruptions caused by user-side factors, including negligent API Key management, improper API usage, or network environment issues.
4. Users bear full responsibility for the content and legality of materials published through the Open API.

Article 7 (Service Suspension)

1. If a user violates these terms, the Service may immediately revoke the API Key and restrict Open API access without prior warning.
2. Grounds for suspension include, but are not limited to:
   • Violation of prohibited activities under Article 4
   • Persistent and intentional Rate Limit violations
   • Security threats to Service infrastructure
   • Violation of the Terms of Service
3. Upon suspension, the Service will notify the user of the reason via registered email. Users may file an objection within 14 days of notification.
4. In cases of severe violations, access to the entire Service — not just the Open API — may be restricted.

Article 8 (SLA Application)

1. The Service's Service Level Agreement (SLA) applies equally to the Open API.
2. The service availability target (99.5% monthly) and credit compensation policies for incidents defined in the SLA also apply to Open API usage.
3. SLA exclusions (external platform outages, user-attributable causes, etc.) apply equally to the Open API.

Article 9 (Changes to These Terms)

1. The Service may modify these terms. Users will be notified at least 30 days in advance via email or in-service announcements before any changes take effect.
2. Updated terms will take effect after the notice period. Users who do not agree to the updated terms may discontinue their use of the Open API.

Article 10 (Miscellaneous)

1. For matters not covered in these terms, the Terms of Service and Payment & Subscription Terms shall apply.
2. Disputes related to Open API usage shall be governed by the jurisdiction and governing law provisions of the Terms of Service.

Change History