Contact Support:
Name: Engiven Support
Email: support@engiven.com
The Engiven APIs are intended to allow approved partner platforms to facilitate the offering of cryptocurrency donation and management services to their nonprofit clients.
\nEngiven’s private APIs allow you to:
\nCreate and update nonprofit organizations (Customers)
\nCreate and update designated giving funds associated with nonprofit organizations
\nInitiate cryptocurrency donations
\nGet transaction details and histories
\nTo utilize the Engiven APIs, your partner platform must be approved by Engiven and have entered into a Partner API Agreement with Engiven.
\nAs an approved partner you may request access to the Engiven Sandbox site by emailing it@engiven.com and requesting a Sandbox API Key. You will be asked to provide:
\nEngiven’s team will provide you the API Key for the Engiven Sandbox via SendSafely.
\nTo test your integration you will need to utilize testnet coins. The testnet is an alternative Bitcoin block chain to be used for testing. You can request testnet coins via any number of public faucets such as:
\nhttps://coinfaucet.eu/en/btc-testnet/
\nhttps://bitcoinfaucet.uo1.net/
\nWe recommend utilizing a faucet as a ‘donor’, and making a request for testnet coins to a faucet using the publicAddress returned from a successful POST to the endpoint https://api.sandbox.engiven.com/gifts
\nOnce you have built your implementation, you will work with the Engiven development team to review and finalize. Once you and the Engiven team agree you are ready to move forward you can request production API keys.
\nRequest your production API key by emailing it@engiven.com. You will be asked to provide:
\nEngiven’s team will provide you the API Key for the Engiven Production APIs via SendSafely.
\nIt is important for Engiven’s Platform Partners and their nonprofit customers to understand the flow of funds related to donations of cryptocurrency made via the API. All donations made via the API are received on behalf of the Partner Platform’s designated nonprofits by Engiven Foundation. Engiven Foundation operates as a project of Players Philanthropy Fund, a Maryland charitable trust recognized by the IRS as a tax-exempt public charity under Section 501(c)(3) of the Internal Revenue Code.
\nWhen your nonprofit customers’ donors make a cryptocurrency donation, they are in fact making the donation to Engiven Foundation for the benefit of your nonprofit customer. Engiven Foundation, as a fiscal sponsor then grants the resulting USD proceeds to your nonprofit customer. In this way, your nonprofit customers are allowing their donors to make cryptocurrency donations that directly benefit the intended nonprofit without that nonprofit having to actually receive or custody cryptocurrency assets.
\nProceeds from gifts made to your nonprofit customers are dispersed from the fiscal sponsor to the nonprofit customer via mailed check the first full week of the month following the month the gift(s) was made.
\nEngiven is developing a Plaid integration that will soon allow your nonprofit customers to elect to connect their local bank accounts for free, daily, automatic disbursements.
\nIn the user flow that is presented to your nonprofit customers who are opting to accept cryptocurrency donations, Engiven requires that you provide a clear description of the flow of funds and the role that the fiscal sponsor (Engiven Foundation) plays; and, that your nonprofit customer acknowledges that they understand that description.
\nSample acknowledgement language to be presented to your nonprofit customer is below. You may choose to modify or add to this language.
\nThe cryptocurrency giving option utilizes a fiscal sponsor, Engiven Foundation, which operates as a project of Players Philanthropy Fund, a Maryland charitable trust recognized by IRS as a tax-exempt public charity under Section 501(c)(3) of the Internal Revenue Code. Cryptocurrency gifts made by your donors will be made to Engiven Foundation, with the resulting USD proceeds designated for grant to your nonprofit organization. In very rare situations, Engiven Foundation may not be able to grant the donation proceeds to your organization when, for example, your organization falls out of compliance with a federal or state regulatory authority. If Engiven Foundation cannot grant the donation to your organization, Engiven Foundation may, after consultation with [API Platform Partner] return the proceeds of the donation to the donor, contact the donor for an alternate recommendation, or select an alternate recipient nonprofit. Proceeds from cryptocurrency gifts made to your organization are dispersed from Engiven Foundation to your organization via mailed check the first full week of the month immediately following the month the gift(s) was made.
\nIn the donation experience flow, you are required to present the below language within the donation flow prior to presenting the donor with the giving address and QR code received via response from a POST to the endpoint https://api.sandbox.engiven.com/gifts :
\n[Nonprofit Customer Name] is a nonprofit corporation receiving cryptocurrency donations through a fiscal sponsorship with the Engiven Foundation, a project of Players Philanthropy Fund, a Maryland charitable trust recognized by IRS as a tax-exempt public charity under Section 501(c)(3) of the Internal Revenue Code (Federal Tax ID: 27-6601178). Contributions to the Engiven Foundation are tax-deductible to the fullest extent of the law.
\nIncluded in the contribution receipt delivered to the donor, you are required to include the below language:
\nYour contribution has been received on behalf of [Nonprofit Customer Name] by Engiven Foundation.
\nEngiven Foundation operates as a project of Players Philanthropy Fund, a Maryland charitable trust recognized by the IRS as a tax-exempt public charity under Section 501(c)(3) of the Internal Revenue Code (Federal Tax ID: 27-6601178). Contributions to Engiven Foundation are tax-deductible to the fullest extent of the law.
\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Engiven API Overview","slug":"engiven-api-overview"},{"content":"API Utilization Process","slug":"api-utilization-process"},{"content":"Understanding Flow of Funds and the role of the Fiscal Sponsor","slug":"understanding-flow-of-funds-and-the-role-of-the-fiscal-sponsor"},{"content":"Disbursement of Funds","slug":"disbursement-of-funds"},{"content":"Disclosures to Nonprofit Organizations","slug":"disclosures-to-nonprofit-organizations"},{"content":"Required Donor Facing Language","slug":"required-donor-facing-language"}],"owner":"19392324","collectionId":"f2357e7c-e34b-4172-879e-d8f715f4a498","publishedId":"2s8YeoPDbc","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"EF5B25"},"publishDate":"2022-11-11T02:23:18.000Z"},"item":[{"name":"Customers","item":[{"name":"https://api.sandbox.engiven.com/customers","id":"9c8819b5-a85c-4c5f-bfa7-59236ca0ed05","request":{"method":"GET","header":[{"key":"Accept","value":"application/json"}],"url":"https://api.sandbox.engiven.com/customers?EIN=12-3456789&fictitiousBusinessName=Test Organization&limit=10&offset=0","description":"List Customer accounts
\n","auth":{"type":"apikey","apikey":{"key":"The EIN of the organization
\n","type":"text/plain"},"key":"EIN","value":"12-3456789"},{"description":{"content":"The name of the organization
\n","type":"text/plain"},"key":"fictitiousBusinessName","value":"Test Organization"},{"description":{"content":"A limit on the number of objects to be returned, between 1 and 100. Defaults to '25'
\n","type":"text/plain"},"key":"limit","value":"10"},{"description":{"content":"The offset from the first result. Defaults to '0'
\n","type":"text/plain"},"key":"offset","value":"0"}],"variable":[]}},"response":[{"id":"c5680c93-f111-4d2d-bade-d0ddeb1aa8f1","name":"List of created customers","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Create a Customer account
\nGet Customer account information
\n","auth":{"type":"apikey","apikey":{"key":"One of 'true' or 'false'. If 'true', will include an array of Funds belonging to the Customer. Defaults to 'false'
\n","type":"text/plain"},"key":"includeFunds","value":"true"}],"variable":[{"id":"f76da991-8ff3-4676-8715-8f8ec2d0c6a5","description":{"content":"(Required) The id of the Customer
\n","type":"text/plain"},"type":"any","value":"d55b664b-c24d-4461-be3d-6545a362d632","key":"id"}]}},"response":[{"id":"616a9ade-2e06-4ad5-9ac8-70baab2a4e97","name":"The Customer information","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Update Customer account information
\n(Required) The id of the Customer
\n","type":"text/plain"},"type":"any","value":"d55b664b-c24d-4461-be3d-6545a362d632","key":"id"}]}},"response":[{"id":"5b212ce7-707c-41c4-a363-9c8d0c01ad68","name":"The updated customer","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Add or update a logo for the Customer
\n(Required) The id of the Customer
\n","type":"text/plain"},"type":"any","value":"d55b664b-c24d-4461-be3d-6545a362d632","key":"id"}]}},"response":[{"id":"78f4d1c7-8cfa-4156-9ee0-9c1aad18fdc7","name":"OK","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Remove the logo from a Customer account
\n","auth":{"type":"apikey","apikey":{"key":"(Required) The id of the Customer
\n","type":"text/plain"},"type":"any","value":"d55b664b-c24d-4461-be3d-6545a362d632","key":"id"}]}},"response":[{"id":"0610776d-a23a-41c7-a141-8b9095126cb3","name":"OK","originalRequest":{"method":"DELETE","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Customers are nonprofit organizations that will be using the Engiven system to receive cryptocurrency
\n","_postman_id":"931bb1e1-ef80-46fe-84ae-842aa159f2b4","auth":{"type":"apikey","apikey":{"key":"List Funds under a Customer account
\n","auth":{"type":"apikey","apikey":{"key":"(Required) The id of the Customer the Funds belong to
\n","type":"text/plain"},"key":"customerId","value":"d55b664b-c24d-4461-be3d-6545a362d632"},{"description":{"content":"The status of the Fund. One of 'archived' or 'active'. Defaults to 'active'
\n","type":"text/plain"},"key":"status","value":"active"}],"variable":[]}},"response":[{"id":"bf6eb537-c171-4449-995f-ca6923ec7bb5","name":"List of a Customer's Funds","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Create a Fund for a Customer account
\nGet Fund information
\n","auth":{"type":"apikey","apikey":{"key":"(Required)
\n","type":"text/plain"},"type":"any","value":"b6f88cba-3d96-4031-b969-bc754130aaeb","key":"id"}]}},"response":[{"id":"ceb262e6-6b89-4580-a298-d8793179e417","name":"View a Customer's Fund","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Update Fund information
\n(Required)
\n","type":"text/plain"},"type":"any","value":"b6f88cba-3d96-4031-b969-bc754130aaeb","key":"id"}]}},"response":[{"id":"858d3303-75d3-4a4a-95c0-af3578ceefd1","name":"The updated Fund","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"List Gifts according to a filter
\n","auth":{"type":"apikey","apikey":{"key":"The id of the Customer
\n","type":"text/plain"},"key":"customerId","value":"d55b664b-c24d-4461-be3d-6545a362d632"},{"disabled":true,"description":{"content":"The id of the Fund the Gift belongs to
\n","type":"text/plain"},"key":"fundId","value":"b6f88cba-3d96-4031-b969-bc754130aaeb"},{"disabled":true,"description":{"content":"A custom ID (eg. your system’s unique ID) that was used to identify Donors when the gift was created
\n","type":"text/plain"},"key":"customDonorId","value":"donor_111"},{"disabled":true,"description":{"content":"A custom id (eg. your system's unique id) that was used to identify a particular promised (pledged) Gift
\n","type":"text/plain"},"key":"customPaymentId","value":"payment_111"},{"disabled":true,"description":{"content":"The transaction hash of the Gift.
\n","type":"text/plain"},"key":"transactionHash","value":"0x1111111111111111111111111111111111111111"},{"disabled":true,"description":{"content":"The status of the Gift. One of 'promised', 'expired', 'confirmed', or 'all'. Defaults to 'confirmed'
\n","type":"text/plain"},"key":"transactionStatus","value":"confirmed"},{"disabled":true,"description":{"content":"The start date for listing Gifts. Uses the date when the Gift was confirmed or created, as applicable. ISO 8601 format 'YYYY-MM-DD'
\n","type":"text/plain"},"key":"startDate","value":"2022-01-01"},{"disabled":true,"description":{"content":"The end date for listing Gifts. Uses the date when the Gift was confirmed or created, as applicable. ISO 8601 format 'YYYY-MM-DD'
\n","type":"text/plain"},"key":"endDate","value":"2022-03-31"},{"disabled":true,"description":{"content":"A limit on the number of objects to be returned, between 1 and 100. Defaults to '25'
\n","type":"text/plain"},"key":"limit","value":"25"},{"disabled":true,"description":{"content":"The offset from the first result. Defaults to '0'
\n","type":"text/plain"},"key":"offset","value":"0"}],"variable":[]}},"response":[{"id":"d9b8564c-26ca-4e29-998a-4bae69d15e9f","name":"List of Gifts","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: apikey","key":"Authorization","value":"Create a promised (pledged) Gift
\nAfter the Gift is confirmed, a POST request will be sent to the URL you provided to Engiven.
\nPayload in the POST Request
\nExample
\n{\n \"eventType\": \"giftComplete\",\n \"object\": \"gift\",\n \"data\": {\n \"address\": \"0x0000000000000000000000000000000000000000\",\n \"transactionHash\": \"0x1111111111111111111111111111111111111111\",\n \"transactionStatus\": \"confirmed\",\n \"customPaymentId\": \"payment_111\"\n }\n}\n\n