Planning an integration with the SignAndGo API.

If your business already runs its own system, such as a client portal, an HR platform or a booking tool, you may want it to send documents for signature without anyone copying details across by hand. This guide is for the person scoping that work, technical or not. It explains the building blocks, the order to tackle them in, and the decisions to make before your developer writes a line.

What the API is for

SignAndGo's developer API lets your own software do what a person would otherwise do in the dashboard: create an envelope, attach a document, name the signers and send it. Webhooks work in the other direction. They let SignAndGo tell your system when something happens to an envelope, such as a signer completing it, so your records update without anyone checking.

Between them, the two remove the most tedious step in many offices: retyping a name and email address from one system into another and then remembering to look for the result.

Is an integration worth it for you?

An integration takes development time, so be honest about the payoff. It tends to make sense when:

  • the same kind of document goes out many times a week
  • the details of each signer already live in your own system
  • something should happen automatically once a document is signed, such as a status changing or a next step starting
  • mistakes from manual copying are causing real problems

If you send a handful of varied documents a month, the dashboard, templates and bulk sending may already do the job with no development at all.

The building blocks

  • Envelope. The unit of work: one or more documents, the people involved and their fields.
  • Recipients. Signers, approvers and people copied in, each with a name and email address, signing in order or all at once.
  • Fields. Where each person signs, initials, dates or fills in details.
  • Status. Where the envelope stands: sent, viewed, signed by some, completed.
  • Webhook. A message SignAndGo sends to an address on your system when an envelope's status changes.
  • Signed document. The completed PDF with signatures in place and the audit certificate appended, which your system can retrieve once the envelope is complete.

A sensible order to build in

  1. Pick one document and one trigger. For example, 'when a candidate is marked as placed, send the assignment terms'. Do not try to automate everything at once.
  2. Set up the document and its fields in a form your system can reuse, so every send lands the fields in the same place.
  3. Send from your system to a test signer you control, and check the envelope appears as expected in the dashboard.
  4. Add the webhook so your system hears when that envelope is completed, and decide exactly what should change in your records when it does.
  5. Retrieve and file the signed PDF in the right place, against the right customer or employee record.
  6. Handle the unhappy paths: an email address that bounces, a signer who never signs, a document that needs replacing.

Webhooks: design for the real world

Treat each webhook as a nudge to go and check, not as the only record of truth. Networks fail, and your system might be briefly unavailable when a message arrives. Good practice is to:

  • check that each webhook genuinely came from SignAndGo before acting on it, using the signature SignAndGo provides
  • make your handler safe to run twice for the same event
  • look up the envelope's current status if a message seems out of order
  • log what you received, so problems can be traced

Testing without upsetting anyone

Use internal test addresses for every early send. A test that accidentally emails a real customer a half-finished contract is worse than a delayed project. Keep a short checklist: create, send, view, sign, webhook received, PDF retrieved, record updated. Run through it after every change.

Security and ownership

Your developer will need API credentials from your SignAndGo account. Treat them like a password: keep them out of code repositories and shared documents, and replace them if anyone who had access leaves. Decide who in your organisation owns the integration, so that someone notices if it stops working, and record what it does in plain language for whoever maintains it next.

API or AI connector?

The API is for systems talking to systems. If what you want is to ask a question such as 'which agreements are still waiting for a signature?', an AI connector may suit you better. Claude and ChatGPT can work with your envelopes through connectors, with consent given per envelope, and nobody needs to write code.

A worked example

This example is invented for illustration. A physiotherapy group with clinics in Birmingham and Coventry runs its own booking system. Each new patient must sign a consent and privacy acknowledgement before the first appointment. The group's developer connects the booking system so that confirming a first appointment sends the form as an envelope. When the patient signs, a webhook tells the booking system, which marks the appointment as ready and files the signed PDF against the patient record. Reception no longer chases paper forms at the front desk.

If you would rather not write code at all, look first at templates and bulk sending, which cover a lot of repeat work without a developer. Questions about the API can go to privacy@myandgo.ai.

Frequently asked questions

Do I need a developer to use the SignAndGo API?
Yes, the API is for software talking to software. If you want automation without code, templates, bulk sending or an AI connector may be enough.
What are webhooks used for?
They let SignAndGo notify your system when an envelope's status changes, such as when it is completed, so your records update automatically.
How should we test an integration?
Send only to internal test addresses at first, and run through creating, sending, signing, receiving the webhook and retrieving the PDF after every change.

See SignAndGo for your team

Send your first envelope in a few minutes, and keep every signed copy with its audit trail.

See how it works