Contribly

Name: Contribly API
Brand: Contribly
Availability: InStock

✓ Official Vendor SpecSocial MediaSocial Managementoauth244 EndpointsREST

For Agents

Run an end-to-end audience contribution workflow: create assignments, accept text, photo, video and form submissions, moderate them, and export approved content via a single OAuth 2.0 password-flow API.

Install Jentic One Beta

Connect the Contribly to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Contribly, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Contribly API.

Create assignments that solicit specific photo, video, text, or form contributions from a defined audience

Accept inbound contributions through POST /contributions and attach uploaded files via POST /media

Moderate user-generated content with flag, like, and explicit moderation actions on each contribution

GET STARTED

Start building with Contribly API

Explore with Jentic

View OpenAPI Document

Contribly is a user-generated content and audience contribution platform that lets publishers, broadcasters, and community sites collect, moderate, and publish submissions from their audiences. The API exposes assignments (calls for content), contributions (submitted text, photos, video, and form responses), media uploads, tag and tagset management, moderation workflows, and export jobs that bundle approved contributions for downstream use. It also covers form-based response collection, contribution flagging and likes, subscription management, and OAuth-secured user identity lookups. Integrations typically run a contribution lifecycle of create assignment, intake media or form responses, moderate, then export.

Use Cases

Patterns agents use Contribly API for, with concrete tasks.

★ Audience Photo and Video Assignments

Newsrooms and broadcasters use Contribly to issue assignments such as 'send us your storm damage photos' and collect media submissions from the public. Each assignment is created with POST /assignments, contributions are submitted with POST /contributions and POST /media, and editors moderate inbound items before publication. The platform handles validation of artifact formats and tracks each contribution's moderation state across the editorial pipeline.

Create a new assignment titled 'Storm photos' with closing date set 7 days out, then list contributions tagged 'storm-damage' and approve those that pass moderation.

Form-Based Audience Surveys

Editorial and engagement teams publish structured forms via POST /forms and collect typed responses through POST /form-responses. This is used for tip lines, competition entries, eyewitness questionnaires, and audience polling where free-form contributions are not enough. Responses are queryable by id and can be tagged and exported alongside other contributions for unified analysis.

Create a form with three required fields (location, eyewitness account, contact email) and list every form-response submitted in the last 24 hours.

Moderation and Flagging Workflows

Community managers handle inbound flags through POST /contributions/{id}/flag and act on them via POST /contributions/{id}/moderate to approve, reject, or hide contributions. Likes are recorded through POST /contributions/{id}/like, giving downstream ranking signals. The endpoints surface enough state for an automated moderation agent to triage, escalate, and act without leaving the API.

Fetch every contribution flagged in the past hour, classify each one against community guidelines, and call POST /contributions/{id}/moderate with the appropriate action.

Exporting Approved Contributions

Once contributions are approved, teams export them in bulk for use in editorial systems, archives, or partner feeds. POST /export-summary returns a preflight count, POST /export creates the job, and GET /exports/{id} is polled until completion. This pattern is well suited to scheduled agent runs that compile daily or weekly digests of audience content.

Call POST /export-summary for last week's approved contributions, kick off POST /export if the count is above zero, then poll GET /exports/{id} every 30 seconds until status is complete.

AI Agent Integration via Jentic

AI agents discover Contribly through Jentic by searching for intents like 'collect audience submissions' or 'moderate user generated content'. Jentic returns the matching operation schema, executes the call against Contribly using a stored OAuth 2.0 password-flow token, and never exposes the credential to the agent's prompt context. This lets a content-ops agent run the full assignment-to-export lifecycle as one chained workflow.

Through Jentic, search 'moderate audience contributions', load the moderation operation schema, and execute POST /contributions/{id}/moderate for every flagged item with a model-decided action.

Key Endpoints

44 endpoints — contribly is a user-generated content and audience contribution platform that lets publishers, broadcasters, and community sites collect, moderate, and publish submissions from their audiences.

METHOD

PATH

DESCRIPTION

POST

/assignments

Create a new assignment

POST

/contributions

Submit a new contribution

POST

/media

Upload a new media file

POST

/contributions/{id}/moderate

Moderate a contribution

POST

/contributions/{id}/flag

Flag a contribution for review

POST

/forms

Create a form

POST

/export

Export approved contributions

GET

/exports/{id}

Poll an export job for completion

POST

/assignments

Create a new assignment

POST

/contributions

Submit a new contribution

POST

/media

Upload a new media file

POST

/contributions/{id}/moderate

Moderate a contribution

POST

/contributions/{id}/flag

Flag a contribution for review

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Contribly uses OAuth 2.0 password-flow tokens. Jentic stores the client credentials and refresh tokens in the encrypted MAXsystem vault and injects a scoped bearer token at execution time, so raw secrets never enter the agent's prompt or memory.

Intent-based discovery

Agents search Jentic by intent (e.g. 'moderate audience contributions' or 'export user submissions'). Jentic returns the matching Contribly operation along with its input schema, so the agent can call POST /contributions/{id}/moderate or POST /export without ever browsing the docs.

Time to first call

Direct Contribly integration: 2-4 days to wire OAuth password-flow, multipart media uploads, moderation state machine, and export polling. Through Jentic: under one hour — search the intent, load the schema, execute.

FAQs

Specific to using Contribly API through Jentic.

What authentication does the Contribly API use?

Contribly uses OAuth 2.0 with the password grant flow. Tokens are issued by the token endpoint declared in the spec and presented as a bearer token on each request. Through Jentic, the OAuth credentials are stored in the encrypted MAXsystem vault and never appear in the agent's prompt context.

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). Sign up at https://app.jentic.com/sign-up.

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.

Contribly

Connect the Contribly to your agent

Capabilities

Start building with Contribly API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs