Precheck an external action
Evaluate whether a supported external action can run and what it is expected to cost, without executing the action or charging credits.
Use precheck immediately before event-access, Visitor-access, contact-unlock, and other action-specific workflows. Inspect allowed, should_charge, credits, and reason_code to decide whether to continue, ask the user for confirmation, or explain why the action is unavailable.
Precheck is advisory and read-only: it does not reserve credits, create a task, or lock the target state. Send the same action type and identifiers to the execution endpoint promptly, and still handle state or balance changes returned by that endpoint.
Authorizations
Body
Read-only action eligibility and expected-credit evaluation request.
Action to evaluate. The listed examples are handled explicitly. Other 1–100 character strings are accepted and return allowed: false with reason_code: unsupported_action.
1 - 100"query_event_personnel"
"unlock_event_contacts"
"unlock_event_visitors"
"unlock_event_full_access"
"unlock_contact_emails"
"unlock_contact_phones"
"search_exhibitor_events"
"search_personnel_events_by_name"
"integration_status"
"integration_export_contacts"
"integration_export_exhibitors"
"others"
Response
Precheck decision envelope
Action eligibility, expected charging, reason, and action-specific detail.
Stable reason explaining the eligibility and charging decision.
ok, already_unlocked, unlock_in_progress, state_conflict, insufficient_balance, no_contacts_available, exceed_max_unlock_limit, invalid_subject, unsupported_action, not_found, forbidden, system_error