Ardent AfricaDocs
Developers

Developer overview

The Ardent Africa public API and embeddable widgets, at a glance.

The Ardent Africa public API is a small, read-only, versioned API for building on top of the platform. It exposes campaigns, petitions, marketplace listings, events, blog posts, public profiles, and platform statistics, all as safe projections. There are no write operations and no access to private, donor, or attendee data.

Base URL:

https://api.ardent.africa/public/v1

What you can do

  • List and read active campaigns.
  • List and read petitions, with aggregate signature stats.
  • List and read active marketplace listings and categories.
  • List and read published events, with public ticket-tier details.
  • List and read published blog posts.
  • List and read public durbars (live audio rooms), including who spoke in them.
  • Read the machine transcript of a recorded durbar.
  • Read public supporter profiles.
  • Read platform-level statistics.
  • Embed campaign, petition, event, poll, durbar and other widgets on your own site.
  • Use the official SDKs (JavaScript/TypeScript and PHP) or the Zapier app instead of calling the API by hand.

What you cannot do

By design, the public API never exposes donations, donor or signer personal data, payments, admin functions, or any write operation. If you need those, you are looking for a private integration, which this API does not provide.

You cannot join a durbar, and no key will ever let you. This page used to say Durbar had no public API at all, on the grounds that joining a room needs a short-lived token only our own clients are issued. Reading was never the problem, and reading now ships: see Durbars. Joining still is. A token is scoped to a room, an identity and a permission set, and an API key has no actor, no trust level, no block relationships and nobody to show a recording consent notice to. Reading about a public room is a public act; entering one is not.

You cannot see who is listening to anything. Speakers are named on the API because they talked in public into a recording that is itself public and indexed. Listeners are only ever a number, and only once a room has ended. Raised hands are not readable by this surface at the database level, because knowing that somebody asked to speak in a known room identifies them.

Quick start

# No key needed to try it (low rate limit applies)
curl https://api.ardent.africa/public/v1/campaigns?limit=5

# With a key for higher limits
curl -H "x-api-key: <YOUR_API_KEY>" \
  https://api.ardent.africa/public/v1/campaigns?limit=5

Next: authentication, rate limits, the full endpoint reference, the machine-readable OpenAPI spec for codegen, the official SDKs, and Zapier automation.

Last updated: 24 August 2026

On this page