mCards Pipeline API

Partner Integration Reference

v1.0

Authentication

All requests require an API key as a Bearer token in the Authorization header.

Scoped Access

Each API key is scoped. A key only returns data for its permitted scopes — e.g. projects, financials.

Response Format

All endpoints return JSON with success, count, and data fields.

Base URL & Authentication

Base URL

https://app--mcards-pipeline--g7fwq7dkzr.base44.app/api/functions

Authorization Header

Authorization: Bearer YOUR_API_KEY

Error Responses

401 Unauthorized — Missing or invalid API key

403 Forbidden — API key lacks the required scope for this endpoint

Endpoints

POST

https://app--mcards-pipeline--g7fwq7dkzr.base44.app/api/functions/apiProjects

scope: projects

Returns all active projects in the pipeline with deal status, close likelihood, and key metadata.

Request Body

Field	Type	Description
status	string	Filter by status: draft \| approved \| under_review \| ai_generated \| rejected \| archived
owner_user_id	string	Filter by owner user ID
include_in_portfolio	boolean	Filter by portfolio inclusion flag

Response Fields

idnameorganization_nameorganization_idstatusscenario_typeclose_likelihoodstart_dateowner_namecurrencyinclude_in_portfolioapproved_datecreated_dateupdated_date

Example Request

curl -X POST https://app--mcards-pipeline--g7fwq7dkzr.base44.app/api/functions/apiProjects \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "value"}'

Example Response

{
  "success": true,
  "count": 2,
  "data": [
    {
      "id": "abc123",
      "...": "name, organization_name, organization_id, ..."
    }
  ]
}

mCards Pipeline API · Contact your account manager to obtain an API key