Jump to Content
Billit API
API DocumentationAPI EndpointsDiscussions
v1.0

API DocumentationDiscussionsBillit API
API DocumentationDiscussions
v1.0API DocumentationAPI EndpointsDiscussions

Documentation

  • Introduction to the Billit API
  • Authentication
  • Idempotent Tokens
  • Webhooks
    • Verify Signature
    • Use webhooks to catch E-Invoice statuses
  • Calculations
  • ExternalProvider data
  • Errors
    • 400
    • 401 - Unauthorized
    • 500
  • Versioning

FAQ: Getting Started

  • Sandbox VS Production
  • Where can I find my CompanyID or a PartyID
  • What support can I get as a developer?
  • How do I get started with the API?
  • How do I get started with the API key
    • Where to find my API Key?
  • How do I get started with OAuth?
    • How do I request OAuth Client ID and Secret?
    • When am I required to use OAuth?
  • How do i get started with Curl?
  • Approval process
    • How do I request a demo for my integration?
  • How can I retrieve the next sequence
  • How can I read/save a file

General API Information

  • Header values
  • OData
  • Types
  • Identifiers
  • Ventilation Codes
  • Patchable Properties

FAQ: Peppol

  • Use Billit as AP while also having invoices in Billit
  • Retrieve the original file sent to the choosen network

FAQ: SDI

  • SDI Access Point

FAQ: Chorus

  • Chorus Pro
Powered by 

Versioning

Suggest Edits

We stand by making our API backwards compatible, meaning building your integration a certain way will keep working even if Billit changes things in the API or adds new improvements. You might see double fields that are mapped to with the same data but this will not interfere with your integration.

If anything does change, which we have not done in the last years. We will make an announcement under the changelog.

Updated 7 months ago