Built for product teams

Integrate Apification into your product

Use the REST API, signed webhooks or embedded Cloud according to the experience your product needs.

Integration surface

One platform, three ways to connect

Start with one channel and combine the others as your workflow becomes more automated or embedded.

97API operations
154file transformations
48webhook events
3.1.0OpenAPI contract
Integration modes

Choose the experience you need to build

Each mode solves a different integration problem. They share the same Cloud resources, permissions and operational controls.

Server-to-server REST API

Manage Cloud resources, users, settings and transformation jobs from your backend.

Best forBack-office automation, SaaS synchronization and controlled batch processing.
  • Scoped API keys
  • Idempotent write operations
  • Asynchronous File Transformer jobs
Inspect the API contract

Event-driven webhooks

React to relevant platform events without polling every resource or background job.

Best forCRM updates, process orchestration, notifications and audit pipelines.
  • HMAC-signed payloads
  • Delivery history and retries
  • Transformation completion events
Explore automation

Embedded Cloud

Place the Apification workspace inside your product with a controlled, branded session.

Best forCustomer portals, reseller products and applications that need a complete file workspace.
  • Signed iframe sessions
  • Themes and effective permissions
  • JavaScript host communication
Review embedded integration
Operational architecture

A complete integration, not just an endpoint

Security, safe retries, background processing and result delivery form one observable flow.

01

Scoped credential

Grant only the read and write permissions required by the integration.

02

Idempotent request

Repeat a failed network request without repeating the business action.

03

Asynchronous job

Process long transformations outside the original HTTP request.

04

Signed event

Notify the destination with a verifiable HMAC webhook.

05

Authenticated result

Retrieve generated files without exposing internal storage paths.

Start with a real request

The contract is visible before you write the integration

Use these patterns as the starting point for API, transformation, webhook and embedded workflows.

The downloadable OpenAPI 3.1 document contains the complete request and response schemas.

Download the API contract
curl --request GET \
  --url "https://www.apification.com/api/v1/cloud/services" \
  --header "Authorization: Bearer sk-apification-..."
curl --request POST \
  --url "https://www.apification.com/api/v1/file-transformer/jobs" \
  --header "Authorization: Bearer sk-apification-..." \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: normalize-customer-file-01" \
  --data '{"operation_key":"text_normalize","source_codes":["cld_source"],"options":{"text_format":"txt"}}'
const expected = createHmac('sha256', webhookSecret)
  .update(rawRequestBody)
  .digest('hex');

if (!timingSafeEqual(expected, signature)) {
  throw new Error('Invalid webhook signature');
}
<iframe src="https://app.example.com/embed/cloud/signed-session"
        title="Apification Cloud"></iframe>

<script>
window.addEventListener('message', ({ origin, data }) => {
  if (origin !== 'https://app.example.com') return;
  if (data.type === 'apification.cloud.selected') useFile(data.file);
});
</script>
Frequently asked questions

Questions about Integrate Apification into your product

Create a dedicated API key and grant only the account, Cloud, transformation, user or webhook scopes required by that integration.

Polling is useful while developing. In production, transformation completion and failure webhooks avoid unnecessary requests and provide a clearer event trail.

Embedded sessions use signed, time-limited access. The effective theme and permissions are resolved server-side before the Cloud workspace opens.