Business API Actions & Webhooks for WordPress – Ingestics
Outbound API Delivery
Ingestics does not just pull data in – it can also push data out. The Business API Actions feature sends data from your WordPress site to external APIs. This enables bidirectional integrations where imported content triggers actions in third-party systems like CRM platforms, marketing automation tools, or notification services.
Job Queue with Encrypted Payloads
Outbound API actions are processed through a job queue. Each job contains the request payload, destination URL, headers, and method. All job payloads are encrypted using AES-256-CBC before being stored in the database, ensuring that sensitive data – such as API keys, tokens, or user information – is never stored in plaintext.
Idempotency Keys
Every outbound request includes an idempotency key – a unique identifier that prevents duplicate sends. If a job is retried due to a transient failure, the receiving API can use the idempotency key to recognise it as a duplicate and avoid processing it twice. This is critical for payment webhooks, order confirmations, and any action where duplicate execution would cause problems.
Destination Locks
To prevent race conditions and concurrent delivery issues, Ingestics applies destination locks. When a job is being delivered to a specific endpoint, that destination is locked, preventing other jobs from sending to the same endpoint simultaneously. The lock is released when delivery completes or fails.
Exponential Backoff Retry
When an outbound request fails, Ingestics retries it using exponential backoff. The first retry happens after a short delay, and each subsequent retry waits longer. This gives the receiving service time to recover from transient failures without overwhelming it with immediate retries. The maximum number of retries and backoff multiplier are configurable.
Webhook Delivery
API actions can be configured as webhook deliveries – sending HTTP POST requests to external endpoints when specific events occur. Common use cases include notifying a CRM when a new post is imported, triggering a Zapier workflow when content is published, or sending data to a data warehouse for analytics.
Configuration
| Setting | Description | Default |
|---|---|---|
| Destination URL | The external API endpoint to deliver data to | – |
| HTTP method | POST, PUT, or PATCH for the outbound request | POST |
| Headers | Custom headers including authentication | – |
| Idempotency key | Unique key to prevent duplicate deliveries | Auto-generated |
| Max retries | Maximum number of retry attempts on failure | 5 |
| Backoff multiplier | Exponential backoff factor between retries | 2x |
| Payload encryption | AES-256-CBC encryption for stored job payloads | Enabled |
Tier Availability
| Tier | API Actions |
|---|---|
| Free | Not available |
| Lite | Not available |
| Pro | Not available |
| Business | Full access – job queue, idempotency, locks, retries, webhooks |
Frequently Asked Questions
Are outbound payloads stored encrypted?
Yes. All job payloads in the queue are encrypted using AES-256-CBC before being written to the database. The encryption key is derived from your WordPress AUTH_KEY and AUTH_SALT constants.
How does the idempotency key work?
Each outbound request gets a unique idempotency key. If the request is retried after a failure, the same key is sent again. The receiving API can use this key to detect that it is a duplicate request and skip processing, preventing double-execution of side effects.
What happens if all retries fail?
If an outbound request fails after all retry attempts are exhausted, the job is marked as failed and the error is logged. The failed job remains in the queue for manual inspection, and you can choose to retry it manually or discard it.
Start automating.
Download Ingestics free. Start fetching APIs and RSS feeds in minutes.