Wisegent for developers

Your tools.One connected flow.

Let your systems talk to each other. Connect your CRM, website or reporting tool to Wisegent with our public REST API. Less double entry. More on your terms.

REST · JSON · API v1 · Permissions you choose

Your own connection. Wisegent on the other end.
  • Clients and addresses
  • Read calendar events
  • Revocable API tokens

Built around your workday

The right data. Where you need it.

Build a connection that fits the way you work. Here is what the public API supports today.

Keep client details together

Read, search, create and update clients from your own system. Use your own client numbers to connect your records.

GET · POST · PUT

Connect the right address

Read a client’s addresses, add new ones and update existing ones. Transfer contact and address details without entering everything twice.

GET · POST · PUT

Take your calendar further

Read bookings and calendar events for a chosen period. Use them as input for your own overviews and reports.

GET /events

The calendar is read-only in the public API. Invoices, payroll and record deletion are not part of API v1.

From request to response

One request. A clear response.

Send your token in the Authorization header and receive structured JSON. Here is an example of retrieving a client.

RequestcURL
curl "https://app.wisegent.se/api/public/v1/clients/42" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer YOUR_TOKEN"
Response excerpt200 OK
{
  "data": {
    "id": 42,
    "type": "company",
    "name": "Example AB",
    "contact_email": "[email protected]",
    "status": 1
  }
}

Illustration with fictional data. No request is sent here. Replace YOUR_TOKEN and the client ID in your own integration.

Access with clear boundaries

You choose what the connection can do.

Each integration uses its own token. Grant only the access it needs and stay in control in Wisegent.

  • Choose permissions

    Choose client read access, client write access or calendar read access. The account’s existing permissions also apply.

  • Only your company’s data

    A token can only access the account owner’s data. Other companies’ clients and bookings are not accessible.

  • A secret you control

    The token is shown only once when created. Store it on your server, never in public browser code. Revoke it in settings when it is no longer needed.

From idea to integration

Three steps to your own connection.

You need a Wisegent account and a developer or integration partner to build and maintain the connection.

API base URLhttps://app.wisegent.se/api/public/v1
  1. Create a token

    The account owner opens Settings → Integrations → API. Name the connection, select permissions and copy the token straight away.

  2. Build your first request

    Follow the API reference and send the token as a Bearer token. Start by reading a client and checking the response in your system.

  3. Manage the ongoing flow

    Handle pagination, validation errors and rate limits. Add write access only if your integration needs to create or update clients.

Before you get started

Questions about the API.

Let’s talk API
Which data can we access?

API v1 supports reading, creating and updating clients and their addresses, plus reading calendar events. It does not include invoices, payroll, deletion or creating and changing bookings.

Do we need a developer?

Yes, a custom API integration requires development and maintenance. For ready-made automations without your own code, you can explore our Zapier integration instead.

Are there rate limits?

The limit is 120 requests per minute per account owner, including up to 30 write requests. Calendar queries can cover up to 93 days. Use pagination and handle the 429 response code in your integration.

Where is the documentation?

The API reference is in Wisegent’s help centre after sign-in, with endpoints, authentication, examples and an OpenAPI specification. It is also linked from Settings → Integrations → API.

Your systems. Your connection.

What would you like to connect to Wisegent?

Tell us how you work today. We’ll help you see what the API can support and where to start.