Skip to content

Dibito REST API (1.1)

The Dibito REST API provides services to submit, verify and deliver eBills. The API is designed to be used by biller integrations.
Please refer to the API tutorial for your first eBill submission.

API Key

This API requires an API key to be passed in the `X-API-Key` header.
Generate your API key in the Dibito application under "Dibito -> API Keys".

Top level overview

  • Create bills by posting either a QR-Invoice as PDF to the /v1/business-cases` endpoint or a fully populated JSON object to one of the business case type endpoints.
  • If the request succeeds, it passed validation and can be delivered to the eBill recipients.
  • Use the webhook endpoints to be notified about changes to your recipient subscriptions or business case statuses.

Referencing existing bills

If you pass one of the reference parameters or fill in the referenced bills section in your business case, the submitted eBill will:
  • In case of a reminder: Add a reminder to the eBill portal of the reciepient for the referenced bill.
  • In case of a donation inquiry: Will do nothing. Donation inquiries cannot be referenced.
  • In any other case: Replace the referenced bill with the new one in the eBill portal of the recipient. (Hint: Use advices to effectively cancel delivered eBills.)

Product Website

https://www.dibito.ch

Further Informations

Consult our documentation for further informations about creating and handling eBills.
Download OpenAPI description
api-docs.json
api-docs.yaml
Overview
URL

https://www.codeblock.ch

Codeblock GmbH

contact@codeblock.ch

Languages
Servers
Generated server url

https://app.dibito.ch/

00 Examples

Operations

10 Business Cases

Operations

20 Bill Recipients

Operations

21 Bill-Recipient Subscriptions

Operations

30 Events

Operations

Find events for business cases that changed processing status

Request

Events business cases that changed processing status

Security
X-API-Key
Query
lastEventIdinteger(int32)

Id of the last received event. If omitted, the result starts with the oldest available event. Example: "12345"

limitinteger(int32)<= 1000

Maximum number of items to be returned (technical maximum is 1000, no more will be returned).

Default 100
curl -i -X GET \
  'https://app.dibito.ch/api/v1/events/processing-status-changed?lastEventId=0&limit=100' \
  -H 'X-API-Key: YOUR_API_KEY_HERE'

Responses

Processing status changed events found

Bodyapplication/jsonArray [
idinteger(int32)required

Event ID

Example: 12345
timestampstring(date-time)required

timestamp of the event

Example: "2015-01-01T10:00Z"
businessCaseIdinteger(int32)

Business Case ID

businessCaseSixIdstring[ 0 .. 36 ] charactersBCID[0-9A-Z]{32}required

business case SIX ID

Example: "BCID0FB909852BBC4D06AD8336AAE87D7FC9"
newStatusstring
Enum"OPEN""INVALID""PROCESSING""FAILED""DELIVERED""DONE"
]
Response
application/json
[
  {
    "id": 12345,
    "timestamp": "2015-01-01T10:00Z",
    "businessCaseId": 0,
    "businessCaseSixId": "BCID0FB909852BBC4D06AD8336AAE87D7FC9",
    "newStatus": "OPEN"
  }
]

31 SIX Events

Operations

40 Webhook Management

Operations

90 PDF

Operations

98 Health Check

Operations

99 Authentication

Operations

webhooks

Webhooks

endpoint-controller

Operations