canonical: https://jentic.com/apis/api2.crowd4cash.ch/crowd4cash

# Api2 Crowd4cash Ch C4C REST API

Jentic publishes the only available OpenAPI specification for Crowd4Cash, keeping it validated and agent-ready. Crowd4Cash is a Swiss crowdlending platform that connects investors with consumer, intermediary, and rental loan opportunities. The API exposes loan listings, opportunity feeds, bidding, contracts, and portfolio access so that investor partners can place bids, manage contracts, and pull portfolio state programmatically. Use it to integrate Swiss crowdlending into a partner platform without building bespoke screen scrapers.

## For AI agents

Browse Swiss crowdlending opportunities, place bids, manage signed contracts, and read portfolio state on Crowd4Cash through an 18-endpoint REST API.

## Scope

Does not handle KYC onboarding, fiat funding rails, or tax reporting - use for browsing loan opportunities, placing bids, and reading contracts and portfolio state only.

## Capabilities

- Authenticate against Crowd4Cash to obtain a bearer credential for subsequent calls
- List active loan opportunities so an investor agent can rank them before placing bids
- Place a bid on a specific loan opportunity at a chosen amount
- Retrieve a signed contract by loanId for record keeping or downstream reporting
- List bids placed by the investor across the platform for review
- Read the current portfolio state to compute exposure or yield metrics

## Use cases

### Automated Bidding on Loan Opportunities

An investor wants to bid on every loan that fits their risk criteria as soon as it opens. An agent polls /Opportunities, filters by interest rate and term, and posts /Bid for each match. Manual bidding inside the Crowd4Cash UI becomes a continuous policy-driven process.

Example prompt: GET /Opportunities, filter by yield criteria, then POST /Bid with the chosen amount on each qualifying loan

### Portfolio Reporting for Investors

An investor with many loans needs a current view of exposure and yield. An agent calls /Portfolio for the latest position, /Bids for in-flight commitments, and /Contracts for signed agreements. The result is a single dashboard line per investor, rebuilt automatically each morning.

Example prompt: Pull /Portfolio, /Bids, and /Contracts, then aggregate exposure and yield by loan type

### Contract Retrieval for Audit

When auditors review a loan book, they need the signed contract for every position. An agent walks the investor's contracts via `/Contracts/{loanId}` and `/Contracts/{partnerId}/{loanId}`, pulling each contract and storing it in document management. The audit pack assembles in minutes.

Example prompt: List the investor's contracts and call `/Contracts/{loanId}` for each to retrieve the full signed document

### Rental Loan Specialisation

Crowd4Cash offers rental-loan products with their own contract format. An agent reads /RentalLoan to discover available rental-loan opportunities and `/Contracts/RentalLoan/{loanId}` for the matching contract, separating rental-loan flow from consumer and intermediary loan pipelines.

Example prompt: List rental-loan opportunities and retrieve each rental-loan contract for the chosen positions

### AI Agent Investing via Jentic

An AI agent that manages investor capital uses Jentic to drive Crowd4Cash by intent. Searching for 'place a bid on a swiss loan' returns the right operation, the agent places bids and reads contracts with managed credentials, and surfaces yield back to the investor without ever exposing the API key.

Example prompt: Use Jentic to find the Crowd4Cash bidding operation, execute it with the chosen loan and amount, and read /Portfolio to confirm the bid landed

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/Authenticate` | Authenticate and obtain a bearer credential |
| GET | `/Opportunities` | List active loan opportunities |
| POST | `/Bid` | Place a bid on a loan opportunity |
| GET | `/Bids` | List bids placed by the investor |
| GET | `/Contracts/{loanId}` | Retrieve a signed contract by loanId |
| GET | `/Contracts/RentalLoan/{loanId}` | Retrieve a rental-loan contract |
| GET | `/Portfolio` | Read the investor portfolio |

## Key resources

- **Auth** — Authenticate to obtain a bearer credential
- **Opportunities** — Active loan opportunities open for bids
- **Loans and Rental Loans** — Standard, intermediary, and rental loan products
- **Bids** — Investor bid placements
- **Contracts** — Signed loan contracts including partner-specific and rental-loan formats
- **Portfolio** — Current investor portfolio position

## Why Jentic

- **Setup:** Wiring the C4C REST API by hand means calling its Authenticate step for an API key, learning the opportunity and contract resource shapes, and assembling bids yourself. Through Jentic you install once, import C4C from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** C4C takes the bid target in the request body, so scope the agent to the operations it needs, such as browsing opportunities and reading your portfolio, and leave out placing a bid unless you add it. You choose the allowed operations, so the agent only calls what you list.
- **Credential handling:** Your C4C API key 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 loan opportunities' or 'read my portfolio', and Jentic returns the matching C4C operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Stripe handles fiat payment rails that Crowd4Cash investors might use for funding the platform off-API.
- **Extensiv** — An unrelated operations platform; included as a complementary recordkeeping system in some investor backends.
- **New Relic** — Monitors uptime of the Crowd4Cash integration so missed bids surface as alerts.

## FAQ

### Why is there no official OpenAPI spec for Crowd4Cash?

Crowd Solutions AG, the operator of Crowd4Cash, does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call C4C 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 Crowd4Cash API use?

Crowd4Cash uses an API-key style bearer credential. Call POST /Authenticate to exchange your investor credentials for a bearer token, then send the token in the Authorization header on subsequent calls. Through Jentic, the credential is held in the credential vault and injected at execution time.

### Can I place a bid on a loan with the API?

Yes. POST /Bid with the loanId and bid amount places a bid on an active opportunity. List your placed bids with GET /Bids and your signed contracts with GET `/Contracts/{loanId}` once a bid converts into a position.

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

The spec does not declare numeric rate limits. Crowd4Cash enforces fair-use throttling on /Opportunities and /Bid. Build retries with backoff and avoid tight polling - read /Opportunities at most every few seconds when watching for new openings.

### How do I bid on a Crowd4Cash opportunity through Jentic?

Install the SDK with `pip install jentic`. Search Jentic for `place a bid on a crowd4cash loan`, load the schema for POST /Bid, and execute it with the loanId and amount. Jentic handles authentication so the agent never sees the raw bearer token.

### Are rental loans handled separately?

Yes. Rental loans have their own opportunity endpoint /RentalLoan and contract retrieval `/Contracts/RentalLoan/{loanId}.` Standard and intermediary loans use /Loan, /IntermediaryLoan, and `/Contracts/{loanId}.`

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

Yes. Because Jentic One is self-hosted, you decide which Crowd4Cash operations your agent may call, so you can grant read-only access such as listing opportunities with GET /Opportunities and reading positions with GET /Portfolio while leaving out POST /Bid. Since the bid target is passed in the request body, an agent cannot place a bid unless you have explicitly added that operation to its allowed set. Your own rules govern which operations and stored credentials the agent uses, so it only calls what you list.