crowd.dev API

Name: crowd.dev API API
Brand: crowd.dev API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact Managementbearer32 EndpointsREST

For Agents

Create, query, and update members, activities, organizations, tasks, notes, tags, and automations inside a crowd.dev tenant.

Connect the crowd.dev API to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 crowd.dev API API.

Create and update community members and query the full member set with POST /member/query

Log activities (commits, posts, replies) against members and organizations

Manage organization records that members are associated with, including bulk querying

Create tasks and notes against community records to drive go-to-market follow-up

GET STARTED

Start building with crowd.dev API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for crowd.dev API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for crowd.dev API, keeping it validated and agent-ready. crowd.dev is a developer-first community and go-to-market data platform that unifies member, activity, and organization data across GitHub, Discord, Slack, and other community surfaces. The API exposes 32 endpoints with consistent CRUD plus query patterns for members, activities, organizations, tasks, notes, tags, and automations. Calls are tenant-scoped via the {tenantId} path variable and authenticated with a bearer token.

Use Cases

Patterns agents use crowd.dev API API for, with concrete tasks.

★ Community Member Sync from External Sources

Maintain a unified view of community members by upserting them through POST /member and PUT /member/{id} from GitHub, Discord, and Slack ingestion pipelines. Teams use POST /member/query with filter expressions to pull members for outreach lists and to detect duplicates. The tenant-scoped base URL keeps multi-workspace deployments cleanly separated.

Create a crowd.dev member with GitHub username octocat and email octocat@example.com, then verify it appears in POST /member/query

Activity Stream Ingestion

Push every relevant community event into crowd.dev's activity stream by calling POST /activity with type, member ID, and source platform. Devrel teams use POST /activity/query to slice the stream by date, type, or member to surface trends and identify the most active contributors. Updates and deletes are available for correcting bad ingest.

Log a crowd.dev activity of type pull-request-merged for member ID m_42 with timestamp 2026-06-10T10:00:00Z

Automated Task Creation from High-Value Signals

Convert high-value community signals into follow-up tasks by calling POST /task with assignee and due-date, then querying open tasks via POST /task/query. Devrel and field-engineering teams use this to make sure no high-intent contributor gets dropped, and to keep follow-up evidence inside crowd.dev rather than a separate task tracker.

Create a crowd.dev task assigned to user u_7 with title 'Follow up on Stripe integration question' due in 3 days

AI Agent Community Insights

An AI agent surfaces a weekly summary of high-value community activity by querying crowd.dev through Jentic. The agent searches for the crowd_query_activities operation, executes against the team's vaulted bearer token, and joins the results with member and organization records. Jentic isolates the bearer token and tenant ID so the agent only ever holds a scoped capability.

Use the Jentic SDK to query crowd.dev activities for the last 7 days and group them by source platform and activity type

Key Endpoints

32 endpoints — jentic publishes the only available openapi specification for crowd.

METHOD

PATH

DESCRIPTION

POST

/member

Create a member

POST

/member/query

Query members with filters

POST

/activity

Create an activity

POST

/activity/query

Query activities with filters

POST

/organization

Create an organization

POST

/task

Create a task

POST

/automation

Create an automation

POST

/member

Create a member

POST

/member/query

Query members with filters

POST

/activity

Create an activity

POST

/activity/query

Query activities with filters

POST

/organization

Create an organization

POST

Why though Jentic?

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

Credential isolation

The crowd.dev bearer token and tenant ID are held encrypted in the Jentic vault. Agents receive a scoped execution token, and Jentic attaches the Authorization header and substitutes the tenant ID at request time so the raw credentials never enter the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'query crowd.dev members' or 'log a community activity' and Jentic returns the matching crowd.dev operation with its input schema, removing the need to read the crowd.dev docs.

Time to first call

Direct crowd.dev integration: 1-2 days to wire up bearer auth, multi-tenant base URL, and the query DSL. Through Jentic: a few hours — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Crove API

Crove generates templated documents that can be triggered from crowd.dev community signals

Use crowd.dev to detect high-value contributor signals and Crove to generate the outbound document or contract that follows.

Complementary

Cronitor API

Cronitor monitors the scheduled jobs that ingest data into crowd.dev

Pair Cronitor with crowd.dev to confirm a recurring GitHub or Discord ingestion job actually fired.

Complementary

Cron-job.org API

cron-job.org schedules recurring HTTP calls that can drive crowd.dev activity ingestion

Use cron-job.org to schedule a recurring crowd.dev /activity/query export when an agent doesn't have its own scheduler.

FAQs

Specific to using crowd.dev API API through Jentic.

Why is there no official OpenAPI spec for crowd.dev API?

crowd.dev does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call crowd.dev API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the crowd.dev API use?

The crowd.dev API uses bearer-token authentication — clients send their token as Authorization: Bearer. Through Jentic, the bearer token is held encrypted in the vault and injected at request time so the raw token never reaches the agent.

Why does the base URL include a {tenantId}?

crowd.dev is multi-tenant, so every API call is scoped to a specific tenant via the path variable. You substitute your tenant ID into https://app.crowd.dev/api/tenant/{tenantId} so a single workspace can host multiple isolated communities.

How do I query members with filters through Jentic?

Search Jentic for 'query crowd.dev members', load the operation schema for POST /member/query, and execute with a filter expression. Jentic handles bearer-token injection and tenant ID configuration.

How many endpoints does the crowd.dev API expose?

Thirty-two endpoints with a consistent CRUD-plus-query shape across members, activities, organizations, tasks, notes, tags, and automations.

Can I configure automations through the API?

Yes. POST /automation creates an automation, GET /automation/{id} retrieves one, and PUT and DELETE /automation/{id} update or remove it, so the same automations you build in the UI can be managed programmatically.