Submit.com API and Integrations for Application and Programme Management
Connect Submit.com grant management software, and Submit.com scholarship, awards and programme software, to the systems your organisation already runs. The Submit.com application programming interface (API) securely shares forms, applications, scores, decisions, payments and users with your customer relationship management (CRM) system, finance tools, data warehouse and automation workflows, without changing how your teams work today.
What the Submit.com API Supports
Submit.com is designed to fit into complex technology stacks securely, reliably and at scale.
- A representational state transfer (REST) API with predictable, resource-based endpoints
- JavaScript Object Notation (JSON) responses with standard Hypertext Transfer Protocol (HTTP) methods and status codes
- Access tokens issued from client credentials, with permission-based access
- Batch export for high‑volume programs
- Webhooks for event-driven updates
API highlights
Easy to navigate
Endpoints are organised around everyday objects, i.e. users, forms, applications, answers and payments. It’s simple to find what you need.
Clear, Consistent data
The API replies with clean, predictable JSON, making it straightforward to use in any modern tool or script.
Built for Large Datasets
Pull results a page at a time (you choose the page size) so your imports and reports stay fast even at scale.
Only The Details You Want
Ask for extra context (like application answers or tags) to be included with your results in one go – perfect for building richer views.
Security First
Uses access tokens and requires HTTPS for every call, keeping your programmes and applicants protected.
Helpful Error Messages
If something goes wrong, you’ll get human-readable status messages so you can fix issues quickly.
Integration scenarios for CRM, finance, student, HR and reporting systems
Most integrations fall into one of six patterns. Each one uses the Submit.com API, a low-code tool connected to it, or a native integration where one exists.
CRM and finance
Send applicant records, statuses, decisions and outcomes to a customer relationship management system, so programme activity sits with the rest of the relationship. Payment records can feed finance systems, and fees taken through Stripe reconcile from Stripe statements.
Method
API and webhooks; native Stripe payments
Student information systems
Pass scholarship applicant and award records to a student information system, so finance and student services work from the same awards list as the scholarship committee.
Method
API
HR information and applicant tracking systems
Move candidate records, statuses and files between Submit.com and a human resources information system (HRIS) or applicant tracking system (ATS), so talent programme data is not entered twice.
Method
API
Data warehouses and business intelligence
Load submissions, answers, scores, tags and decisions into a data warehouse or business intelligence (BI) tool for dashboards, accreditation evidence and board reporting.
Method
Paginated API and batch export
Low-code automation
Teams without developers can connect the API to tools such as Zapier, Make, Power Automate or Google Apps Script to automate routine tasks, such as adding a row to a spreadsheet when an application is submitted.
Method
API through a low-code tool
Marketing and communications
Start an email journey in a marketing tool when an application changes status or moves to a new round, alongside the emails Submit.com already sends.
Method
Webhooks or a low-code tool
What connects, how, and what is documented
This table separates native integrations, which work without development, from connections built on the API or a low-code tool. The evidence column says what is published today, so your IT team knows what to confirm during evaluation.
| System category | Data exchanged | Integration method | Evidence status |
|---|---|---|---|
| Payments | Entry fees, application fees and payment records | Native payment question connected to your own Stripe account | Native. Documented in the Submit.com help centre |
| Sign-in | User identity for applicants, reviewers and staff | Native sign-in with Google, Microsoft, LinkedIn or Facebook; Security Assertion Markup Language (SAML) single sign-on for enterprise customers | Native for social sign-in. SAML arranged with the Submit.com security team |
| CRM | Applicant records, statuses, decisions and outcomes | API and webhooks, or a low-code tool | API capability. No named CRM connector published |
| Finance | Payment records and funding decisions | API, or reconciliation from Stripe statements | API capability. Stripe reconciliation in use at Cork City Council |
| Student information systems | Applicant and award records | API | API capability. No named connector published |
| HRIS and ATS | Candidate records, statuses and files | API | API capability. No named connector published |
| Data warehouse and BI | Submissions, answers, scores, tags and decisions | Paginated API and batch export; comma-separated values (CSV) and Excel downloads from reports | API capability. Report exports documented in the help centre |
| Marketing and email tools | Statuses and communications events | Webhooks or a low-code tool | API capability. Ask for the current list of webhook events |
| Low-code automation | Any object the API exposes | Zapier, Make, Power Automate or Google Apps Script connected to the API | Supported pairing. Confirm whether a ready-made app listing exists for your tool |
| File storage | Files and attachments with their metadata | API | API capability |
On smaller screens, scroll the table sideways to see every column.
What you can sync
Use the Submit.com API to connect Submit.com with your other systems and automate data flows across the full programme lifecycle. These are the objects an integration can read and exchange.
People
Applicants, nominees, candidates and team users
Programme structure
Programmes, rounds, panels and reviewer assignments
Forms and content
Forms, questions, answers, files and metadata
Progress and outcomes
Application statuses, tags, scores and decisions
Communications
Confirmation, reminder and outcome events
Authentication, permissions and webhooks
IT and security teams usually ask three questions about an API: how callers prove who they are, what they can reach, and how other systems hear about changes. This is how a Submit.com integration answers each one.
Authenticate
Your integration uses the client credentials from your Submit.com admin dashboard to request an access token, then sends that token with each call. Every request uses HTTPS, so data is encrypted in transit.
Reach only what is permitted
Access is permission-based, so an integration only reaches the data it has been granted. Administrators can rotate tokens at any time and restrict who can generate them.
Stay in sync with webhooks
Webhooks notify your systems when something changes in Submit.com, such as a status update, so connected tools stay current without constantly checking for changes.
API access is separate from user sign-in. Applicants, reviewers and staff can sign in with Google, Microsoft, LinkedIn or Facebook accounts, and enterprise customers can arrange SAML single sign-on with the Submit.com security team. Multi-factor authentication, audit trails and data retention are covered on the Submit.com security and compliance page.
High-volume exports and data warehousing
Large programmes generate a lot of records. The Submit.com API is designed so that pulling them stays predictable.
Paging you control
Results come back a page at a time, and you choose the page size, so an import of tens of thousands of answers runs in manageable batches rather than one large request.
Related data in one call
Ask for related details, such as application answers or tags, to be included with your results, rather than making a separate call for each record.
Batch export
Batch export suits overnight loads into a data warehouse, where the whole dataset for a programme is refreshed on a schedule.
When you do not need the API
For one-off analysis, the form summary, scores and applications reports download as CSV files, and permitted users can download the summary as an Excel file. See Submit.com reporting and data extraction.
Getting Started
Step 1
In your Submit.com admin dashboard, note your client credentials.
Step 2
Request an access token (a secure pass) from the API
Step 3
Use that token to fetch the objects you need users, forms, applications, answers, tags, or payments and plug them into your workflow.
Integration examples by programme type
How integrations are typically used with each type of programme. One is a published customer example; the others describe common set-ups and are labelled as such.
Customer example
Grants: payments into finance
Cork City Council takes parking permit and other fees through the native Stripe integration. Finance staff who used to enter each payment into the council's financial systems by hand now reconcile from Stripe statements.
Read the Cork City Council story | Submit.com grant management software
Typical set-up
Scholarships: awards into the student system
A university sends scholarship award decisions from Submit.com to its student information system through the API, so student finance sees the same list the committee approved.
Typical set-up
Awards: entrants into the CRM
An awards organiser passes entrant and shortlist records to its CRM, and a webhook starts a marketing email sequence for shortlisted entrants.
Typical set-up
Innovation: applicants into the pipeline
An enterprise or innovation programme sends successful applicants to the CRM it uses to track supported companies after the programme ends.
Typical set-up
Talent: candidates into HR systems
A talent or development programme passes selected candidates and their documents to the organisation's HRIS or ATS, so records are not keyed in twice.