WP-CLI operations
Use command-line tools to inspect and advance event imports.
Before running commands
This article is for hosting administrators. Use WP-CLI from the correct WordPress installation, as the appropriate operating-system user. Replace the example connection ID with your event's ID. Do not put the Cadmium API key in a command URL or public log.
An active license and normal validation requirements still apply to imports. Commands are not a way to bypass a held feed.
Check a connection
wp metasprout status 1
Inspect the connection and run state before queueing additional work.
Request an import
wp metasprout run 1
Use the command's help output to inspect optional flags before building automation. Confirm the resulting job reaches completion; a queued job has not necessarily finished importing.
Advance pending work
wp metasprout work
This checks pending work. A large fetch may need several worker passes. Configure a recurring runner through the host rather than assuming one invocation drains every job.
Run due WordPress cron events
wp cron event run --due-now
This is a WordPress command that processes due events, including other plugins' jobs. Have the host choose the schedule, site path, execution user and logging. Avoid duplicate runners and verify unattended completion.
Public API configuration
wp metasprout public-api 1 status --user=ADMIN
wp metasprout public-api 1 enable --user=ADMIN
wp metasprout public-api 1 disable --user=ADMIN
Replace ADMIN with an authorized administrator. Enabling the API is a separate public-exposure decision; read Public read API first.
Related: Scheduling and Troubleshooting.