Monetary donations
OverviewAPI setupHosted setupProduct donations
OverviewAPI setupHosted setupAdditional fieldsDiscount redemptionOutcome emailsApplications inboxOrganization validation
OverviewCompliance checksEligibility reviewAgent verificationTestingOverview
These features allow you to automate acceptance or rejection of validation checks at the point of creation. This helps you test your implementation without the verification stages requiring human intervention. By specifying certain values in certain fields, you can automatically trigger a desired event to enable your testing program. Other than these exceptions, queries are created in the same way as production queries.
Please Note ā ļø
All automatic actions will be applied after the POST action. This means that the response of the POST actions will not have the value of the specified automatic actions. They will be available at the next GET call.
Validation Request
The field responsible for calling automatic actions on validation request is name
. Create your request using the documentation as usual, and in the name
field enter one of the possible values below depending on what you are aiming to achieve.
For accepting a validation request use the below in the name
field:
ā test_accept
For rejecting a validation request select one of the following and use this in the name
field:
ā test_reject_other
ā test_reject_not_eligible
ā test_reject_incorrect_documentation
ā test_reject_not_attributable_to_registry
API example
POST - Create a Validation request Request Body
GET - Expected validation request Response
Agent Verification
The field responsible for calling automatic actions in agent verification is firstName
.
Create your request using the API reference as usual, and in the firstName
field enter one of the possible values below depending on what you are aiming to achieve.
For accepting the Agent Verification use the below in the firstName
field:
ā test_accept
For rejecting the Agent Verification use one of the below in the firstName
field:
ā test_reject_validation_request_failed
ā test_reject_user_verification_expired
ā test_reject_user_failed_percent_review
ā test_reject_reapply
ā test_reject_fake_email_used
ā test_reject_no_online_presence
ā test_reject_nonprofit_association_expired
ā test_reject_other
API example
POST - Create an Agent Verification Request Body
GET - Retrieve an Agent Verification Response
Monitoring Subscription
The field responsible for calling automatic actions on monitoring is organisationId
or validationRequestId
.
To trigger an auto accept or reject action, append one of the values below to the ID of the organisationId
or validationRequestId
field:
ā -complianceStatus:pass
ā -complianceStatus:fail
Based on your choice the response will contain the appropriate specific fields. In the example below we use the organisationId
field and we will send the pass
parameter. Using this method returns all results
with a status of clear
.
API example
POST - Create a Monitoring Subscription Request Body
GET - Retrieve a Monitoring Subscription Response
By default, all parameters for monitoring will be set to clear
when calling the pass
action. In the case of invoking the fail
action, they will have the value flag
.
To overwrite the default value for a particular parameter, add the parameter with the value at the end of the organisationId
or validationRequestId
.
List of possible parameters:
ā warning
ā sanction
ā hateSpeech
ā compliance
ā commercial
ā adverseMedia
ā controversial
Additional parameters values:
ā flag
ā clear
API example with parameters
For example, if you want to flag commercial
and adverseMedia
for an organisation you have to add -commercial:flag-adverseMedia:flag
to the end of the field.
POST - Create a Monitoring Subscription Request
GET - Retrieve a Monitoring Subscription Response
Eligibility Request
The field responsible for calling automatic actions on Eligibility is suggestedActivitySubTags
. Create your request using the documentation as usual, and in the suggestedActivitySubTags
field enter one of the possible values below depending on what you are aiming to achieve. Please note that this field takes an array.
To accept an eligibility request use the below in the suggestedActivitySubTags
field:
ā ["test_pass"]
To fail an eligibility request use the following in the suggestedActivitySubTags
field:
ā ["test_fail"]
API examples
POST - Create Eligibility Subscription Request Body
GET - Create an Eligibility Subscription Response
On this page
- Overview
- Validation Request
- API example
- POST - Create a Validation request Request Body
- GET - Expected validation request Response
- Agent Verification
- API example
- POST - Create an Agent Verification Request Body
- GET - Retrieve an Agent Verification Response
- Monitoring Subscription
- API example
- POST - Create a Monitoring Subscription Request Body
- GET - Retrieve a Monitoring Subscription Response
- List of possible parameters:
- Additional parameters values:
- API example with parameters
- POST - Create a Monitoring Subscription Request
- GET - Retrieve a Monitoring Subscription Response
- Eligibility Request
- API examples
- POST - Create Eligibility Subscription Request Body
- GET - Create an Eligibility Subscription Response