Footer365 API, v1

Build on Footer365

Make a key, make your first call, and the rules every call follows.

The Footer365 API lets your own systems read and change the details Footer365 holds for your people, read each person's signature, read your templates, rules and campaigns, turn rules on and off, and pause and resume campaigns. Resellers and distributors read their customers and seats through it. Webhooks tell your systems when something changes, so they do not have to keep asking.

1. Make a key

An organisation makes keys in the customer portal under Developers > API keys, which needs the Manage developers permission. A reseller or distributor makes them in the reseller portal under Account > API keys. A key is shown once, when it is made: store it in your system's secret store straight away. Give each integration its own key, holding only the scopes it needs.

2. Make your first call

The API is at https://api.footer365.net, and every address starts with the version, /v1. Send the key as a bearer token, over https:

curl https://api.footer365.net/v1/me -H "Authorization: Bearer f365_live_ten_..."

The same call in PowerShell:

Invoke-RestMethod https://api.footer365.net/v1/me -Headers @{ Authorization = "Bearer f365_live_ten_..." }

/v1/me needs no particular scope. It answers with the organisation, reseller or distributor the key acts for, the key's name and prefix, the scopes it holds, its rate limits and, for a key made by an administrator limited to part of the organisation, the part it is limited to in limitedTo. That proves the key works.

3. The rules every call follows

  • https only. A call over plain http is refused rather than redirected. If a key has ever been sent over http, revoke it.
  • Never put the key in the address. A key in the query string is refused, because addresses end up in logs.
  • One account per key. A key acts for the account that made it, and nothing in a request can change that.
  • JSON in and out. Times are in UTC, written like 2026-10-19T09:15:00Z.
  • Ignore what you do not know. New fields may be added to an answer at any time within a version, and new events to webhooks. A change that would break an integration gets a new version, /v2.
  • Lists. People come a page at a time: pass the nextCursor of one page as ?cursor= for the next. Templates, rules, campaigns and customers come whole, in one answer.

Every answer carries an X-Request-Id. Quote it if you contact support about a call.

4. Find the call you need

The reference, in the menu, lists every call with what it takes and what it answers with. It is generated from the API's own description, which most API tools can import from https://api.footer365.net/v1/openapi.json, or download a copy from /developers/openapi-v1.json.

For how a change to someone's details is applied, and how folders and a key's own limit to part of the organisation shape what it reaches, see The Footer365 API in the help centre.

The reference

MetaCheck the service is up, Describes the caller's key PeopleLists people and groups a page at a time, Reads one person and their details, Sets or clears details held for one person, Reads the signature a person's rules give one kind of message TemplatesLists the templates the key can see, Reads one template and its current version RulesLists the rules the key can see, Reads one rule, Turns a rule on, Turns a rule off CampaignsLists the campaigns the key can see, Reads one campaign, Pauses a running campaign, Resumes a paused campaign Recipient listsReplaces a list's entries Customers (resellers)Lists the customers the key reaches, Reads one customer the key reaches, Reads one customer's seats