GoFundMe Pro (formerly Classy) is a fundraising platform for nonprofits. Its API exposes campaigns, donations and transactions, supporters, fundraising pages and teams, designations, and recurring donation plans, letting organizations sync fundraising data and automate donor operations. Nexla connects to the GoFundMe Pro (Classy) v2 REST API at api.classy.org using OAuth2 client-credentials authentication.
Power end-to-end data operations for your GoFundMe Pro API with Nexla. Our bi-directional GoFundMe Pro connector is purpose-built for GoFundMe Pro, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to GoFundMe Pro or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your GoFundMe Pro workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a GoFundMe Pro credential, you need a GoFundMe Pro (Classy) API application to obtain a Client ID and Client Secret. The API uses the OAuth2 client-credentials (2-legged) flow: Nexla exchanges these credentials for an access token at https://api.classy.org/oauth2/auth and uses that token to call the v2 API at https://api.classy.org.
To create an application and obtain your credentials, follow these steps:
Sign in to your GoFundMe Pro account and open the Apps and Extensions page from the main menu.
Click the GoFundMe Pro API option to open the API section.
Click to create a new app, then enter an Application Name that is easy to identify (for example, "Nexla Integration") and a Redirect URI (for example, the address of your main website).
Select the Terms of Service checkbox, then click Create App.
Open Your Applications, locate the app you created, and click Edit to view and copy the Client ID and Client Secret.
Store both values securely. The Client Secret is sensitive and should be kept confidential. You can return to your API credentials later from My Settings > GoFundMe Pro API.
You will also need your GoFundMe Pro (Classy) organization ID to configure most source and destination endpoints. The organization ID identifies your organization within the Classy platform and appears in your organization's admin URLs and API responses. For complete details on authentication, organizations, and available endpoints, see the GoFundMe Pro API Documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your GoFundMe Pro (Classy) application Client ID in the Client ID field.
Enter your GoFundMe Pro (Classy) application Client Secret in the Client Secret field. This value is sensitive and should be kept confidential.
Nexla uses these credentials with the OAuth2 client-credentials flow to obtain an access token from https://api.classy.org/oauth2/auth. If your Client Secret is compromised, edit your application in the GoFundMe Pro API settings to rotate it, then update the credential in Nexla.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the GoFundMe Pro connector tile, then select the credential that will be used to connect to the GoFundMe Pro (Classy) API, and click Next; or, create a new GoFundMe Pro credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common GoFundMe Pro (Classy) endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu, and enter any required parameters. Available endpoint templates are listed in the expandable boxes below.
[Rest API] List Campaigns
List campaigns belonging to an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Campaign
Get details of a single campaign.
Enter the Campaign ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Campaign Transactions
List donations/transactions for a campaign.
Enter the Campaign ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Organization Transactions
List all donations/transactions for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Transaction
Get details of a single transaction (donation).
Enter the Transaction ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Transaction Items
List line items within a transaction.
Enter the Transaction ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Supporters
List supporters (donors) for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Supporter
Get details of a single supporter (donor).
Enter the Supporter ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Campaign Supporters
List supporters (donors) who gave to a campaign.
Enter the Campaign ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Fundraising Pages
List fundraising pages for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Fundraising Page
Get details of a single fundraising page.
Enter the Fundraising Page ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Campaign Fundraising Pages
List fundraising pages under a campaign.
Enter the Campaign ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Fundraising Teams
List fundraising teams for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Fundraising Team
Get details of a single fundraising team.
Enter the Fundraising Team ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Campaign Fundraising Teams
List fundraising teams under a campaign.
Enter the Campaign ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Designations
List designations (funds/programs) for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Designation
Get details of a single designation.
Enter the Designation ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Recurring Donation Plans
List recurring donation plans for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Recurring Donation Plan
Get details of a single recurring donation plan.
Enter the Recurring Donation Plan ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Recurring Donation Plan Transactions
List transactions produced by a recurring donation plan.
Enter the Recurring Donation Plan ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Registrations
List event/peer-to-peer registrations for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Organization Activities
List organization activity feed entries.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Dedications
List donation dedications (tribute/memorial gifts) for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Fundraising Page Donors
List donations made to a specific fundraising page.
Enter the Fundraising Page ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] Get Current Member
Get the member profile associated with the current access token.
This endpoint requires no additional parameters; it returns data scoped to the member associated with the credential.
[Rest API] List Ticket Types
List event ticket types for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Organization Transaction Items
List transaction line items across an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
[Rest API] List Source Tracking Codes
List UTM/source-tracking codes for an organization.
Enter the Organization ID in the endpoint configuration to identify the resource this source reads from. Results are returned as JSON and paginated automatically, so Nexla fetches all available pages.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
GoFundMe Pro data sources can also be manually configured to ingest data from any valid GoFundMe Pro (Classy) v2 API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new GoFundMe Pro data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the GoFundMe Pro destination, and select the Send to Destination option from the menu. Select the GoFundMe Pro connector from the list of available destination connectors, then select the credential that will be used to connect to the GoFundMe Pro (Classy) API, and click Next; or, create a new GoFundMe Pro credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common GoFundMe Pro (Classy) endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Create Campaign Transaction
Create a new donation/transaction against a campaign.
Enter the Campaign ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Update Transaction
Update an existing transaction (e.g. status, dedications), used to mark refunds/adjustments; the API has no dedicated refund endpoint.
Enter the Transaction ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Create Supporter
Create a new supporter (donor) record for an organization.
Enter the Organization ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Update Supporter
Update an existing supporter (donor).
Enter the Supporter ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Create Fundraising Page
Create a new fundraising page under a campaign.
Enter the Campaign ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Update Fundraising Page
Update an existing fundraising page.
Enter the Fundraising Page ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Create Fundraising Team
Create a new fundraising team under a campaign.
Enter the Campaign ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Update Fundraising Team
Update an existing fundraising team.
Enter the Fundraising Team ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Update Campaign
Update an existing campaign.
Enter the Campaign ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Create Designation
Create a new designation (fund/program) for an organization.
Enter the Organization ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
Create a credit adjustment (refund-like correction) against a fundraising page's totals.
Enter the Fundraising Page ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
[Rest API] Create Campaign Credit Adjustment
Create a credit adjustment (refund-like correction) against a campaign's totals.
Enter the Campaign ID in the endpoint configuration to target the resource this destination writes to. Each record from the Nexset is sent as a JSON request body to the GoFundMe Pro (Classy) API.
GoFundMe Pro destinations can also be manually configured to send data to any valid GoFundMe Pro (Classy) v2 API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
GoFundMe Pro (Classy) API endpoints expect JSON request bodies. For update operations, include the ID of the object to be updated in the endpoint URL.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured GoFundMe Pro endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the GoFundMe Pro endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
