POST
/integrations/20240515/project
Step 1: Create Screening Project Lifecycle step 1
Step 1 of Bulk Screening: Creates a new project container. Supports up to 1,000,000 records per batch.
The id generated in the 201 response will be used in all subsequent stages of processing a Bulk Screening project.
Note: The scoreConfiguration section of the request is purely optional and not recommended for most use cases. Omitting it will have the Screening Batch use the Score Settings configured within the iWave appliation.
Headers
| Header | Value |
|---|---|
Content-Type | application/json |
Accept | application/json |
Plus Authorization:
Bearer <token> — required but absent from the collection's
requests; see finding G1.
Request body Tier A · source-verbatim
Field names and structure are authoritative. The values are generated placeholder noise — see Lesson 5 before copying any of them.
{
"name": "string",
"scoreConfiguration": {
"primaryAffinity": "DIS",
"primaryAffinityDescription": "Science",
"secondaryAffinity": "AGR",
"secondaryAffinityDescription": "Human Services - Basic/Emergency Aid",
"minimumConfidenceOfMatch": 1754.4408490954277,
"scoreWeights": {
"propensity": 2259,
"affinity": 8697,
"capacity": 4297
},
"scoreCapacityLimits": [
8372,
393
],
"recencyFrequencyMonetary": {
"weights": {
"recency": 2810,
"frequency": 3082,
"monetary": 9482
},
"recencyLimits": [
4258,
5532
],
"frequencyLimits": [
6918,
6487
],
"monetaryLimits": [
104,
4898
]
}
}
}
Saved responses Tier A · source-verbatim
Exactly as saved in the collection, including any incoherent sample values. Click to switch.
Try it
Simulated mode replays the saved examples above — no network, no credentials, works forever.
Paste your Postman mock
server URL (https://…mock.pstmn.io). Requests go through this
site's proxy, which only forwards to Postman mock hosts, strips any
Authorization header, and never logs bodies. It will not call the real
API — here's why.
Request body (editable):
Call it yourself
For the real API, run this from your own environment with your own token — this site never handles credentials.
curl -X POST \
'https://api.app.iwave.com/integrations/20240515/project' \
-H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
-H 'Accept: application/json' \
-H 'Content-Type: application/json' \
-d @request.json