relay

Custom implementation · API access

Your systems.
Your workflow.
Connected.

Turn disconnected tools into a workflow that works. Get a custom implementation built around your business, or integrate directly through an API.

Explore our servicesSee the API example

Built around your stack. Designed for your next step.

From connection to completionSystem integrationWorkflow automationCustom business logicAPI implementation

Two ways to build

The right fit for your team.

Hand over the implementation, or keep development in-house and connect through an API.

01 / Built for you

Custom implementation
as a service.

Bring your requirements. We turn them into a scoped solution that fits your existing systems and the way your team works.

  • Integration with existing tools and data
  • Workflow automation and business rules
  • Testing, deployment, and handover
  • Ongoing support scoped to your needs
See how implementation works
02 / Build with us

API access for
your own application.

Give your developers a direct integration path. Use API requests to connect capabilities to your product and keep control of the experience.

  • Documented request and response formats
  • Authentication and access requirements
  • Usage limits agreed around your workload
  • Integration guidance for your developers
Explore the request example

For developers

One request.
A connected workflow.

A clear API contract gives your team a practical starting point. Define the inputs, trigger the workflow, and use the response in your application.

Authenticate
Pass an API token from your server.
Send structured data
Submit the fields your workflow needs as JSON.
Handle the response
Track the workflow using the returned identifier.
Example requestcURL / JSON
curl -X POST \
  https://api.example.com/v1/workflows \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow": "sync_customer",
    "input": {
      "customer_id": "customer_123"
    }
  }'
Example response · 202 Accepted
{
  "id": "workflow_456",
  "status": "queued"
}

Illustrative API contract. api.example.com is a placeholder; the endpoint and schema are defined during implementation.

From brief to working software

A clear path to delivery.

Start with the outcome you need. Define the scope before implementation begins.

01 / Discover

Map the requirements.

Review your systems, data, and current workflow. Agree on the problem, success criteria, and integration boundaries.

02 / Implement

Build the connections.

Develop the integration and business logic. Validate the solution against your agreed use cases and real operating needs.

03 / Deliver

Launch with a handover.

Deploy the agreed solution, document how it works, and establish the support or maintenance your team needs.

A few practical details

Before you begin.

Can we start with one integration?

Yes. A focused integration is a useful starting point. Scope one workflow, validate it, and expand when there is a clear next requirement.

Do we need our own development team?

For a custom implementation, delivery can include the development work. Direct API integration usually needs a developer on your side to connect and maintain your application.

How are pricing and API usage handled?

Implementation pricing depends on the agreed scope. API usage is scoped separately around request volume, workload, and support requirements. The final proposal sets out those details.

Can you work with our existing tools?

Compatibility is checked during discovery. Available APIs, data access, and your security requirements determine the best integration approach.

Your next step

Start with a useful brief.

A few concrete details help turn an idea into a realistic implementation scope.

  1. 01 The workflow you want to improve
  2. 02 The tools and systems involved
  3. 03 Your expected API volume, if relevant
  4. 04 Your delivery timeline and constraints