Go Rallyup RallyUp REST API

Name: RallyUp REST API
Brand: RallyUp REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsBilling Subscriptionsbearer18 EndpointsREST

For Agents

Pull RallyUp fundraising data including donations, auction bids, raffle winners, and live-stream status. Useful for agents that reconcile campaign performance or trigger donor follow-ups.

Install Jentic One Beta

Connect the RallyUp REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RallyUp REST 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.

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 RallyUp REST API.

List active and past fundraising campaigns with their identifiers and metadata

Retrieve donation and recurring donation records for accounting reconciliation

Fetch auction bid history and confirmed auction winners after a campaign closes

GET STARTED

Start building with RallyUp REST API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for RallyUp REST API, keeping it validated and agent-ready. The RallyUp REST API exposes campaign, donation, auction, raffle, sweepstakes, and live-stream data from the RallyUp fundraising platform. It supports two integration patterns: organisations syncing their fundraising data with external CRMs and analytics tools, and partners embedding RallyUp campaign actions inside their own products. Endpoints cover campaign listings, transaction items, recurring donations, auction bids, raffle and sweepstakes winners, participants, teams, and organiser messaging.

Use Cases

Patterns agents use RallyUp REST API for, with concrete tasks.

★ Donor Reconciliation

Pull RallyUp donation and recurring donation records into an accounting system to reconcile campaign income with bank deposits. The API exposes transaction items at /v3/api/transactionItems and recurring donations at /v3/api/recurringDonations, so finance teams can match each donation to a deposit batch without exporting CSVs from the RallyUp dashboard.

Fetch all donations for campaign ID 12345 since 2026-01-01 and produce a CSV grouped by payment method.

Auction Winner Fulfilment

Retrieve auction bids and confirmed winners after a fundraising auction closes so a fulfilment agent can email each winner with payment and shipping instructions. The /v3/api/auctionBids and /v2/api/auctionWinners endpoints return the bidder identity, item, and winning amount for each lot.

Pull all auction winners for campaign 7788 and send each one a personalised payment-link email.

Live-Stream Engagement Monitoring

Track the status of a live fundraising broadcast and the campaign updates posted during it. The /v3/api/liveStreamStatus and /v3/api/campaignUpdates endpoints let an operations dashboard surface stream uptime, viewer-facing announcements, and donation pacing in near real time.

Poll live-stream status every 60 seconds for campaign 9001 and alert Slack if the stream goes offline.

AI Agent Donor Engagement

An AI agent uses Jentic to call the RallyUp REST API on behalf of a development team. The agent searches for the operation that lists donations, loads its input schema, and pulls fresh donor records to draft personalised thank-you messages. Jentic isolates the bearer token from the agent context.

Search Jentic for 'list rallyup donations', load the schema, fetch donations from the last 24 hours, and draft a thank-you email per donor.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for rallyup rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/token

Exchange credentials for a bearer token

GET

/v2/api/listcampaigns

List all campaigns on the account

GET

/v2/api/listdonations

List donations for a campaign

GET

/v3/api/recurringDonations

List recurring donation records

GET

/v3/api/auctionBids

Retrieve auction bid history

GET

/v2/api/auctionWinners

Get confirmed auction winners

GET

/v3/api/raffleWinners

Fetch raffle winners for a campaign

GET

/v3/api/liveStreamStatus

Check campaign live-stream status

POST

/v1/token

Exchange credentials for a bearer token

GET

/v2/api/listcampaigns

List all campaigns on the account

GET

/v2/api/listdonations

List donations for a campaign

GET

/v3/api/recurringDonations

List recurring donation records

GET

/v3/api/auctionBids

Retrieve auction bid history

Why Jentic?

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

Credential isolation

Your RallyUp bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list RallyUp donations' or 'read recurring donations', and Jentic returns the matching RallyUp operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using RallyUp REST API through Jentic.

Why is there no official OpenAPI spec for RallyUp REST API?

RallyUp does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call RallyUp REST API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the RallyUp REST API use?

The RallyUp REST API uses HTTP bearer token authentication. Tokens are obtained via POST /v1/token. When called through Jentic, the bearer token is stored encrypted in your Jentic One instance and never exposed to the agent context.

Can I retrieve recurring donations with the RallyUp REST API?

Yes. Call GET /v3/api/recurringDonations to list recurring donation records. The endpoint returns donation amount, frequency, and donor identifiers so you can match recurring revenue against scheduled charges.

What are the rate limits for the RallyUp REST API?

The OpenAPI spec does not declare numeric rate limits. RallyUp publishes per-account guidance in its developer documentation; in practice, paginate list endpoints and back off on HTTP 429 responses.

How do I list a RallyUp campaign's donations through Jentic?

Run a Jentic search for 'list rallyup donations', load the schema for GET /v2/api/listdonations, then execute it with the campaign ID. Install with pip install jentic and call the search, load, and execute methods in sequence.

Does the RallyUp REST API support live-stream status checks?

Yes. GET /v3/api/liveStreamStatus returns the current status of a campaign's live broadcast. Poll this endpoint to drive operations dashboards or trigger alerts when a stream drops.

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

Yes. Jentic One is self-hosted, so you set the rules that decide which RallyUp operations and credentials your agent may use. Because the RallyUp REST API exposes read operations that take their filters as parameters rather than resource ids in the path, you can grant only the operations the agent needs, such as GET /v2/api/listcampaigns and GET /v2/api/listdonations, while withholding recurring donation or auction bid reads it should not touch. Since the API surface you allow is read-only, the agent pulls fundraising data without gaining any write ability.