Connect your application to AccordFlow.

composer require robo-meister/accord-flow-api

<?php
require __DIR__ . '/vendor/autoload.php';

use AccordFlow\AccordFlowClient;
use AccordFlow\AccordFlowException;

$baseUrl = getenv('ACCORDFLOW_BASE_URL');
$token = getenv('ACCORDFLOW_TOKEN');
if (!$baseUrl || !$token) {
    throw new RuntimeException('Set the server-side AccordFlow URL and token.');
}

$client = new AccordFlowClient(
    baseUrl: $baseUrl,
    bearerToken: $token,
);

try {
    $status = $client->status();
    echo json_encode($status, JSON_THROW_ON_ERROR | JSON_PRETTY_PRINT);
} catch (AccordFlowException $error) {
    // Log the status only; responses can contain sensitive signing data.
    error_log('AccordFlow request failed; HTTP ' . $error->getStatusCode());
    exit(1);
}

The client also accepts tenantId for deployments configured to use the tenant header. Follow your deployment's authentication policy.

1. Prepare an envelope and attach the approved document.
2. Add recipients and create the signing session.
3. Review and dispatch the invitation using the configured delivery owner.
4. Read status, then retrieve the artifacts and evidence produced by the signing route.

Dispatching an invitation does not establish signer consent. The signer supplies consent in the signing interaction. Final signed-document retrieval and evidence exports are separate operations; available artifacts depend on the runtime and provider.