curl --request PUT 'https://esa.acreblitz.com/api/v2/groups/work-order-42/portal-lock' \
--header "X-API-Key: $ACREBLITZ_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"account_id": "your-account",
"locked": true
}'
{
"success": true,
"provider_group_id": "work-order-42",
"account_id": "your-account",
"locked": true,
"application_event_ids": [
"019953f8-8c00-7000-8000-000000000002"
]
}
Portal and application controls
Set group portal lock
Lock or unlock all current applications in an account-scoped group
PUT
/
api
/
v2
/
groups
/
{provider_group_id}
/
portal-lock
curl --request PUT 'https://esa.acreblitz.com/api/v2/groups/work-order-42/portal-lock' \
--header "X-API-Key: $ACREBLITZ_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"account_id": "your-account",
"locked": true
}'
{
"success": true,
"provider_group_id": "work-order-42",
"account_id": "your-account",
"locked": true,
"application_event_ids": [
"019953f8-8c00-7000-8000-000000000002"
]
}
Lock or unlock all current applications in an account-scoped group.
Group scope
The operation applies to existing applications owned by your provider with this account and group. It returns their application-event references. An empty or unowned group returns 404. New applications added afterward start unlocked. Wait for bulk completion before locking a complete job, and call again after adding applications. Group unlock also clears locks set individually on those applications. Shared runoff selections follow the same field/year lock rule as an individual application lock.curl --request PUT 'https://esa.acreblitz.com/api/v2/groups/work-order-42/portal-lock' \
--header "X-API-Key: $ACREBLITZ_API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"account_id": "your-account",
"locked": true
}'
{
"success": true,
"provider_group_id": "work-order-42",
"account_id": "your-account",
"locked": true,
"application_event_ids": [
"019953f8-8c00-7000-8000-000000000002"
]
}
Errors
No applications for the supplied group/account returns404 GROUP_NOT_FOUND. Invalid or missing account, group, or lock values return 422 INVALID_REQUEST.
All routes can also return authentication, validation, rate-limit, and dependency errors. Use the error catalog and examples to choose a retry or correction. Keep X-Request-ID when present.
