canonical: https://jentic.com/apis/raisely.com/raisely

# Raisely API

Raisely is a fundraising platform for charities. The API manages campaigns, donations, profiles, users, products, orders, and subscriptions. The API exposes 22 endpoints secured with bearer authentication.

## For AI agents

Programmatically login, sign up. Covers 22 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Login
- Sign up
- Get authenticated user
- Create campaign
- List campaigns
- Update campaign

## Use cases

### E-Commerce Operations

Use the Raisely API to perform e commerce operations programmatically. The API provides 22 endpoints covering core functionality including login, sign up, get authenticated user.

Example prompt: Call POST /login to login

### Automated Authentication Management

Automate authentication operations by combining multiple Raisely API endpoints. Agents can sign up and then get authenticated user in a single workflow.

Example prompt: Call POST /signup to sign up, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Raisely API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'login', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/login` | Login |
| POST | `/signup` | Sign up |
| GET | `/authenticate` | Get authenticated user |
| POST | `/campaigns` | Create campaign |
| GET | `/campaigns` | List campaigns |
| GET | `/campaigns/{uuid}` | Get campaign |
| PATCH | `/campaigns/{uuid}` | Update campaign |
| DELETE | `/campaigns/{uuid}` | Delete campaign |

## Key resources

- **Authentication** — Operations related to Authentication
- **Campaigns** — Operations related to Campaigns
- **Donations** — Operations related to Donations
- **Orders** — Operations related to Orders
- **Products** — Operations related to Products

## Why Jentic

- **Setup:** Wiring the Raisely API by hand means learning its bearer auth and hand-coding requests across its campaigns, donations, and profiles endpoints. Through Jentic you install once, import the Raisely API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** Raisely puts the campaign uuid in the URL path (`/campaigns/{uuid}`), so a rule can pin your agent to one campaign: it can read and update that campaign and nothing else. You choose the operations it may call, so destructive ones like deleting a campaign are not included unless you add them.
- **Credential handling:** Your Raisely 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.
- **Discovery method:** Agents search Jentic by intent such as 'list fundraising campaigns' or 'create a campaign', and Jentic returns the matching Raisely operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Raisely API use?

The Raisely API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I login with the Raisely API?

Yes. Use the POST /login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Raisely API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I login through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'login'. Jentic returns the matching Raisely API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Raisely API have?

The Raisely API exposes 22 endpoints covering authentication, campaigns, donations operations.

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

Yes. Because you run Jentic One yourself, you decide which Raisely operations your agent may call, so you can allow reading and listing campaigns while excluding destructive calls like DELETE `/campaigns/{uuid}.` Since Raisely puts the campaign uuid in the URL path, a rule can pin the agent to a single campaign, letting it read and update only that campaign and nothing else. The bearer token you store is injected at execution time under those same rules, so the agent never gains access beyond what you grant.