---
title: "Create Connect"
method: POST
path: "/v1/connects"
tags: ["Connects"]
---

# Create Connect

`POST /v1/connects`

Get an existing connect or create a new connect for an existing nonprofit organization.

The returned Connect can be used to integrate the client-side Chariot Connect component using the `id` property (CID) and also query for data generated from the Chariot Connect instance using the connect_id query parameter in any of the List Grants API endpoints.

<Note>
Only one Connect object can be created per organization.
If one already exists, this will return a `200 OK` status with the existing object.
</Note>

## Request body

- object
  - `organization_id` string, required — The unique identifier for the organization
  - `contact` object, required
    - `email` string, required — The email address for the nonprofit account contact
    - `phone` string — The phone number for the nonprofit account contact
    - `first_name` string — The first name of the nonprofit account contact that manages this Connect
    - `last_name` string — The last name of the nonprofit account contact that manages this Connect
  - `name` string — A human readable name of the Connect, optional.
  - `metadata` object — A map of arbitrary string keys and values to store information about the object.

## Response `200`

OK

- Connect — A Connect represents an instance of Chariot Connect for a particular nonprofit. A nonprofit organization will create Connect objects in order to integrate Chariot Connect into their websites or fundraising platforms to start accepting donations directly from Donor Advised Funds. Each nonprofit can have multiple Connect objects where each one represents a logical separation for how the organization wants to organize their sources of donations. For example, they might have 2 Connect instances, one that they use to integrate Chariot Connect directly on their website and the other that they provide to a 3rd party fundraising platform. On the client side, Chariot Connect is instantiated with the `id` of the Connect object, also called the `cid`. A connect object also contains an `apiKey`. This is useful for nonprofits to provide to fundraising platforms on their behalf to programatically integrate Chariot Connect and access resources and information created from the Connect instance through various Chariot API endpoints. More information on integrating Chariot Connect into a client-side application can be found here: https://givechariot.readme.io
  - `id` string, required — The unique identifier for this object. This is also the 'publishable' cid to use for initializing Connect for client-side integration.
  - `name` string — A human readable name for the connect, optional.
  - `apiKey` string, required — (deprecated) A secure token that can be used to make M2M API calls to read data generated by this object.
  - `active` boolean — A flag to indicate if this connect is active. If true, then this Connect can process donations and grants, otherwise this Connect cannot process grants.
  - `createdAt` string, date-time — Time when this object was created. Expressed in RFC 3339 format.
  - `updatedAt` string, date-time — Time when this object was last updated. Expressed in RFC 3339 format.
  - `createdBy` string — ID of the user who created this object.
  - `archived` boolean — A flag to indicate if this object is marked for deletion.
  - `metadata` object — A map of arbitrary string keys and values to store information about the object.

## Other responses

- `201` — Created
- `400` — The request is invalid or contains invalid parameters
- `401` — Unauthorized. The request is missing the security (OAuth2 Bearer token) requirements and the server is unable to verify the identify of the caller.
- `403` — Access denied
- `404` — Resource Not Found
- `500` — Internal Server Error

---

[API](https://skmtc.net/chariot-giving/apis/chariot-api-4.md) · [All operations](https://skmtc.net/chariot-giving/apis/chariot-api-4/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/chariot-giving/chariot-api-4/versions/c194d399d515/schema)