Pledge API Authentication
How to authenticate Pledge API requests: one Bearer API key plus a connectionId. MindCloud stores your Pledge API key securely — set it once, never resend it.
Every Pledge API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Pledge account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.
Steps to authenticate
- Create a MindCloud account at app.mindcloud.co if you do not already have one.
- Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
- Create a Pledge connection in Connections. Pledge uses an API key. You generate the key in your Pledge account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
- Copy the connection’s
connectionId— you will send it on every request alongside your MindCloud API Key.
How requests are authenticated
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Pledge account that should run the action. MindCloud stores and refreshes the Pledge credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.
For example, calling List Organizations with an Pledge connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/pledge/actions/list-organizations/run" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--header "Content-Type: application/json" \
--data '{
"connectionId": "$CONNECTION_ID",
"arguments": {}
}'The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Pledge account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Set up your Pledge API key
You need a Pledge account with access to Impact Hub. Sandbox testing uses a separate sandbox account and sandbox API key.
- Sign in to Pledge Impact Hub
Create an account if you do not already have one, then open Impact Hub for your account.
Impact Hub - Open the API keys page
From Impact Hub, go to the API keys section and open your keys page.
Impact Hub → APIs → Keys - Copy your API key
Copy the API key shown in Impact Hub and paste it into the MindCloud connection field.
- Use a sandbox key for sandbox testing
If you want to test against Pledge sandbox, sign in to the sandbox Impact Hub instead and copy the sandbox API key from the API section.
Sandbox Impact Hub
Keep your key safe
Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.