e-invoice.be | Operate As Docs

Connect your client's e-invoice.be with a key they paste, and call its API through Operate As.

Website: e-invoice.be
Connects by: Pasting a API key
Category: Accounting
Services: 1
Tools: 50

Service	Key	Base URL
e-invoice.be	`e-invoice-be`	`https://api.e-invoice.be`

Connecting

Your client makes a API key in their e-invoice.be settings and pastes it on their link. Operate As tries it with e-invoice.be before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "e-invoice-be"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "e-invoice-be"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the e-invoice.be key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install e-invoice.be's typed package for your language:

pip install operate-as-e-invoice-be

pip install operate-as-e-invoice-be

Run e-invoice-be.create_tenant_api_admin_tenants_post

curl -X POST https://api.operate.as/v1/actions/e-invoice-be.create_tenant_api_admin_tenants_post \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {}
  }'

curl -X POST https://api.operate.as/v1/actions/e-invoice-be.create_tenant_api_admin_tenants_post \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {}  }'

Every input, with its JSON Schema: GET /v1/actions/e-invoice-be.create_tenant_api_admin_tenants_post

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.e-invoice.be. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../e-invoice-be/api/me/" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../e-invoice-be/api/me/" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in e-invoice.be. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}