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.