Contribly

Can I moderate user-submitted contributions through the Contribly API?

Yes. Each contribution can be flagged via POST /contributions/{id}/flag and acted on via POST /contributions/{id}/moderate. Likes are tracked through POST /contributions/{id}/like and you can permanently remove items with DELETE /contributions/{id}, which makes it suitable for both human-in-the-loop and fully automated moderation flows.

How do I collect form responses with the Contribly API?

Create a form with POST /forms, then accept submissions with POST /form-responses. List all responses with GET /form-responses or fetch a specific one with GET /form-responses/{id}. This is the recommended path for tip lines, eyewitness questionnaires, and competition entries where you want structured fields rather than free-form contributions.

What are the rate limits for the Contribly API?

The published OpenAPI specification does not declare explicit rate limits. Treat the API as bound by standard HTTP 429 backoff and consult Contribly's onboarding documentation for the limit applied to your account tier before running bulk export or media upload jobs.

How do I export approved contributions through Jentic?

Through Jentic, search for 'export contributions', load the schema for POST /export, and execute it after calling POST /export-summary to confirm the row count. Then poll GET /exports/{id} until the job reports complete. The Jentic SDK pattern is search, load, execute via the async Python client (pip install jentic). Get started with Jentic One, the self-hosted execution layer.

Can I attach media files to contributions?

Yes. Upload the binary file with POST /media first, then reference the resulting media identifier when creating the contribution via POST /contributions. The /artifact-formats endpoint lists the formats Contribly accepts for the current account.

Can I limit what my agent is allowed to do with the Contribly API?

Yes. Because you run Jentic One yourself, your own rules decide which Contribly operations and credentials the agent may use, so you can grant read-only intake calls while withholding state-changing ones like POST /contributions/{id}/moderate or POST /contributions/{id}/flag until you explicitly add them. Since Contribly puts the contribution id in the URL path, such as /contributions/{id}/moderate, a rule can also pin the agent to acting on a single contribution rather than the whole queue. The OAuth credentials stay in your self-hosted instance and are injected only at execution time, so the agent never sees them.