Integrations

Lesson 75

API and webhooks

Create an API key with limited permissions and a webhook that tells your system when something happens.

Length:
2 min
Plan:
Professional

Watch first: 68. Integrations: the map and the 5 steps

API and webhooks

2 min · Recorded on October 31, 2026

Step by step

  1. 1The API lets another system, yours, your accounting or Zapier, read or load your company’s data in Keptmarks. It gets in with an API key. In Settings, Integrations, API keys, tap Create key, and give it a name that says what it’s for: here, Accounting system.
  2. 2Then, what it can do: each part of the app has Read, and some have Create and change. Check only what’s needed: here, read jobs and reservations, nothing else. The key acts with your permissions, limited to what you checked. If you like, restrict it to certain IP addresses, and choose when it expires. Tap Create.
  3. 3The full key is shown only once: copy it and keep it somewhere safe, for example in your other system’s settings. Keptmarks only stores a fingerprint, so if it gets lost, you revoke it and create another one. That’s why it’s blurred here. Tap Done.
  4. 4In the list you see each key with its permissions, who created it, when it was last used and when it expires. With View requests, what it did: each request with its time and its response. And with Revoke it stops working instantly: if a key leaked or you no longer use it, revoke it. Here I revoke it, because it was a test.
  5. 5Webhooks go the other way: Keptmarks notifies an https address of yours when something happens, like a job finished, a new ticket, a booking or low stock. Under Webhooks you add the address, choose the events, and keep the signing secret, which is also shown only once. With Send test you check that it arrives. All the details are in the developer documentation.

The videos use a demo company with made-up data.