Skip to main content
POST
/
webhooks
cURL
curl --request POST \
  --url https://api.maesn.dev/webhooks \
  --header 'Content-Type: application/json' \
  --header 'X-ACCOUNT-KEY: <x-account-key>' \
  --header 'X-API-KEY: <x-api-key>' \
  --data '
{
  "callbackUrl": "https://example.com/webhook-endpoint/12345"
}
'
{
  "meta": {
    "warnings": [
      "Field not used by target system"
    ],
    "pagination": {
      "total": 125,
      "perPage": 50,
      "currentPage": 1,
      "totalPages": 3
    }
  },
  "data": {
    "id": "94fdb7fd-13ae-47a6-8a2a-000e6ddc60d9",
    "callbackUrl": "https://example.com/webhook-endpoint/12345",
    "createdDate": "2025-06-01T00:00:00Z",
    "expiresDate": "2026-06-01T00:00:00Z",
    "secret": "0f9cfb7fe655d00547fa0720ed4fa1777d6ad1a8e3f94c3b16991e7ceaa5a59c",
    "updatedDate": "2025-06-01T00:00:00Z"
  }
}

​
Field support per integration

The callbackUrl should be unique per end user to ensure that each received event can be clearly mapped back to the correct end user.
If you’re not using the Interactive Authentication Flow, make sure the query parameters environmentName and companyId are correctly populated. You can obtain these values by using the GET Environments and GET Companies endpoints available under the Authentication section.
Supported Request Parameters:
​
callbackUrl
string
required
​
resource
enum
required
Available options: ACCOUNT, CREDIT_NOTE, CUSTOMER, DIMENSION, EXPENSE, INVOICE, ITEM, JOURNAL_ENTRY, OFFER, SALES_ORDER, SUPPLIER
If you’re not using the Interactive Authentication Flow, make sure the query parameter companyId is correctly populated. You can obtain this value by using the GET Companies endpoint available under the Authentication section.
Supported Request Parameters:
​
callbackUrl
string
required
​
resource
enum
required
Available options: ACCOUNT, BANK_ACCOUNT, BILL, CONTACT, EXPENSE, INVOICE, JOURNAL_ENTRY, PAYMENT
Ensure that the query parameter _companyId_ is correctly filled with the account ID associated with the contact. This value can be retrieved by using the GET Companies endpoint in the Authentication section. Use the returned id as the value for _companyId_.
Supported Request Parameters:
​
callbackUrl
string
required
​
eventType
enum
required
Available options: CREATED, DELETED, UPDATED
​
resource
enum
required
Available options: ACCOUNT, CREDIT_NOTE, CUSTOMER, INVOICE, ITEM, PAYMENT, SUPPLIER, TAX_RATE
Supported Request Parameters:
​
callbackUrl
string
required
​
eventType
enum
required
Available options: CREATED, DELETED, REVOKED, UPDATED
​
resource
enum
required
Available options: CUSTOMER, INVOICE, ITEM, PAYMENT, SUPPLIER, TOKEN
If you’re not using the Interactive Authentication Flow, make sure the query parameter companyId is correctly populated. You can obtain this value by using the GET Companies endpoint available under the Authentication section.
Supported Request Parameters:
​
callbackUrl
string
required
​
eventType
enum
required
Available options: CREATED, DELETED, UPDATED
​
resource
enum
required
Available options: CONTACT, INVOICE, PAYMENT, TAX_RATE
Supported Request Parameters:
​
callbackUrl
string
required
​
resource
enum
required
Available options: INVOICE
Supported Request Parameters:
​
callbackUrl
string
required
Supported Request Parameters:
​
callbackUrl
string
required
​
eventType
enum
Available options: CREATED, DELETED, UPDATED
​
resource
enum
Available options: CUSTOMER, CREDIT_NOTE, INVOICE, SALES_ORDER, SUPPLIER
Supported Request Parameters:
​
callbackUrl
string
required

Headers

​
X-API-KEY
string
required

API key

​
X-ACCOUNT-KEY
string
required

Account key

Query Parameters

​
companyId
string
​
environmentName
string

Body

application/json
​
callbackUrl
string
Example:

"https://example.com/webhook-endpoint/12345"

​
eventType
enum<string>
Available options:
ACCOUNT,
BANK_ACCOUNT,
BILL,
CONTACT,
CREDIT_NOTE,
CUSTOMER,
DIMENSION,
EXPENSE,
INVOICE,
ITEM,
JOURNAL_ENTRY,
OFFER,
PAYMENT,
SALES_ORDER,
SUPPLIER,
TAX_RATE,
TOKEN
​
resource
enum<string>
Available options:
CREATED,
DELETED,
REVOKED,
UPDATED

Response

200 - application/json
​
meta
object
​
data
object
Last modified on June 10, 2026